Changes between Version 19 and Version 20 of BluePrint/Plugins

Timestamp:

06/21/13 23:11:09 (12 years ago)

Author:

Fran Boon

Comment:

--

BluePrint/Plugins

@@ -14 +14 @@
 
 === Developer ===
-The Developer wishes to be able to develop new functionality which extends a base Eden install without needing to have anything added to trunk. +++
-* e.g. Their feature involves something confidential to the site. ++
+The Developer wishes to be able to develop new functionality which extends a base Eden install without needing to have anything added to trunk.
+* e.g. Their feature may involve something confidential to the site.
+* e.g. Their feature may not be seen as relevant to core Eden.
+* e.g. Their feature may not be seen as robust enough for core Eden.
 
 This functionality may include:
 * Modules
  * Models
-  * This may require the most work
  * Controllers
-  * These will be available in the co-app namespace
 * [DeveloperGuidelines/Templates Template]
  * Settings
@@ -28 +28 @@
  * Controller Customizations
  * Parsers
- * 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
 * [DeveloperGuidelines/Themes Theme]
  * Views
  * CSS
- * 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
 * Widgets
- * Widgets can already be defined in Templates
- * Applying the Widgets to existing modules would be done in controller customizations in Templates
- * The value comes if the Widget is to be easily shared with the rest of the community
+
+=== Note ===
+We can actually keep a lot of stuff out of trunk very easily already:
+* Templates can be added to .gitignore
+* Themes can be added to .gitignore
+* Views can already be defined in Templates & Themes
+* Widgets can be defined in Templates
+* Applying Widgets to existing modules would be done in controller customizations in Templates
+
+The value comes if we want to be able to easily share these customisations back to the wider community
+
 ==== New data ====
 * 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. +++
 * A site needs to add a new 1-N component to go with an existing primary resource. +++
 
-These can be done with a Model and a custom crud_form in the customize_ section of the Template
+These can be done with a Model and a custom crud_form in a customize function in the Template
 
 ==== New functionality ====
@@ -60 +66 @@
 * S3Menu to be extended to read the settings & add additional menu entries found in those folders
  * Templates which don't use S3Menu will not support these, but that's seen as a bug in these templates
+* S3Model to be extended to be able to conditionally load models from the co-app
+* Controllers in the co-app will be easily available
 
 === Future extensions ===