Hi all, Just a quick update to let you know what's happening with dragonfly-ng, and what on earth it is.
Basically, dragonfly-ng is (almost) a complete rewrite of Dragonfly's client side logic (that is, the javascript code). I've decided to drop the work I was doing on previous client mockups (still available in experiments/avocado if you want to look at them), since the design ended up evolving to something very similar to what we originally had with Dragonfly, and I figured that it's not really worth duplicating the work. At the moment, I've started working on the groundwork. I've implemented most of the SourceManager stuff, so, we can add and remove sources fairly easily. Sources are basically the things that were known as 'views' in ye olde Dragonfly. I'd plan that plugins can provide sources if they wish, and can register them with the SourceManager simply by doing Client.sourceManager.add (this); Obviously, plugins don't have to provide sources, they can do whatever they want. Anyway, before I start getting technical. :) I'm planning at the *very* least, some basic mail viewing functionality for M4. This means that the following tasks would needed to be completed for dragonfly-ng: * Coding up some sort of plugin loader and manager. * Implementing authentication against the server. * HTML templating, though, I haven't quite decided how exactly this will work. * and obviously, implementing the mail source and logic. Hopefully that explains a bit. I spent 30 minutes racking my brain about something that I couldn't remember exactly that needed to go in this email, so, if you remember for me, *please* ask; it needed discussion IIRC. If you really do want to check out the code, you can find it in experiments/dragonfly-ng. Also, *we need a better name*! :) Cheers, Alex Hixon _______________________________________________ Bongo-devel mailing list [email protected] https://mail.gna.org/listinfo/bongo-devel
