Changes between Version 19 and Version 20 of BluePrint/Plugins


Ignore:
Timestamp:
06/21/13 23:11:09 (8 years ago)
Author:
Fran Boon
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Plugins

    v19 v20  
    1414
    1515=== Developer ===
    16 The Developer wishes to be able to develop new functionality which extends a base Eden install without needing to have anything added to trunk. +++
    17 * e.g. Their feature involves something confidential to the site. ++
     16The Developer wishes to be able to develop new functionality which extends a base Eden install without needing to have anything added to trunk.
     17* e.g. Their feature may involve something confidential to the site.
     18* e.g. Their feature may not be seen as relevant to core Eden.
     19* e.g. Their feature may not be seen as robust enough for core Eden.
    1820
    1921This functionality may include:
    2022* Modules
    2123 * Models
    22   * This may require the most work
    2324 * Controllers
    24   * These will be available in the co-app namespace
    2525* [DeveloperGuidelines/Templates Template]
    2626 * Settings
     
    2828 * Controller Customizations
    2929 * Parsers
    30  * Note: It is very easy already to have a Template kept out of the main repo via a .gitignore, so the value comes if the Template is to be easily shared with the rest of the Community
    3130* [DeveloperGuidelines/Themes Theme]
    3231 * Views
    3332 * CSS
    34  * Note: It is very easy already to have a Theme kept out of the main repo via a .gitignore, so the value comes if the Theme is to be easily shared with the rest of the Community
    3533* Widgets
    36  * Widgets can already be defined in Templates
    37  * Applying the Widgets to existing modules would be done in controller customizations in Templates
    38  * The value comes if the Widget is to be easily shared with the rest of the community
     34
     35=== Note ===
     36We can actually keep a lot of stuff out of trunk very easily already:
     37* Templates can be added to .gitignore
     38* Themes can be added to .gitignore
     39* Views can already be defined in Templates & Themes
     40* Widgets can be defined in Templates
     41* Applying Widgets to existing modules would be done in controller customizations in Templates
     42
     43The value comes if we want to be able to easily share these customisations back to the wider community
     44
    3945==== New data ====
    4046* A site wants to add fields to an existing primary resource, and have them show up in the primary resource's Basic Details form. These will be 1-1 with the primary resource records. +++
    4147* A site needs to add a new 1-N component to go with an existing primary resource. +++
    4248
    43 These can be done with a Model and a custom crud_form in the customize_ section of the Template
     49These can be done with a Model and a custom crud_form in a customize function in the Template
    4450
    4551==== New functionality ====
     
    6066* S3Menu to be extended to read the settings & add additional menu entries found in those folders
    6167 * Templates which don't use S3Menu will not support these, but that's seen as a bug in these templates
     68* S3Model to be extended to be able to conditionally load models from the co-app
     69* Controllers in the co-app will be easily available
    6270
    6371=== Future extensions ===