Ernst wrote: "i suppose there are twoo distinct approaches 1 you use the current editwizard application and use the generated xml to create some other form of editors. this could done by a flash movie, i suppose. 2 you write a clien that can read editwizard editor definitions and can talk to dove. (if you want to use dove, in this approach for instance i think the xul style would require a rdf resource). this approach i think is a lot harder.
I think many developers will have some reservation towards flash becouse it is not open source and maintaining flash movies that you didn't write yourselfe are a bitch to maintain (in my humble experience,) but it is an interesting idear nevertheless.." Hi Ernst I envisage that there will be a fixed element to the flash and a dynamic element - the dynamic element created from the existing editwizard XML and the fixed element created by a flash GUI wizard/designer/tool. Furthermore, there would have to be a logic engine/parser/whatever, to communicate with the server and perform validation, etc. (this should be a flash script). Because of the general disdain for flash "programming" (movie-making), the best solution would be to have the design tool create xml and flash movies created on-the-fly, server-side, then despatched to the client. So, one function/servlet/whatever would create the edit portion of the flash xml from the editwizard xml, embed that in the static flash xml template, serve that to the engine which creates the flash movie, for delivery to the client. Obviously, this process should be cached! I realise this is easier said than done, but think that if it is done well, it'll change the potential of mmbase. I really don't want to have to write flash movies, so I'm voting on Laszlo being the obvious choice (as it is open source) for creating the flash movies. Regards Emile _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
