On 8/14/06, Mike Schrag <[EMAIL PROTECTED]> wrote:
I don't know enough about Eclipse internals to know how feasible this is, but would defining a default namespace and treating WebObjects .html files as XML/XHTML allow for more flexibility in parsing?
Is there any merit to the possibility of using XSLT or something similar to transform the files back and forth between legacy WebObjects HTML format and some XHTML format that the default Eclipse tools would handle better, either in-memory or as some tools process?
Just thinking out loud here, feel free to shine the harsh light of reality on my simplistic thinking :).
Logan
If it's going to be an Eclipse-based tool, my preferred route would
be to propose an addition to the browser API that supports DOM
access, at which point we can do all kinds of fancy things without
requiring our files to be in any particular format.
ms
I don't know enough about Eclipse internals to know how feasible this is, but would defining a default namespace and treating WebObjects .html files as XML/XHTML allow for more flexibility in parsing?
Is there any merit to the possibility of using XSLT or something similar to transform the files back and forth between legacy WebObjects HTML format and some XHTML format that the default Eclipse tools would handle better, either in-memory or as some tools process?
Just thinking out loud here, feel free to shine the harsh light of reality on my simplistic thinking :).
Logan
_______________________________________________ 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 archive@mail-archive.com
