|
|
Post by simotek on Feb 22, 2022 5:48:13 GMT
I really should fix that power button :-(
I'm working on a better completely different theme that matches the Vertex GTK theme, with that its possible to have efl gtk and Qt all look the same in a way I like.
That’s one of the biggest battle with theming with edj. Worth it but I don’t think many people know how much work theming is with efl. Although I’ve not really tried getting under the hood with gtk or QT, so maybe I’m wrong. If you want to do more then change colors with Qt you need to write C++ code, I was a Qt app developer for 5 years so i've played with this a little but never enough to do a full theme, really just haven't found the time. If you no how to write C++ making a Qt theme isn't hard its just a very small number of people who know how to write C++ make themes and feel motivated too.
gtk is by far the easiest of the 3 but also the least flexible by a long way (I've made a few partial gtk themes but haven't done heaps since gtk3), its basically just images and a limited version of CSS stylesheets.
|
|
|
|
Post by simotek on Feb 22, 2022 6:21:11 GMT
simotek , nice theme. I always loved your enlightenment themes. It is not a priority for me but I hope to package them for bodhi at some point. At least for the e25 release. e17 had a number of segfault issues. Really alot but I never noticed them until I started working on Moksha's code. I fixed all the ones I found and know about. Most fixed by backporting later enlightenment commits. Yeah by e17.6 alot of the major ones have been fixed and more were related to the code paths that didn't involve running the compositor module which is one of the reasons going compositor only made later versions of e much simpler.
Some of the extra modules were also a major major issue, on openSUSE we didn't ship very many of the extras for example I knew that engage triggered a bunch of crashes all the time so we simply didn't ship it, we had e17.6 on openSUSE for a long time with practically no issues actually being triggered (I think we skipped e18 completely) having a newer efl might have also helped a bit.
|
|
|
|
Post by ylee on Feb 22, 2022 20:52:04 GMT
Yeah by e17.6 alot of the major ones have been fixed and more were related to the code paths that didn't involve running the compositor module which is one of the reasons going compositor only made later versions of e much simpler. Some of the extra modules were also a major major issue, on openSUSE we didn't ship very many of the extras for example I knew that engage triggered a bunch of crashes all the time so we simply didn't ship it, we had e17.6 on openSUSE for a long time with practically no issues actually being triggered (I think we skipped e18 completely) having a newer efl might have also helped a bit.
When Jeff forked e17 one of the first thing he did was strip e17 compositing out of the code. Moksha completely lacks that. This was before I was involved in moksha development but Jeff's rationale was compositing was problematic for us. For one thing on some hardware, it simply did not work. It did not work on a netbook I had then and still have. Half the screen was black and the other half messed up. It was unusable with compositing enabled. I never looked into why nor do I know how well e25 works on it if at all. Might be interesting to try and by now I would be able to at least figure out some of the issues and make a detailed bug report to Raster. So yes the segfaults I found in e17/moksha may indeed have been related to this lack of compositing. Not really worth my time looking over old moksha commits or my notes on the development then to find out for sure. Moksha has went its own way and has been sorta successful for us. |
|
|
|
Post by simotek on Feb 23, 2022 11:25:34 GMT
Yeah by e17.6 alot of the major ones have been fixed and more were related to the code paths that didn't involve running the compositor module which is one of the reasons going compositor only made later versions of e much simpler. Some of the extra modules were also a major major issue, on openSUSE we didn't ship very many of the extras for example I knew that engage triggered a bunch of crashes all the time so we simply didn't ship it, we had e17.6 on openSUSE for a long time with practically no issues actually being triggered (I think we skipped e18 completely) having a newer efl might have also helped a bit.
When Jeff forked e17 one of the first thing he did was strip e17 compositing out of the code. Moksha completely lacks that. This was before I was involved in moksha development but Jeff's rationale was compositing was problematic for us. For one thing on some hardware, it simply did not work. It did not work on a netbook I had then and still have. Half the screen was black and the other half messed up. It was unusable with compositing enabled. I never looked into why nor do I know how well e25 works on it if at all. Might be interesting to try and by now I would be able to at least figure out some of the issues and make a detailed bug report to Raster. So yes the segfaults I found in e17/moksha may indeed have been related to this lack of compositing. Not really worth my time looking over old moksha commits or my notes on the development then to find out for sure. Moksha has went its own way and has been sorta successful for us. Yeah from memory it was related to the fact that alot of the "Extra" modules Bodhi shipped that weren't supported by the core e devs didn't work with the compositor or caused issues with the compositor running. openSUSE got e packages alot later we were able to dodge the issue alot by never having shipped those modules that had been written much earlier in e development and didn't work as well with the compositor. On the other hand Bodhi users were using those modules and didn't want them to go away which left Jeff with much harder decisions then I had.
With the netbook unfortunately they used a really old 32bit intel chipset which used a modified driver which was missing some of the basic opengl functionality that e needed, every other intel CPU/GPU worked fine as did basically every other semi modern GPU driver. So I expect your netbook still probably wouldn't work but that issue is very specific to that chipset. On the other hand e with a compositor runs ok on my old 32bit raspberry pi which has a far slower CPU.
|
|
|
|
Post by ylee on Feb 24, 2022 13:46:17 GMT
... With the netbook unfortunately they used a really old 32bit intel chipset which used a modified driver which was missing some of the basic opengl functionality that e needed, every other intel CPU/GPU worked fine as did basically every other semi modern GPU driver. So I expect your netbook still probably wouldn't work but that issue is very specific to that chipset. On the other hand e with a compositor runs ok on my old 32bit raspberry pi which has a far slower CPU.
Interesting info on the graphics stuff. Yes opengl did not work properly on it. I remember that much. |
|
ligoxi
Crew Member
Posts: 197
Likes: 356
|
Post by ligoxi on Feb 24, 2022 20:34:03 GMT
simotek you are the person on youtube opensuse conference from 2017? I have searched really a lot. This thread and last posts kind of answer to some of my questions about the history of e. I just remembered your video being one very rare case of promoting e on youtube. But i had forgotten it and i just found it again 
|
|
|
|
Post by simotek on Feb 24, 2022 23:06:21 GMT
simotek you are the person on youtube opensuse conference from 2017? I have searched really a lot. This thread and last posts kind of answer to some of my questions about the history of e. I just remembered your video being one very rare case of promoting e on youtube. But i had forgotten it and i just found it again  Yeah that would be me, If you want more history and fun I gave a talk mostly about e16 then a bit of compiz at linux.conf.au a few years back www.youtube.com/watch?v=AzfatESGo24 |
|
