Nathan,
> I am having trouble integrating our own Javascript libraries into a
> xform rendered by Orbeon because of YUI versions. We depend on YUI
> 2.2.2 but Orbeon is using 0.12.0. I'm going to try rebuilding the
> resources jars with the newer YUI js files. Is there any reason
> reason why Orbeon is using such an old version of YUI? Anything I
> need to watch out when changing to a newer YUI version?
The main reason is that upgrading takes time, in particular:
* Everytime you upgrade you have to make sure nothing is broken.
* We have made changes to YUI and during an upgrade we need to make
sure the changes are either already included in YUI or port them to
the new version:
http://wiki.objectweb.org/ops/Wiki.jsp?page=YUINote that in spite of the big difference in version numbers, the
version we use is not THAT old: it's just that Yahoo changed their
versioning strategy and jumped from version 0.12.2 (January 2007) to
version 2.2.0 (February 2007).
It would be a great contribution if you did the work and contributed
it back, but to do it perfectly you would need to look at the list of
changes at
http://wiki.objectweb.org/ops/Wiki.jsp?page=YUI as well.
-Erik
--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/--
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
Locked
