Changes between Version 10 and Version 11 of BluePrint/Plugins


Ignore:
Timestamp:
06/21/13 19:34:23 (12 years ago)
Author:
Pat Tressel
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BluePrint/Plugins

    v10 v11  
    1111
    1212Plugins also provide an outlet for frustrated wannabe Eden devs who can't get their features accepted into trunk, and those who want to use Eden for a somewhat non-target use. (They'll let me add a kanban module, so I have someplace to point a kanban phone app. --Pat)
     13
    1314== Use-Cases ==
    14 === End-User ===
    15 The End-User wishes to be able to browse a repository of plugins, viewing their names, descriptions & who maintains them. They wish to be able to click on a plugin to easily install them into their running instance of Eden.
     15
     16Not all of these are equally likely to be requested and used, or deemed necessary. The items are ranked +++ highest likely need, down to + not particularly urgent, shown following the proposed use case.
     17
     18=== New data ===
     19
     20A 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. +++
     21
     22A site needs to add a new 1-N component to go with an existing primary resource. +++
     23
     24=== New functionality ===
     25
     26A site needs an entire new module with model / controller / view, that yet makes use of existing tables, including having them as components. +++
     27
     28=== Modified UI ===
     29
     30A site wants to match the look and feel of other tools they use, including types of widgets. E.g. they may want to replace the map viewer with one that they use in another application. + because this is handled by templates and that functionality is working. However, if we can make templates into plugins, we would not need to store everyone's templates in trunk. In that case, +++
     31
     32=== Delivery ===
     33
     34The admin wants to be able to browse a repository of plugins, viewing their names, descriptions, social rating, who maintains them. ++
     35
     36Installation should be no harder than installing a Web2py application, plus some configuration editing. ++
     37
     38Pie in the sky: They may wish to be able to click on a plugin to easily install them into their running instance of Eden. +
    1639
    1740=== Developer ===
    18 The Developer wishes to be able to develop new functionality which extends a base Eden install without needing to have anything added to Trunk.
     41
     42The Developer wishes to be able to develop new functionality which extends a base Eden install without needing to have anything added to trunk. +++
     43
     44They may want this for any of several reasons:
     45
     46Their feature involves something confidential to the site. ++
     47
     48----
     49(Following to be updated.)
    1950
    2051This functionality may include: