Hi,
Now that T4 is likely to go the way of the dodo and I'm looking at a new
app, I'm evaluating T5 along with several other frameworks. I'm trying to
get some info on T5 that may help out.
It appears that the page spec has gone away in T5. While it was optional in
T4, one of the things I
Interesting idea.
You could look at contributing a BindingSource, call it 'variable'.
You'd need to investigate how they are created, not sure about typing
the values, the get/set in the Binding interface are Object so you may
be able to get away with out worrying about it:
t:loop
On Fri, 24 Aug 2007 14:49:39 -0300, Josh Canfield [EMAIL PROTECTED]
wrote:
Interesting idea.
You could look at contributing a BindingSource, call it 'variable'.
You'd need to investigate how they are created, not sure about typing
the values, the get/set in the Binding interface are Object
Well, on the one hand I guess that means it's not supported yet. But on the
other, it's nice to see that there's interest in it.
Taking it a step further, it'd be nice if you didn't even need to bind a
value and if they just became properties of the component itself. E.g., why
supply a value or
anyway? If the loop can already figure these out, make them read-only
properties of the loop. Then you could reference them like ${loop_id.index}
or ${loop_id.value}.
That'd be nice in some cases, but there are also times when I want to
be able to access them through my component class. I
