|author||Carsten Haitzler (Rasterman) <firstname.lastname@example.org>||2018-03-01 16:44:01 +0900|
|committer||Carsten Haitzler (Rasterman) <email@example.com>||2018-03-01 16:44:01 +0900|
Revert "theme: rename "default" theme to "dark""
This reverts commit d764e0b2790b322778e6db80932c168ae0d43b96. The whole idea of renaming the default theme is an "api break" even if config is changed. and symlinks don't work on windows as a solution. (well on ntfs only as only as administrator, so they don't exist). modifying config for switch from default to dark also will break the case where someone put ~/.elementary/themes/default.edj there and it just is different to the system one and how their theme changes on them as it switches to dark. basically we can't rename a theme like this mid-flight in efl. default is default and has to stay that name. it can change the look, but not the name. i think the apparent reasoning behind this is not a good one. the work on flat is temporary. i don't think we will ever maintain multiple "default themes" as its just far too much work. we can maintain color SCHEMES which are just a list of colorclasses and colors for them - that's separate to a theme and would override. right now these things don't exist. we are not going to create a dark.edj and a light.edj just to store differing default colorclass values. we should be doing the above with colorclass "color palette/scheme/whatever" files that override those named colorclasses globally on init. so reverting because this is an api break and we shouldn't break api unless there is really absolutely no other choice. here the choice is to just temporarily work in a branch and modify default and then merge the branch when done.
Diffstat (limited to 'configure.ac')
1 files changed, 1 insertions, 1 deletions
|@@ -21,7 +21,7 @@ m4_ifdef([AM_SILENT_RULES], [AM_SILENT_RULES([yes])])|
|21||# Due to a bug in automake 1.14 we need to use this after AM_INIT_AUTOMAKE||21||# Due to a bug in automake 1.14 we need to use this after AM_INIT_AUTOMAKE|
|22||# http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15981||22||# http://debbugs.gnu.org/cgi/bugreport.cgi?bug=15981|
|27||#### Apply configuring with legacy api's only, eo api's or both.||27||#### Apply configuring with legacy api's only, eo api's or both.|