On Sat, 4 Sep 2021 16:42:19 +0100 Peter Flynn <pe...@silmaril.ie> said:
> Many years ago I and others asked if there was a config option to move > the ☒ 🗖 🗕 icons (close–max–min) from the right top corner of all > windows to the left top corner. > > At the time, the only possibility was to decompile the theme, change thr > script, and recompile. > > Are there any plans to implement this in the config? same answer. :) make a theme that does that. every time someone wants a new customization option means themes have to be designed with both layouts in mind and need a signal to tell it which one to use. that increases the workload for the theme maker. themes are already prohibitively massive in scope. you are asking to make them yet-more-massive. the problem is they are massive as a result of year after year of "just add one more thing". i am putting my foot down and focusing on ways of simplifying or if i am to add anything it had better be MAJORLY useful in massive ways to justify the work. i actually want to cut down what is in themes if i can, not increase it. i know this is not what you want to hear. :( it's me trying to have you understand that i'm making a trade off here. a full theme for efl+e is larger that most apps you use. the default them fort efl is 71,000 lines of theme source. that doesn't include images etc. themselves - just the edc. the sourcecode for terminology (one of the largest efl apps other than e) is 45,000 lines of code. rage (video player) is 7,000 lines of code. ecrire is 1,700. entice is 2800. evisum is 11,000. you don't see a lot of themes for e/fl today because doing a theme is a monumental amount of work. very few would bother and this makes me want to really REDUCE the work, not increase it. I'm redoing colorclasses now. this doesn't actually add work. it's just fixes existing lines that declare a cc for an element. it's better structured. it does include more cc's in a master cc list and then a parent tree to simplify it. i am hoping people just c&p that in and follow the same scheme. but this allows users to select their own colors (eg dark, light, pink, purple, green, yellow, etc.) and will allow users to have a very simple way to say "i hate dark - give me light" (or pink or purple or green and combinations of these). thus the value is very very high to lots of users but the effort in a theme is very very low. the value of "controls at top-left option" is doubtful - fairly low and only for a few people is this really needed or REALLY wanted, but the effort is fairly high as quite a few groups need quite extensive re-thinking to handle both cases. so my argument here is the math for effort vs reward with a goal of simplifying themes makes it a "no" on my list. :( sorry to bear the bad news. BUT... you can happily do a theme and modify it to do this. i'm not stopping you. nothing is. BUT making it now a requirement of themes to go support is putting the burden not on you - the one who wants it but everyone else trying to make themes who may have no desire to have it.. :) -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
