On 17/09/2009, at 4:26 PM, Lachlan Deck wrote:
> On 17/09/2009, at 3:46 PM, Q wrote:
>
>> On 17/09/2009, at 3:01 PM, Lachlan Deck wrote:
>>
>>>> So you don't have to have sleepless nights over deadlocks when
>>>> using concurrent request handling :)
>>>
>>> unless, I imagine, the libraries you primarily depend on are
>>> themselves not written in scala(?)
>>>
>>>> Now, developing and deploying more ambitious Web 2.0 UI is a
>>>> possibility...
>>>
>>> I am interested in Groovy in particular, Quinton, as it does have
>>> reasonably decent tool support nowadays. (It appears that Scala
>>> does too: http://www.scala-lang.org/node/94)
>>
>> I need to have another look at groovy, and how far its eclipse
>> support has come since the last time I tried it.
>
> Okay. Let me know either way.
>
>>> So... I'm happy to look into updating the new Component/View
>>> wizard for wolips to creating the component class in alternate
>>> languages (if desired) as that seems to me to be the primary
>>> obstacle to utilising these two languages with WOLips (is that
>>> what you meant Quinton?).
>>
>> The lack of support in the wizards is more an inconvenience, than
>> an obstacle that would prevent you using scala or groovy.
>
> Sure - though it would be a hassle.
>
>> I wouldn't be in a rush to support such things in wolips unless you
>> are actually using them yourself ongoing, else they will likely
>> wither on the vine.
>
> 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.
> 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.
-- Seeya...QQuinton Dolan - qdola..mail.com Gold Coast, QLD, Australia (GMT+10)
This archive was generated by hypermail 2.0.0 : Thu Sep 17 2009 - 03:01:29 EDT