Re: Time out!
Re: Time out!
- Subject: Re: Time out!
- From: Chuck Hill <email@hidden>
- Date: Mon, 14 Aug 2006 09:57:26 -0700
On Aug 14, 2006, at 9:25 AM, Alan Ward 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
On Aug 12, 2006, at 3:17 PM, 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.
--
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 (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden