On 1.2.2007 17:35 Uhr, Joern Nettingsmeier wrote: > Michael Wechner wrote: >> Joern Nettingsmeier wrote: >> >>> no, i'm not talking about passing the data from a client browser. we >>> won't find a common denominator for that, since every editor is doing >>> it's own thing here. >> >> >> and this is exactly what Neutron tries to solve. Instead writing for >> each editor a dedicated connector implement Neutron once ;-) > > i like the idea of neutron, but your argument is a little strange. i > might as well suggest that all editors implement a bxe-compatible mode. > (now that would be frightful indeed :)
What'ss wrong with the way BXE loads and saves the XML data? I don't say, everyone should do it that way (it was never intended for that) and I certainly don't vouch for using that as a "standard", but all it does is GET and PUT the XML file and to which URL should do that is defined in the config XML file. You even could write your own loader/saver classes. If you don't like PUT and GET... So I really don't see, what's frightful about the loading/saving part. But anyway, what do I care, WORKSFORME :) chregu > but it's the same as with many things w3c: working drafts come cheap, > it's the implementations that make a new spec. > > as nice as neutron seems, it does ring a warning bell that there are no > other implementations on the horizon. i don't mean to disrespect the > effort, but as it is now, it's just another single-vendor standard... > > that said, i'm all for integrating a complete neutron implementation > into lenya, but it does not really address the current issue of editor > abstraction. > > get the tinymce people to add a neutron front-end, and i will be dancing > naked on the streets shouting "michi, you da man!" :) > > -- christian stocker | Bitflux GmbH | schoeneggstrasse 5 | ch-8004 zurich phone +41 44 240 56 70 | mobile +41 76 561 88 60 | fax +41 1 240 56 71 http://www.bitflux.ch | [EMAIL PROTECTED] | GPG 0x5CE1DECB --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
