On 17/09/2009, at 5:00 PM, Q wrote:
> On 17/09/2009, at 4:26 PM, Lachlan Deck wrote:
>
>> Certainly. I'd like to see what using groovy would be like for
>> things like components. I'm not clear on whether wogroovy is
>> needed or not
>
> The bulk of the code in wogroovy are just GJDK style extensions to
> make writing code more convenient and concise, but there is also
> some meta object code included in it that is important when it comes
> to using NS collections because groovy was not selecting the correct
> constructor when doing implicit conversions between native and NS
> collections (from memory). This may or may not be necessary anymore,
> but I believe I created some unit tests in the wogroovy project to
> exercise the issues I found.
>
> That being said wogroovy is totally unmaintained.
okay. You're not (or don't plan on) using it at all?
>> and what the wolips groovy plugin actually does ?
>
> Assuming it still works, all it does is enable the CMD+OPT+[1-5?]
> keyboard shortcuts to jump between component elements when in the
> groovy plugin editor.
Ah, of course.
with regards,
--Lachlan Deck
This archive was generated by hypermail 2.0.0 : Thu Sep 17 2009 - 03:10:02 EDT