Changes between Initial Version and Version 1 of Ticket #22316, comment 58
- Timestamp:
- 12/29/2012 11:21:21 PM (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #22316, comment 58
initial v1 1 1 SUMMARY PROPOSAL: 2 2 3 1.- plugin-dependencies (w/ versioned dependencies and theme dependencies) into core 4 2.- Class Loader (we can certainly even use the UniversalClassLoader from Symfony here) into core 3 1. plugin-dependencies (w/ versioned dependencies and theme dependencies) into core 5 4 6 3.- "Library" plugins have one index.php file which just registers their (sub-)namespace with the ClassLoader. All later loading is demand-based. The declare "Provides:" and "Version:" à la Debian 5 2. Class Loader (we can certainly even use the UniversalClassLoader from Symfony here) into core 7 6 8 4.- Functionality plugins work as usual (perfect backwards compatibility), though they can (and should, IMHO) use "libraries" when possible. They declare dependencies if at all posible, so that we can fail gracefully if pre-conditions are not met (as opposed to just WSOD'ing) 7 3. "Library" plugins have one index.php file which just registers their (sub-)namespace with the ClassLoader. All later loading is demand-based. The declare "Provides:" and "Version:" à la Debian 9 8 10 5.- Themes can optionally depend on certain functionalities to be present (via de same "Depends" mechanism). The theme chooser UI would need to be refreshed to include some feedback for this, though. 9 4. Functionality plugins work as usual (perfect backwards compatibility), though they can (and should, IMHO) use "libraries" when possible. They declare dependencies if at all posible, so that we can fail gracefully if pre-conditions are not met (as opposed to just WSOD'ing) 10 11 5. Themes can optionally depend on certain functionalities to be present (via de same "Depends" mechanism). The theme chooser UI would need to be refreshed to include some feedback for this, though. 11 12 12 13