ampatspell. wrote:
> Will legacy XForms (ops 2.8) be supported and improved after 3.0 final?
> I liked very much the `old` simple and elegant approach with easyness of
> development and, as i don't need full XForms support, i'm thinking of
> staying with the `old`. of corse, only if legacy forms wouldn't be
> supported only for back-compability.
If by "supported" you mean improved and debugged, the answer is likely
no, at least, not by us and for free. If by "supported" you mean do we
plan to remove the code, the answer is that at this point we do plan
to leave the code in place for 3.0, as maximizing backward
compatibility is a goal of 3.0.
Note that I obviously don't agree that "elegance" and "ease of
development" are diminished with OPS 3.0 ;-) On the contrary:
o If you use XForms, you now have the standard approach for
integrating XForms with XHTML. You also have very close to 100% of
the XForm spec supported.
o If you don't use XForms at all, then things have improved a bit,
with the PFC's generic support for XML submissions.
Now if you mean that you do not want to use the Ajax-based XForms
engine, then you may have a point: it should be possible in the future
to make the XForms NG engine support non-Ajax-aware browsers, possibly
with some limitations (such as a restriction in the XForms events
fired). This would be the way to go IMO.
-Erik
--
You receive this message as a subscriber of the
[hidden email] mailing list.
To unsubscribe: mailto:
[hidden email]
For general help: mailto:
[hidden email]?subject=help
ObjectWeb mailing lists service home page:
http://www.objectweb.org/wws