Re: Time out!
Re: Time out!
- Subject: Re: Time out!
- From: Thomas <email@hidden>
- Date: Sun, 13 Aug 2006 08:04:39 +1000
For a long time our CMS has had the ability to serve WO-intelligent
content by interpreting tags of the form
<wotag wotype="WOString" value=session.loggedInUser.niceName
valueWhenEmpty="No name!" />
or
<woblock wotype="WOConditional"
condition=session.loggedInUser.niceName negate=true>
Your name is missing!
</woblock>
or
<wotag wotype="ShoppingCartDetails" cart=session.submittedOrder />
And this is a wonderfully powerful way to embed very intelligent
content. However, I have yet to find a good way of editing it. You
can define these tags in the GoLive HTML dictionary, and the page
will display with all the tags in their correct hierarchy, and you
can even "twiddle" blocks to display their nested content. But the
major problem is that GoLive insists on adding quotes around all
attributes, which makes it useless.
But if anybody knows how to edit tags of this sort in a mainstream
WYSIWYG web editor, I'd be very interested. I'd be happy to buy a
commercial editor if that's what it takes, but a GoLive plugin would
be great.
Reading between the lines of what is reported about WWDC, it seems
that people like me who work in the visual space instead of the
textual space are going to be looking for a new way to edit our WO
pages. I love WOBuilder for what it is supposed to do, but swear at
it a lot because it does things I don't want. The single-file .wo
template with these sort of tags would be great, as long as there was
some form of visually-oriented editor.
I'm all ears!
A different problem is that Web-page-embedded WYSIWYG HTML editors
can't handle the wotags. They either delete them or quote all the
attributes or do other bad stuff. I've even considered being able to
parse another form, eg {wotag wotype="WOString" ...} just for this.
Regards
Thomas
On 13/08/2006, at 7:17, Anjo Krank wrote:
Am 12.08.2006 um 23:03 schrieb Chuck Hill:
An import point to consider here is that we are not limited to
this traditional implementation. The only restriction that the WO
frameworks place is that there is an implementation for
public WOElement template()
I have seen (I think it was another of David Terans "do it like
this" examples that allowed there to me no .wod file, with the
HTML containing (for example)
<WebObject name="Foo" WOComponent="WOHyperlink" class="bigLink"
string=linkTitle/>
I have that code here somewhere. Allegedly, the problem is that
extra parsing step that makes startup times larger, in fact this
was the reason why these absurd .wo packages were created in the
first place. Another problem is the ambiguity between strings and
dynamic parts.
OpenGroupWare had some marginally better-thought out templating:
<wo:WOHyperlink const:href="http://...";
dynamic:onclick="someMethodOnComponent"..>
Which at least can handle XML. Leaving the problem with where you
put the .api and the .woo files. And what to do with the bazillion
of existing components out there. And localization...s
This is not to but the idea down, far from it. In fact, I'll gladly
convert all of Wonder to it once it gets more fleshed out. But it
needs some serious benefit over the existing solution (a working
DreamWeaver plugin?).
Cheers, Anjo
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40woomeranet.com.au
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