04-10-2013 04:46 PM
Is there any documentation available for SPAM development? I think Benjamin had metioned that there might be some documentation kicking aorund somewhere?
04-22-2013 09:59 AM
APM.
We can drop the 'S'.
It is possible to add extended functionality to SAPM without any changes to the core product. This is done by following the conventions of ASP.NET MVC. The following steps will create a page for use in SAPM.
To access the newly added page the existing view files (.cshtml) have to be modified. For example, to add a link on the home page to the new plugin page, a new li element must be added to APFW\Views\Home\Index.cshtml with a link to the MyPlugin page.
Cons:
SAPM is a Single Page Application. That means that page changes are retrieved via ajax and inserted into the DOM rather than replace it. So any css or javascript stays in effect across page changes. This makes it very easy for any styling or script that the add-on adds to have an impact on the entire application. So if the add-on isn’t thoroughly tested it can cause defects in our sections of the app.