[754] | 1 | Introduction |
---|
| 2 | ============ |
---|
| 3 | |
---|
[1559] | 4 | This package designed for extend Documents, Events and containers with additional |
---|
| 5 | 'Mobile Content' field. This field may contains alternative content in mobile |
---|
| 6 | presentation of the object. |
---|
[754] | 7 | |
---|
[1559] | 8 | On creation and/or editing an object, if some content added to mentioned field, - |
---|
| 9 | object marks with qintagroup.mobile.interfaces.IMobile interface. Object marked |
---|
| 10 | with this interface take into consideration by other Quintagroup product - |
---|
| 11 | qPlongGoogleSitemaps for mobile sitemap creation. For simplifying object marking |
---|
| 12 | with qintagroup.mobile.interfaces.IMobile interface there is |
---|
| 13 | *Manage Mobile Content* configlet, which alows you to mark/unmark object with |
---|
| 14 | mentioned inteface. |
---|
| 15 | |
---|
| 16 | On installation to portal_skins added *mobile_extender* File system directory |
---|
| 17 | view, which contains alternative views for document, events and containers. |
---|
| 18 | But this layer not added to existent themes by default because it lead to |
---|
| 19 | changing presentation of mentioned objects with data from 'Mobile Content' |
---|
| 20 | or if it empty - from the 'Text' field. So to apply mentioned behavior you |
---|
| 21 | should add manually 'mobile_extender' layer to theme, which you design to use as |
---|
| 22 | mobile one, just after 'custom' layer. |
---|
| 23 | |
---|
| 24 | On installation also registered 'Manage Mobile Content' configlet and |
---|
| 25 | |
---|
| 26 | Installs: using 'Add/Remove Product' section on 'Site Setup' page. |
---|
| 27 | Depends on: 'archetypes.schemaextender' package. |
---|