• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: WO and alternative languages was Re: WWDC
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: WO and alternative languages was Re: WWDC


  • Subject: Re: WO and alternative languages was Re: WWDC
  • From: Q <email@hidden>
  • Date: Mon, 18 Jun 2007 14:29:54 +1000


On 18/06/2007, at 1:45 PM, Lachlan Deck wrote:

On 18/06/2007, at 12:43 PM, Q wrote:

Speaking of which, I've played around with WOGroovy and I was pretty
impressed with it. After a somewhat rocky start, Groovy has become
reasonably mature and WOGroovy seems to work well. It's also a relatively
small project, which is reassuring. If it was some huge messy framework I
would be worried about adopting it and then hitting a wall halfway through a
project because of some hard to track down bug, but given it's simplicity, I
think it would be fairly straightforward to track down and fix any bugs that
might've been overlooked by the developer. All in all, it seems like an
excellent and very useful framework.

That developer would be me. If you have any issues feel free to let me know. ;)

Good to know. I hadn't heard of WOGroovy until this morning and had recently been looking at incorporating Groovy for the purposes of rapid turnaround.

The original version of WOGroovy was written by Suzuki Tetsuya, and lives here http://wogroovy.sourceforge.jp but hasn't been updated in a long time.


I basically rewrote it reusing most of the original metaclass helper code, removed the xcode requirement, and added rapid turnaround using the groovy class loader. My version is available online here: http:// code.google.com/p/wogroovy
You will need to check it out of the repository.



As you have observed WOGroovy is a very small veneer to make using groovy with WebObjects seamless. Outside the rapid turnaround code, which is just some classloader magic, the WOGroovy framework itself doesn't actually do much but inject some helper categories into the metaclass registry. The fixes for the NS* collection handling are the only really important bits, and they don't need to be "loaded", they just need to be in the classpath somewhere.

Do you have any example projects (intermixing standard java and groovy)?

Not really, in the source tree there is a small example app I started as a test case to exercise some of the collection handling, and demonstrate some of the implicit functions added by the WOGroovy categories. But I haven't done anything with it for a little while.


--
Seeya...Q

Quinton Dolan - email@hidden
Gold Coast, QLD, Australia
Ph: +61 419 729 806


_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >WWDC (From: Don Guernsey <email@hidden>)
 >Re: WWDC (From: Dana Kashubeck <email@hidden>)
 >Re: WWDC (From: Marc Guenther <email@hidden>)
 >Re: WWDC (From: Simon McLean <email@hidden>)
 >Re: WWDC (From: Q <email@hidden>)
 >Re: WWDC (From: Damien Petrilli <email@hidden>)
 >RE: WWDC (From: "Bruce Fancher" <email@hidden>)
 >WO and alternative languages was Re: WWDC (From: Q <email@hidden>)
 >Re: WO and alternative languages was Re: WWDC (From: Lachlan Deck <email@hidden>)

  • Prev by Date: Re: WWDC photos (WebObjects Lab + Bash)
  • Next by Date: Re: Duplicate objects in a relationship
  • Previous by thread: Re: WO and alternative languages was Re: WWDC
  • Next by thread: Re: WWDC
  • Index(es):
    • Date
    • Thread