I hear what you guys are saying... thank you for all your thoughts. I've posted a feature enhancement request via "Radar" at Apple. Here's what I asked for:
Bug ID# 5673303. Title: addRequiredWebResources() WebObjects feature enhancement Request-Response loop Summary: The request-response loop is outdated. It needs to be modified to call a new method "WOComponent.addRequiredWebResources()". All components on the page should get this message, even those that are not shown because they are wrapped in a WOConditional that evaluates to false. That way all components in the tree get a chance to say what javascript and CSS resources they need even if their appendToResponse() is never called. Why this is needed: In order to create truly reusable sub components, we need this feature. In the Web 2.0 era, where partial page refreshes are common, it is very possible that you will later flip the boolean of a WOConditional so that some complex sub components are displayed and advanced Javascript and CSS resources are needed between the "head" tags. Therefore the request-response loop must anticipate that elements not currently displayed at initial full page load will later be shown and will have needed their resources placed between the head tags at initial page load time. Notes: Without this feature, we can't make self contained WOComponents that are full of AJax and Web 2.0 features. We have to live with compromises that make assumptions, we can't just blindly take a WOComponent from a framework, slap it on a page, and expect it to work. Thank you. -- Aaron
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
