Calendar:Deprecated:Build System: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
There are four 'flavours' of calendar living in one tree. xpi-for-suite, xpi-for-toolkit-apps, lighning and thunderbird. A lot of code is shared, but not all. The current build-system is a bit painful, because it isn't really possible to not share code. Sunbird works around it by overwriting files in the jar, and lightning copies a lot. Pain. | There are four 'flavours' of calendar living in one tree. xpi-for-suite, xpi-for-toolkit-apps, lighning and thunderbird. A lot of code is shared, but not all. The current build-system is a bit painful, because it isn't really possible to not share code. Sunbird works around it by overwriting files in the jar, and lightning copies a lot. Pain. | ||
To get a better system, i suggest a calendar/base/resources for shared files, and seperate | To get a better system, i suggest a calendar/base/resources for shared files, and a seperate dir per flavour for forked files. | ||
To get there: | |||
# Move files that obviously should be shared into base. This would be the event dialog, the server properties etc. | |||
# Move files that are not shared into a dir per app. This would be the about screens etc | |||
# Try to use overlays to minimize needed forks. For example, the default would assume toolkit, with <toolbarpalette> and everything. This can be overlayed for xpfe into something that works there. | |||
Revision as of 15:16, 17 April 2005
There are four 'flavours' of calendar living in one tree. xpi-for-suite, xpi-for-toolkit-apps, lighning and thunderbird. A lot of code is shared, but not all. The current build-system is a bit painful, because it isn't really possible to not share code. Sunbird works around it by overwriting files in the jar, and lightning copies a lot. Pain.
To get a better system, i suggest a calendar/base/resources for shared files, and a seperate dir per flavour for forked files.
To get there:
- Move files that obviously should be shared into base. This would be the event dialog, the server properties etc.
- Move files that are not shared into a dir per app. This would be the about screens etc
- Try to use overlays to minimize needed forks. For example, the default would assume toolkit, with <toolbarpalette> and everything. This can be overlayed for xpfe into something that works there.