Combined Component Template Parser that reduces .wo components to
single .html files
For people who are used to Wonder's, this is not the same
implementation. With 5.4's template parser, there are a couple
notable differences:
1) 5.4 requires you to choose between using wod + html or inline.
You cannot mix and match within a single component like you can
with Wonder's WOOGNL parser.
2) 5.4 DEFAULT syntax is, for example, <wo:WOHyperlink action =
"[doSomething]"/> with brackets rather than $doSomething like
WOOGNL. However, there is a configuration setting to switch to use
$ if you'd like. WOLips supports parsing bracket-style as well as
offering completion for them.
3) The definition of which parser you use is an application
setting. This means that you cannot mix and match parsers among
frameworks. So if you want to use Wonder's parser, you cannot mix
it with 5.4's (and vice versa).
4) WOOGNL framework does not currently work with 5.4. I have a 5.4-
compliant version ready, but due to some API changes, it requires
changes to the Project Wonder build system. Going forward, we will
at the very least have to have separate 5.3 and 5.4 builds of
WOOGNL, and probably the nightly build server will offer a separate
complete 5.3/5.4 build. I don't know what the timeframe is for
addressing the build system issue. In the meantime, I may just
provide a custom build of WOOGNL for 5.4 that is not updated
automatically for now.
5) The new 5.4 parser requires valid XML template files.
Is there a recommended migration route from 5.3 style wod/html to 5.4
html ? is it a case of changing each and every component by hand ?
Simon
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
