On Aug 14, 2006, at 5:21 PM, Joe Little wrote:
On 8/14/06, RedBugz Software <[EMAIL PROTECTED]> wrote:
I believe the Spindle Eclipse plugin for Tapestry allows for these
separated
files. I may be naive, but are there that many technical hurdles
to allowing
<span woid="componentName"> in addition or as a replacement to
<webobject
name="componentName">? Both Tapestry and JSF use this convention
and both
have Eclipse support, including WYSIWIG support either done or
coming soon
for both.
I'm presuming that for this all to work, we'd have to do as Anjo
suggests and have the editor convert on the fly from WO tag syntax to
this, and save back as WO tag syntax. I noticed people talking about
TR's (news to me) and this <span> tag, but I don't know how that would
work with WebObjects unless there was some process in the
request/response loop know how to handle the alternative. Is there
something I'm missing here, and that we can use other tags with WO
now?
You always could. What matters is a tree of WOElement returned by
the template() method in WOComponent. This can be overridden to
parse any sort of template and return the WOElement tree that really
drives WO and RR loop. Think of the .HTML and .WOD as a frozen
WOElement tree. Hmm, we could serialize it into XML. Now THAT would
be UGLY!
Chuck
--
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems. http://www.global-village.net/products/practical_webobjects
_______________________________________________
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
