I'm wondering though what the value of this is. The main advantage of CForms is to handle the typical problem of HTML forms: the form needs to be redisplayed in a loop until everything's valid. This is because the browser is a stupid client which we need to send a new page after each interaction.
If you're developing a smarter client using XUL or Flash, you're not likely going to send a new XUL file or Flash movie to the browser between each interaction. Rather, all validation logic (and event handling logic) can be implemented in the client, which can communicate XML messages with the server. Somehow forcing CForms in between there seems unnatural to me. On Tue, 2004-04-06 at 14:05, Vadim Gritsenko wrote: > roy huang wrote: > > <snip what="CForms in XUL"/> > > >WDYT? > > > > > > I think it's time to see some examples. If one of you guys who knows XUL > can produce XUL skin for CForms and/or other interesting examples, I'm > sure they will be included as part of Cocoon samples app. > > Vadim -- Bruno Dumon http://outerthought.org/ Outerthought - Open Source, Java & XML Competence Support Center [EMAIL PROTECTED] [EMAIL PROTECTED]
