Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »


Groovy is a nice and efficient language and the groovy shell from openmind is a good start, but having groovy support throughout the system would make it even more efficient.


Following some ideas

  • store scripts similar to the templates in the templates workspace
    • or extra workspace, or resources?
  • special property to execute on startup
    • can be used for repairing
  • add support for groovy template/paragraph models
    • make properties accessible in freemarker: model.prop
    • one can select the script in the in-place template's dialog?
  • add support for bean notation for content
    • similar to their xml support
    • content.child.@property
  • add handy closure support
    • content.visit(){..}
  • add builder support
  • add scripted commands
    • make sure that they can be used easily in the observation, schedule and workflow module
    • use case example: archive news & events
  • add the groovy servlet to support scripted servlets
  • add support for data module importers
    • combine the nice xml support with the builder!
  • No labels