update to Groovy 1.8?

[dansmith65]

I'd like to use the new native JSON support in Groovy 1.8. Any chance of an update to ScriptMaster?

http://docs.codehaus.org/display/GROOVY/Groovy+1.8+release+notes

[john renfrew]

Plus one from me on 1.8 for the same reason as Dan - JSON slurper

[Russell Barlow]

+1 to this request. Same reason, JSON slurper.

[john renfrew]

Any progress on this??

Please

[john renfrew]

And now can that request be updated to 1.8.1

Why?

Take() and Drop()

FindAll on ALL objects which match Groovy truth

sort() reverse() unique() with Boolean switch to keep original list/map and return new one

additions to groupBy()

and JSON slurper we are still missing from earlier

[Jesse Barnum]

Groovy 1.8.1 is not released yet. If you'll post a reminder on here when that is shipping, I'll go ahead and update ScriptMaster with that (I don't want to do 1.8 now if 1.8.1 is imminent).

[john renfrew]

Thanks very much Jesse...

It is there at: http://groovy.codehaus.org/Download

Stable Releases: Groovy 1.8

Groovy 1.8 is the latest and current stable branch.

The latest version of that branch is Groovy 1.8.2.

[NovaChan]

+1 for Groovy with native JSON support in ScriptMaster. I see they're up to 1.8.4 now. Just so you know there's one more in the following for this. Thanks!

[wbasham]

For anyone still following this thread...

ScriptMaster 4.13 has just been released and it includes Groovy 1.8.5. Sorry it took so long. :smile:

[Larry Goldman]

ScriptMaster 4.13 is broken. To see for yourself, open ScriptMaster sample file, try to run "Access the FileMaker Calculation Engine Part 3". Result:

java.lang.IllegalStateException: FileMaker called plugin on thread: Thread[AWT-AppKit,5,main]; but plugin is trying to call back to FileMaker on a different thread: Thread[AWT-EventQueue-0,6,main]. This is not allowed.

[Larry Goldman]

Furthermore, I find that when using Filemaker 11 on either Windows or Mac systems, to revert the version of ScriptMaster being used, I have to look in:

~/Library/Application Support/Filemaker/Extensions (Mac OS X)

C:Users<username>AppDataLocalFileMakerExtensions (Windows 7)

Replacing Scriptmaster in /Applications/Filemaker Pro11/Extensions is not sufficient.

[David Wikström]

Just to confirm that I can reproduce this too...

[Jesse Barnum]

Hi Larry, thanks for reporting the problem - ScriptMaster 4.131 is now released to fix that specific issue.

The second issue you're talking about is the way plug-ins are designed to work with FileMaker; that location is the auto-update folder. Plugins installed via auto-update are put in that location, and take priority over plug-ins installed in the application directory. I wish Apple had not decided to make that folder hidden in OS X 10.7 Lion, it used to be visible.

ScriptMaster 4.13 is broken. To see for yourself, open ScriptMaster sample file, try to run "Access the FileMaker Calculation Engine Part 3". Result:

java.lang.IllegalStateException: FileMaker called plugin on thread: Thread[AWT-AppKit,5,main]; but plugin is trying to call back to FileMaker on a different thread: Thread[AWT-EventQueue-0,6,main]. This is not allowed.

[Ocean West]

If there are custom plugins created with ScriptMaster Advance, is it necessary to have these upgraded as well to include the upgrade to Groovy?

[wbasham]

The new version of Groovy is important for development as opposed to deployment. There is no need to regenerate existing plugins.

[wbasham]

It has been brought to our attention that another module "Access the FileMaker Calculation Engine Part 1" resulted in an IllegalStateException when executed. This has now been fixed. However, we are not currently doing a live deploy of ScriptMaster. If anyone needs this module for development, please contact me via email ([email protected]) and I'll be happy to send you the modified plugin. The change will also be reflected in the next deployment of ScriptMaster.