[ http://jira.magnolia.info/browse/MAGNOLIA-635?page=all ]
Boris Kraft reassigned MAGNOLIA-635:
------------------------------------
Assignee: Philipp Bracher (was: Boris Kraft)
> Using rhino (javascript) for configuration, scripting, shell
> ------------------------------------------------------------
>
> Key: MAGNOLIA-635
> URL: http://jira.magnolia.info/browse/MAGNOLIA-635
> Project: magnolia
> Issue Type: Sub-task
> Affects Versions: 3.5
> Reporter: Philipp Bracher
> Assigned To: Philipp Bracher
> Fix For: 3.5
>
>
> Since some days I'm thinking about using rhino (javascript) to make magnolia
> customizable.
> Now I like to get some feedback form the audience before I think farther.
> Primar thoughts:
> - our main developers are weboriented and know javascript
> - If something is configured in a scripting language it is very felxible
> - It reduces the abstract step to a configuration file like xml
> - You can adapt functions (like the activation) without downloading the
> sources
> Configuration
> -------------
> The startup script is written in javascript and if you need to instantiate an
> other cache-handler for example you just do
> it by changing this startup file.
> Let's call this IoC by scripting ;-)
> Changing Execution
> ------------------
> Methods like activation could be extracted to a script like activate.js which
> one could adapt without subclassing.
> Shell
> -----
> We could include Rhinos shell this would it make easy to analyze data:
> - dump data
> - change data
> - queries
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://www.magnolia.info/en/magnolia/developer.html
----------------------------------------------------------------
