In message <004e01c133bf$fa6ecca0$0100a8c0@scooby00>, Scott Eade
<[EMAIL PROTECTED]> writes
>There is also the DateSelector class which is kind of cool. In
>tdk 2.1, ParameterParser contains some smarts to pull together
>the day, month and year components that DateSelector generates
>to make it really easy to use. I haven't tried to hook this up to
>Intake yet, but it shouldn't be too difficult. The only problem
>is that the smarts in ParameterParser have been ripped out in
>turbine 3.0. This is a shame because this is harder piece of the
>puzzle (generating the three inputs could easily be done with
>a velocimacro, but bringing the parts back together into a
>single Date will have to be done somehow else). Anyone
>working on turbine 3 care to comment?
Yep, I'd be interested to hear what Jason has to say. I tried to engage
him in a discussion as to why this functionality was useful and how it
could be implemented in v3 in a "cleaner" way but he appeared to be more
interested in ploughing ahead with his plans regardless.
I for one am going to need some convincing about v3 to switch my
development over when it comes to be ready to use . Right now v2 meets
most of my needs. At least though we have v2 in its own repository so
there's no barrier to continuing to improve and debug that code, and the
rich functionality it provides.
--
Sean Legassick
[EMAIL PROTECTED]
Je suis un homme: rien d'humain en m'est �tranger
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
