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 | |
| 16 | Not 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 | |
| 20 | 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. +++ |
| 21 | |
| 22 | A site needs to add a new 1-N component to go with an existing primary resource. +++ |
| 23 | |
| 24 | === New functionality === |
| 25 | |
| 26 | A 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 | |
| 30 | A 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 | |
| 34 | The admin wants to be able to browse a repository of plugins, viewing their names, descriptions, social rating, who maintains them. ++ |
| 35 | |
| 36 | Installation should be no harder than installing a Web2py application, plus some configuration editing. ++ |
| 37 | |
| 38 | Pie in the sky: They may wish to be able to click on a plugin to easily install them into their running instance of Eden. + |