I still think you'll have it... Just look at the plugin discussions.
The plugin manager is undeniably my 'baby', and it reflects in the amount of passion that I have for it, that I'm not only working on it, working on all its mechanics but also in developing plugins for it, and that as working as it is, it's still very much a work in progress.
I'm in pretty much none of them, because it's way out of my league. Or I just simply fear having to deal with it later...
Well, plugins had to be dealt with sometime, and it was at the stage where I couldn't let it pass any longer without doing something to it, so I started really figuring out the mechanics of it - and after that, it was simply the period of time it took to solve the underlying issues around the plugin manager's behaviour. I'm still wrangling with some of it but the core system works rather well.
I did get the feeling that you weren't that interested in writing plugins - and that's cool. I like writing plugins because it means that stuff I wouldn't put in the core, I can put in plugins, and it means that functionality can be developed in relative isolation, rather than having things that interact with each other like most core stuff.
Perhaps I started Wedge because I didn't want to have to bother with making mods any longer...
Heheh, well, part of the appeal for me was the chance to really make something of the package manager in some fashion. It isn't a bad tool, but it needed some serious love and attention.
I'm still stuck with AeMe too, BTW. I've reached a point where I'm starting to think it should stay the way it is, and I'll (or you'll) merge the attachment and avatar systems into AeMe once we reach 1.1 or something, or possibly earlier but not before the demo...
Hmm, I understand the reticence, not least because there is simply so much that interacts with it, it has so many consequences, and most of them have to not only be gotten right, but to avoid making a hash of it, most of them have to be figured out in advance.
I don't have a problem with releasing the demo as it is publicly (but not releasing a downloadable demo yet, there's still stuff too broken, like board access not having a working UI) and doing that after the demo but the longer it's left (and in particular after 1.0), the harder it's going to be to do.
Much as I stated with the dropping-bbc-in-favour-of-WYSIWYG, it's something that if we're going to do, we pretty much have to do it now rather than later.
The converter can be fixed up after the event. The core support, though, can't - because if it's left past 1.0, it's not only importing but upgrading that's going to be problematic - and that's a scenario I don't want to go down if at all possible, just because of the nightmare scenario it causes generally. Far better that we put the core in the core and have the converter deal with - measure twice, cut once, rather than measure three or four times and cut twice.
