Re: WOComponent children
Re: WOComponent children
- Subject: Re: WOComponent children
- From: email@hidden
- Date: Wed, 16 Jan 2008 18:09:33 -0500
Hi Mike,
I've heard of scriptaculous :-) In plain
text scriptaculous.js has the following comment:
"inserting via DOM fails in Safari
2.0, so brute force approach"
All I'm saying is that while I agree
that your proposed DOM manipulation solution is the best given the current
architecture of WO, it is still working around a flaw in the base architecture.
Also, the DOM manipulation should be tested on a range of browsers and
implemented carefully. It will probably work on most of them in the end...
but why can't we just do it the right way, by stating the requried resources
between the head tags on initial page load?
This marks the first time that WO has
put up a road block on my creativity. It is a flaw.
In parting, I hope you do get that DOM
manipulation working and we can all benefit from it.
Yours,
-- Aaron
>For that matter, the default implementation of
scriptaculous ALREADY
>works this way -- look at scriptaculous.js --
it dynamically loads the
>other parts of the framework (effects.js, builder.js). _______________________________________________
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