Changes between Version 11 and Version 12 of BluePrint/Plugins
- Timestamp:
- 06/21/13 22:49:17 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
BluePrint/Plugins
v11 v12 27 27 28 28 === Modified UI === 29 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, +++ 29 30 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 Note: It is very easy already to have a template kept out of the main repo via a .gitignore so this seems lower priority to Fran 31 32 32 33 === Delivery ===