forked from maqetta/maqetta
-
Notifications
You must be signed in to change notification settings - Fork 0
Configurable libraries
JonFerraiolo edited this page Jul 3, 2012
·
1 revision
This page provides strawman proposals for how to support multiple widget libraries and multiple versions of widget libraries.
- User chooses which libraries and which particular versions of libraries to use in his compositions
- (MUST) User can pick libraries/versions for a particular project
- (NICETOHAVE) User can pick libraries/versions for a particular HTML file
- NOTE: we already allow user to pick which theme(s) they want to use
- Admin chooses which libraries and which particular versions of libraries to make available to his users
- (MUST) Admin can include/exclude particular libraries/versions
- (MUST) Admin can include/exclude particular themes
- Custom libraries/versions/themes
- (MUST) Need to support both standard libraries/versions/themes (e.g., Dojo) or custom libraries/versions/themes (i.e., widgets and themes developed by a particular organization)
- (MUST) New project dialog
- Ability to choose which libraries to use in a given project - probably share same or similar UI with modify libraries dialog
- (NICETOHAVE) New file dialog
- Ability to choose which libraries to use in a given file. Note that we already auto-include libraries when adding a widget from that library based on widget metadata. This item means allowing user to include a library even if no widgets are added from that library.
- (MUST) A configuration file that defines which libraries to use. Similar to PROJECT/.settings/libs.settings (see below)? ``