You actually want this one on wonder-dev instead of woproject-dev,
but I suspect I didn't go forward more with it mainly because I
didn't want to deal with symbol collisions in constants. You would
pretty much have to introduce some sort of leading symbol like in
your example, which would subtly break anyone who was using that
symbol already, and then you'd have to introduce support for escaping
that symbol. With non-constant, it's a lot easier to introduce a new
symbol because there are a lot of them that can't appear in a
keypath, but in a constant, it's open season. I'm guessing I didn't
want to deal with it at the time, but one of our guys has has asked
for constant support also. You can send me your patch if you'd like?
On Jan 17, 2007, at 12:39 AM, Peter Vandoros wrote:
> I have just integrated the WOOgnl framework because Mike got me
> very interested about Helper Classes :)
>
> Anyway, i have a question/request:
>
> Is it possible to allow a helper class come from a constant binding
> instead of a key value coding binding?
> eg.
> come from: value = "*currentPersion|displayName"; (note use of '*'
> as the helper marker. this should be configurable)
> instead of from: value = currentPerson|displayName;
>
> The reason i want to be able to do this is because i am one of
> those developers that still uses WOBuilder for creating the
> component structure and it treats those as illegal bindings.
>
> Being open source, i looked at the source and have discovered
> commented-out code that used constant associations as well. Why has
> this been commented out?
>
> I can make some changes to the code in a custom version so it will
> optionally allow this situation but i don't want to have to reapply
> my changes for every new version of the framework.
>
> So i was wondering if i were to modify the source to optionally
> allow my scenario, could it possibly be included into the
> "official" version?
>
> Much appreciated
>
> Peter
This archive was generated by hypermail 2.0.0 : Wed Jan 17 2007 - 07:12:23 EST