Stateful NonSynchronized Reusable Components are pretty useful as well.


On Jul 4, 2007, at 7:36 PM, Kieran Kelleher wrote:

Topic = "Stateless NonSynchronized Reusable Components" ........ these make life easier and easier

On Jul 4, 2007, at 3:00 PM, Chuck Hill wrote:


On Jul 4, 2007, at 11:46 AM, Pascal Robert wrote:

3. Large, convoluted, table based layouts are very difficult to visualize in a text only view. This is pretty obvious, but since I've been using css instead of tables and breaking things into components for my own stuff forever, I've not confronted it head-on before. So I think using the component editor actually encourages you to write better components.

We can hope. I have been disturbed to see how little use many WO developers make of the power of components. It should be their bread and butter, not some advanced technique.

Topic for WOWODC 2008 ? :-)

In fact that is one of the topics I am considering.

Chuck

--

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      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/kieran_lists% 40mac.com

This email sent to [EMAIL PROTECTED]



--

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      (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Reply via email to