You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jun 7, 2024. It is now read-only.
mlist edited this page Apr 12, 2013
·
10 revisions
AddinModules are considerably simpler than operations or tabs since they are in first instance independent of domain classes. Like all content modules they have to be placed under grails-app/modules. They need to provide a class implementing the interface AddinModule, as well as a view template to render. The view template should begin with an underscore and be located under grails-app/views/addins. Let's look at an example:
packageorg.openlab.module.addinimportorg.openlab.module.*;
classGeneLegendAddinModuleimplementsAddinModule{
//the name of the add-in will be displayed for selection in the user settingsdefgetName()
{
"gene legend"
}
//the name of the templatedefgetTemplate()
{
"geneLegendAddin"
}
//the name of the grails-plug-in corresponding to the OLF module//used for locating the templatedefgetPluginName()
{
"gene-tracker"
}
}