![]() |
|
|
|
|
Change By:
|
Antti Hietala
(04/Apr/13 2:54 PM)
|
|
Description:
|
Document how to work with commands and actions when developing a Magnolia 5 app. Commands and actions is one of the three key concepts that app developers need to know. (The other two are forms & dialogs and the ContentApp framework.)
Tasks:
* Describe how commands are implemented and defined. Use content in http://wiki.magnolia-cms.com/display/DEV/Commands
* Repurpose 4.5 commands documentation where still relevant http://documentation.magnolia-cms.com/technical-guide/commands.html
* Creating reusable commands. An action in another app can use the same command. For example, you may define one activation command and trigger it with different actions in different apps, thus activating different types of content.
* Not all actions need commands. For example, most dialog actions such as "Save" don't need a command. Only some actions delegate the real work to a command such as activation, import and export.
* Import and export are examples of action-command pairs. http://wiki.magnolia-cms.com/display/DEV/Import+Export+Actions Describe them with diagrams in an advanced section of documentation about actions.
* Use Amplify presentation slide 91 to explain the relationship between actions and commands. http://www.slideshare.net/pbaerfuss/magnolia-m5-under-the-hood
* Write a tutorial how to add an action to a basic ContentApp. It builds upon the My first app tutorial.
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
----------------------------------------------------------------
For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html
Alternatively, use our forums: http://forum.magnolia-cms.com/
To unsubscribe, E-mail to: <
[email protected]>
----------------------------------------------------------------
