Re: Best Practice Displaying Option Text Field
Re: Best Practice Displaying Option Text Field
- Subject: Re: Best Practice Displaying Option Text Field
- From: David Elsner <email@hidden>
- Date: Fri, 16 Apr 2004 10:04:21 +1000
I'm not sure if this is best practice or not, but I would just bind the
WOConditional to the variable streetAddress if its null = false,
anything thing else will return true.
Dave
On 16/04/2004, at 9:23 AM, Hunter Hillegas wrote:
I have a best practices question...
Let's say I have a text field, like a second line of a street address,
that I consider 'optional'. When I display that entity using
WOStrings, I want to only show that line/string if it contains data.
What I've been doing is writing a method in the component, such as
address2IsEmpty() or whatever that returns a boolean and then I wrap
the line in a WOConditional... Works fine but seems like a bit heavy
handed...
Since I keep finding out cool things that WO will do for you, I
thought I would ask if there is a short cut around writing the method,
etc...
Thanks!
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.