nickvergessen wrote:You can create your own project if you want to. However we will always have a style included and need it so we can develop it.
keith10456 wrote:IMO it makes sense to always have at lease 1 default theme included.
your missing the point maybe I am not saying that the theme should not be included. I am saying that we should maintain its own development project and include the stable version of that in the main phpbb project.
nickvergessen wrote:It makes no sense to move it to a separate project as most patches require backend and front-end changes.
Only in the confines of an existing theme! There will be a lot of changes/pulls/bugs with a new theme which deal solely with the HTML/CSS/JS
No because I do not develop a theme to fit a back-end! If its truly abstracted I would develop a theme to meet the needs of the content/UX/UI. Then turn around and make sure the backend has everything I need.
Look I am completely open to suggestion on how best to handle this.
The main problems with the current way that I have are as follows.
1. The concept of development vs production themes. A development version of the theme somehow needs to be maintained. I can elaborate more on this if need be.
2. The current method of tracking the development and progression of the theme is diluted in the confines of the entire projects scope. It is not easy to only see/track changes,bugs,issues only related to the HTML/CSS/JS layer
3. Their are several resources that are required for development on the front-side that we may not want to ship but should be maintained within the confines of the theme. Add these to the already complex directory structure of phpbb along with a more suited development break-out of content and your file base can become astronomical.
4. Currently if their is a bug or issue with the theme that might be an easy fix we have to either wait for a completely new release of phpbb to publish said fix. When dealing with the front-end these can pile up fairly quickly.
5. A change that only affects the front-end with no changes to the back-end is not easily understood for those testing/developing since they usually get merge with unrelated merges of back-end changes.
If you have suggestions on how to resolve these without some sort of separation I am open to them.