- From: T.V Raman <raman@google.com>
- Date: Tue, 25 Oct 2005 09:38:18 -0700
- To: wiecha@us.ibm.com
- Cc: allan@beaufour.dk, www-forms@w3.org
Building on what Charlie says below:
If you compare a vanila html+javascript AJAX impl with an
XHTML+XForms impl of the same app, you'll typically discover that
the script code in the vanila AJAX application ends up
implementing an application-specific version of the XForms
Process Model.
This is not a knock against scripting; scripting has its place
both within and without the XForms world. However, using the
XForms Processing Model where appropriate reduces the need to
repeatedly implement the oft-seen design pattern of "update
model, copy fresh values to the view"
that one sees in many AJAX applications. The net effect of this
is that it frees the JavaScript programmer to discover the next
level of design patterns
>>>>> "Charles" == Charles F Wiecha <wiecha@us.ibm.com> writes:
Charles> There are also great opportunities, I think, for
Charles> using XForms to reduce the need for custom
Charles> javascript in AJAX applications...why not think
Charles> about the XForms processing model as the glue that
Charles> links XML models to HTML widgets in an AJAX app?
Charles> This would be another benefit to supporting a
Charles> separable XForms model and custom controls...
Charles>
Charles> Charlie Wiecha
Charles>
Charles>
Charles>
Charles>
Charles>
Charles> Allan Beaufour <allan@beaufour.dk> Sent by:
Charles> www-forms-request@w3.org 10/25/2005 09:40 AM
Charles>
Charles> To Undisclosed.Recipients: ; cc www-forms@w3.org
Charles> Subject Re: AJAX vs. Xforms
Charles>
Charles>
Charles>
Charles>
Charles>
Charles>
Charles>
Charles> On Tuesday October 25 2005 14:05, Jason Eacott
Charles> wrote:
>> ajax is popular because its accessible, and can be applied
>> to existing infrastructure. xforms is a whole different
>> approach, with a much
Charles> steeper
>> learning curve and requires more effort to make a
>> reality. but clearly there are lots of people who think
>> the effort is worth it.
Charles>
Charles> I think it is. There are overlap in the uses of AJAX
Charles> and XForms IMHO. As Mark also writes we really need
Charles> some better intros and examples -- that could help
Charles> the process.
Charles>
Charles> .... Allan
Charles>
Charles>
Charles>
Charles> <br><font size=2 face="sans-serif">There are also
Charles> great opportunities, I think, for using XForms to
Charles> reduce the need for custom javascript in AJAX
Charles> applications...why not think about the XForms
Charles> processing model as the glue that links XML models
Charles> to HTML widgets in an AJAX app? This would be
Charles> another benefit to supporting a separable XForms
Charles> model and custom controls...</font> <br> <br><font
Charles> size=2 face="sans-serif">Charlie Wiecha</font>
Charles> <br><font size=2 face="sans-serif"><br> </font> <br>
Charles> <br> <br> <table width=100%> <tr valign=top> <td
Charles> width=40%><font size=1 face="sans-serif"><b>Allan
Charles> Beaufour <allan@beaufour.dk></b> </font>
Charles> <br><font size=1 face="sans-serif">Sent by:
Charles> www-forms-request@w3.org</font> <p><font size=1
Charles> face="sans-serif">10/25/2005 09:40 AM</font> <td
Charles> width=59%> <table width=100%> <tr> <td> <div
Charles> align=right><font size=1
Charles> face="sans-serif">To</font></div> <td
Charles> valign=top><font size=1
Charles> face="sans-serif">Undisclosed.Recipients: ;</font>
Charles> <tr> <td> <div align=right><font size=1
Charles> face="sans-serif">cc</font></div> <td
Charles> valign=top><font size=1
Charles> face="sans-serif">www-forms@w3.org</font> <tr> <td>
Charles> <div align=right><font size=1
Charles> face="sans-serif">Subject</font></div> <td
Charles> valign=top><font size=1 face="sans-serif">Re: AJAX
Charles> vs. Xforms</font></table> <br> <table> <tr
Charles> valign=top> <td> <td></table> <br></table> <br> <br>
Charles> <br><font size=2><tt><br> On Tuesday October 25 2005
Charles> 14:05, Jason Eacott wrote:<br> > ajax is popular
Charles> because its accessible, and can be applied to
Charles> existing<br> > infrastructure. xforms is a whole
Charles> different approach, with a much steeper<br> >
Charles> learning curve and requires more effort to make a
Charles> reality. but clearly<br> > there are lots of
Charles> people who think the effort is worth it.<br> <br> I
Charles> think it is. There are overlap in the uses of AJAX
Charles> and XForms IMHO. As Mark <br> also writes we really
Charles> need some better intros and examples -- that could
Charles> help <br> the process.<br> <br> .... Allan<br> <br>
Charles> </tt></font>
Charles> <br>
--
-- T. V. Raman
Received on Wednesday, 26 October 2005 01:13:27 UTC