Changeset 1561 in products for quintagroup.mobileextender


Ignore:
Timestamp:
Jan 15, 2010 10:29:58 AM (11 years ago)
Author:
olha
Message:

README.txt updated.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • quintagroup.mobileextender/trunk/quintagroup/mobileextender/README.txt

    r1559 r1561  
    22============ 
    33 
    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. 
     4quintagroup.mobileextender package is designed for extend Documents, Events and  
     5containers with additional 'Mobile Content' field. This field may contain alternative  
     6content in mobile presentation of the object. 
    77 
    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. 
     8If some content was added to the mentioned field, on object creation and/or edition -  
     9such objects will be marked with qintagroup.mobile.interfaces.IMobile interface.  
    1510 
    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. 
     11Such marked objects are taken into consideration by another Quintagroup product -  
     12qPlongGoogleSitemaps for mobile sitemap creation. There is *Manage Mobile Content*  
     13configlet, aimed to simplify object marking with qintagroup.mobile.interfaces.IMobile  
     14interface, which allows you to mark/unmark object with mentioned inteface. 
    2315 
    24 On installation also registered 'Manage Mobile Content' configlet and  
     16Features 
     17-------- 
    2518 
    26 Installs: using 'Add/Remove Product' section on 'Site Setup' page. 
    27 Depends on: 'archetypes.schemaextender' package. 
     19On product installation *mobile_extender* File system directory view is added to  
     20portal_skins, which contains alternative views for document, events and containers. 
     21 
     22But this layer will not be not added to the existent theme by default settings,  
     23because it might lead to changing presentation of mentioned objects with data from  
     24'Mobile Content' field, or in case it is empty - from the 'Text' field.  
     25 
     26So, to apply mentioned behavior you should manually add 'mobile_extender' layer to the  
     27theme, you intent to use as mobile one, just after 'custom' layer. 
     28 
     29Also, after installation 'Manage Mobile Content' configlet is registered. 
     30 
     31Requirements 
     32------------ 
     33 
     34 * Plone 3.x 
     35 
     36Dependency 
     37---------- 
     38 
     39 * archetypes.schemaextender 
     40 
     41Authors 
     42------- 
     43 
     44 * Anriy Mylenkyi 
     45 * Volodymyr Cherepanyak 
Note: See TracChangeset for help on using the changeset viewer.