Hugi,
On Feb 17, 2009, at 8:00 PM, Hugi Thordarson wrote:
Heh, yeah- it's somewhat insane that the only way to find out how
WOConditional works
Actually, this is not (or, more precisely, SHOULD not) be a
WOConditional trait; the very same behaviour should be used for
all .wod boolean bindings which contain a number object (say, for a
WOHyperlink "disabled" binding, and for WOString "escapeHTML" binding,
yadda yadda yadda...).
If each of them does this for itself (and potentially in a different
way than all the others), then the thing is much worse disaster I've
thought :(
is to decompile it (or by trial and error). And I agree -
WOConditional should only resolve to false for null or (exactly) zero.
Quite.
But since WOConditional's behaviour will never be modified,
Yeah, that's what I meant by "it's of no consequence" of mine.
the simplest way is probably to create your own conditional
component/element and just do a find/replace. Should be simple enough.
It is not, or am I overlooking something?
There's a lot of different BigDecimal-returning attributes in the
project, and I see no straighforward way to find which ones of them --
and where -- are used for diverse boolean conditions in .wod's -- but
for going through them manually and checking them all by hand, for
which the project _is_ sort of big :(
Thanks and best,
---
Ondra Čada
OCSoftware: [email protected] http://www.ocs.cz
private [email protected] http://www.ocs.cz/oc
_______________________________________________
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]
