Re: Time out!
Re: Time out!
- Subject: Re: Time out!
- From: Anjo Krank <email@hidden>
- Date: Mon, 14 Aug 2006 22:40:35 +0200
I don't really agree with most of the proposed changes (bindings
inline, yeech!), but the <webobjects name="foo"> -> <span woid="foo">
or <tr woid="foo"> might actually be useful for us. In particular, we
could use the WST because IIRC, the main problem was that they choke
on webobjects tags without some huge patch... so you would morph the
tags on loading into the editor (WOGenericContainer/tr -> <tr
woid="foo">) and re-morph on save? Would that work?
Cheers, Anjo
Am 14.08.2006 um 22:01 schrieb Mike Schrag:
To do any level of meaningful refactoring, etc, you would have to
have an AST-style model behind the files anyway, in which case
writing out either format is not that big of a deal. Also, once
there is a proper WO-compatible HTML parser (maybe actually using
WOParser) as part of said tool, adding support for jsp-style
bindings probably isn't all that complicated.
ms
On Aug 14, 2006, at 3:53 PM, Thomas wrote:
Perhaps we could have it both ways? If we had a tool that
converted between the two-file and one-file forms (possibly using
XSLT), you could at least keep the run-time generation and
development-time editing as separate issues.
After that you could add a second parser so that either form could
be used at run-time. Or even better, have the .html file itself
define which method was to be used-- either for the entire file or
maybe even for each tag.
Regards
Thomas
On 15/08/2006, at 2:57, Chuck Hill wrote:
Mixing wod definitions in with html is simply rude :-) It makes
refactoring even more of a pain than it already
is (with KVC) as now you have another set of files in which
references may be found.
I am not so fond of it myself. I have a number of pieces of code
that dynamically generate the WOD portion for use with canned
HTML (or vice versa). Changing these to having them all in one
would be a painful task. Luckily, the architecture of
WOComponents is such that we don't all need to use the same
parser. Even different pages in the same app can use different
parsers.
If we are going to adapt an existing HTML editing tool for use
with WO we probably don't have any choice but to follow the herd,
discard the concept of WOD and merge both concepts into a single
HTML file.
Chuck
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mdimension.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40logicunited.com
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden