Confirmed users
1,041
edits
Extension Dependencies: Difference between revisions
Jump to navigation
Jump to search
m
→User Interface
m (→Overview) |
m (→User Interface) |
||
| Line 52: | Line 52: | ||
'''Future:''' Just as the minVersion and maxVersion for application compatibility is automatically updated via the rdf specified in the item's updateURL the minVersion and maxVersion for an em:requires should also be updated automatically. Since this is version specific information adding and removing em:requires would not be supported since that should only occur during a version upgrade and not a compatibility update. | '''Future:''' Just as the minVersion and maxVersion for application compatibility is automatically updated via the rdf specified in the item's updateURL the minVersion and maxVersion for an em:requires should also be updated automatically. Since this is version specific information adding and removing em:requires would not be supported since that should only occur during a version upgrade and not a compatibility update. | ||
== User Interface == | == User Interface == | ||
Items that are disabled due to dependencies not being satisfied would have the same available commands as an incompatible item. In addition to these commands they would also have the option to bring up the dialog used during install for installing the extensions specified in em:requires that are currently not installed or enabled on their system. | Items that are disabled due to dependencies not being satisfied would have the same available commands as an incompatible item. In addition to these commands they would also have the option to bring up the dialog used during install for installing the extensions specified in <tt>em:requires</tt> that are currently not installed or enabled on their system. | ||
== Application Startup == | == Application Startup == | ||
When operations are needed (e.g. needs-install, needs-upgrade, etc.) after the operations are completed all enabled items with dependencies will have their dependencies verified and the item's autoDisabled property will be set accordingly. | When operations are needed (e.g. needs-install, needs-upgrade, etc.) after the operations are completed all enabled items with dependencies will have their dependencies verified and the item's autoDisabled property will be set accordingly. | ||