hello The problem with pushing all kinds of stuff to the client is (and i suppose that's why the xsl transformations were removed from the client in the wizard) is that if you do this you want to know your client well. Well, if there is one thing about browsers that most developers are properly impressed with than it is the surprising way in which brosers differ (between brands and between versions). So I think a smarter client is a great idear, but not if this client is 'any broser'. perhaps xul and a lock to the mozilla platform would be safer. I know that Oracle has made a huge client environment for their database apps as a applet (best of both worlds?). but plain old jscript and relying on changing xml, dom, xsl, whatnot browser implemetations dous not seem like a smart move to me.
regards, Ernst > Hi All > > anyone interested in client-side XML processing, please visit the > following link: > http://xmljs.sourceforge.net/ > > It's a javascript XML parser, which I think is better suited to > editwizards than the current implementation (or any proposed future > implementations that I've heard of). Another huge benefit would be the > introduction of metadata-based (or other) client-side logic, which would > change the possibilities of editwzards beyond simple content management. > > I think that mmbase is a toolset at the core, then with the various > applications and editwizards it becomes a CMS, but the introduction of > "proper" client-side logic could allow it to become a platform for > full-blown applications as well. > > cheers > Emile > _______________________________________________ > Developers mailing list > [email protected] > http://lists.mmbase.org/mailman/listinfo/developers > _______________________________________________ Developers mailing list [email protected] http://lists.mmbase.org/mailman/listinfo/developers
