On 02/04/15 22:46, Simon Lees wrote: > > > On 04/01/2015 11:48 PM, Tom Hacohen wrote: >> On 01/04/15 00:54, Andrew Williams wrote: >>> Hi all, >>> >>> Please excuse the somewhat random / rambling email but I've been thinking >>> more about E17/E18 etc theming, sharing of custom setups and release cycles >>> and the impact they have on the E user community and potential new users. >>> >>> E17 may have been a long time in the making but during that period we were >>> able to create and run (two different?) theme / background support sites >>> that proved to be very popular. They were a great way share content, get >>> updates and also to promote the beautiful desktop phenomenon that was the >>> future of Enlightenment. More recently conversations have been brought up >>> around config sharing or promoting desktop setups - I love that as an >>> extension to what has worked in the past and I've seen it hook new users on >>> other systems. >>> >>> In the new regular release cycle of E18/E19 etc (which has a huge number of >>> benefits) it's much harder to point people at a place to get themes and >>> even to manage the custom themes you downloaded as the version bumps can >>> break what you've got. On community supported sites it's harder to manage >>> this upgrade cycle and from what I've seen this could have contributed to >>> many places still having the most popular themes being for E17 and not >>> later versions. >>> >>> Another related topic of conversation that's been floating around for a >>> while is Marrakesh - or the more general topic of how to we distribute our >>> apps easier to many different platforms. Is this actually a new problem or >>> is it related and we've just managed to avoid it due to great sites like >>> exchange and get-e? >>> >>> And so to my point. As we approach the landmark version number of E20 is >>> there an opportunity to draw a line in the sand from which point forward we >>> can better support themes, their upgrade paths and their sharing / >>> installation? >>> What I wonder is this. Can we create, sponsor or simply endorse a central >>> site for (initially) theme sharing etc that would be better integrated into >>> the environment either by creating a native desktop app or even integrating >>> it into theme selection dialogs etc so discovery is a breeze? If we take >>> this opportunity to create a "LTS" or "stable" theme base then it would be >>> on us, rather than every themer, to ensure that future upgrades to Edegrade >>> somewhat gracefully if an out of date theme is selected. As something >>> better tied to the core product there would be an opportunity to manage >>> version requirements, integrate config sharing or whatever the next cool >>> thing is and build all of this out ahead of the full dream of app >>> distribution through our own delivery mechanism. >>> >>> I could be way off the mark here but I think this could help to increase >>> engagement whilst giving us a little more exposure / experience with an >>> "app store" like system for distributing / engaging / promoting our work. >>> Additionally the web frontend could be a great showcase of the cool things >>> that E enables beyond the current screenshot setup and less up to date >>> external theme sites. >>> >>> Thanks for sticking with me through the long post - I hope some of it is >>> interesting. Apologies if this steps on previous threads - I've been away >>> from the group for a while but hoped the outsider returning's point of view >>> could be useful :-) >> I clarified it on the ML a few months back. E19 themes will no longer >> break. You can feel free to theme whatever you want, and you can be sure >> these themes will work. I don't remember if this also applies to E18 >> themes, or just since the E19 release. > There is some changes between e18 themes and e19, mostly around the > compositor and parts being moved around, menu's won't work with e18 > themes in e19 for example, there are also several new modules in e19 but > it wasn't hard to. Between e18 and e19 most of the text colors and some > others were also changed from being hard coded everywhere to being > defined. I don't remember if a e19 theme will work with e18 I'm guessing > there may be issues for similar reasons. > > So far I haven't seen any changes for e20 that would make full e19 > themes not work. There was a lot of e18 and maybe e19 themes that just > had the default elementary theme and a custom enlightenment theme, for > e20 these themes won't work without implementing the elementary part. > There is also the risk that people developing for e20 will miss parts in > e19, but I guess thats for theme devs to deal with. > > > Looking in the history for my git repo's I did the conversion from e18 > to e19 in the following 2 commits, I don't remember which elementary > version had the first e18 theme vs the first e19 theme. > > https://github.com/simotek/Enlightenment-Themes/commit/397aefd4e2fb66a3ed4603ec4d58aa0c9147acc0 > https://github.com/simotek/Enlightenment-Themes/commit/bdd070b51c0b49276ec4073ed72ee0d0a2d77c1e > > Then there was another 2 commits for efl 1.10 and 1.11, I haven't pulled > changes since then (e19 was released with efl 1.11) > https://github.com/simotek/Enlightenment-Themes/commit/8408a90b158abf8944b3711361003ee1827f22b7 > https://github.com/simotek/Enlightenment-Themes/commit/e878197ee3e546bcdae188059c33732cd260586e > > The full change is > https://github.com/simotek/Enlightenment-Themes/compare/e18...master#files_bucket > which is the diff between my e18 and master branch (Note there is a > large number of changes related to my build scripts in there) >
You are right. E19 obviously broke everything with the compositor rewrite. E19 onwards is stable, apart of as I said, implementing the Elm part of the theme, which was kinda required before too, as elm usage was allowed. -- Tom. ------------------------------------------------------------------------------ BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT Develop your own process in accordance with the BPMN 2 standard Learn Process modeling best practices with Bonita BPM through live exercises http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
