I agree that dividing the project up like this and separating the html from the code is great and very progressive, but that's very javascript-centric code, it would affect which types of developers you'd be getting considerably. I, for instance, am not the greatest javascript coder, though I know my PHP pretty good... I'd probably be useless...
But there are very many pluses going for the JSON model... Especially if we were to use a good javascript library at the core. -Arnor On 2/7/07, Mathieu Lecarme <[EMAIL PROTECTED]> wrote:
till a écrit : > Apologies - it's late here. Just resending with the correct subject. > > ---------- Forwarded message ---------- > > Hi boys and girls, > > the draft is here: > http://trac.roundcube.net/trac.cgi/wiki/Plugin_API_Draft > > Happy to read all your feedback! > > Cheers, > Brennan & Till > JSON is a very good idea both for js interface and distant API. Full DHTML pluggable interface is a huge change in code, but JSON server side implementation will not break anything, it may be a good starting point? With a read/write contact API I can post a protoype of AdressBook.app sync, and Thunderbird 2.0 too. M.
