Yo

Welcome to the forums dude. It’s great to see you again!

Glad to see you have officially joined the forums


OK, yes Moksha is a fork of e17. When Jeff made the fork, e18 and e19 were judged by Jeff to unstable for Bodhi as well as had various issues that had caused us problems with e17. One being compositing which did not work with all hardware, but in later versions of enlightenment, one could not really disable compositing fully. Jeff and one or two others helping him stripped everything out of e17 that was deemed buggy or problematic for some of our users as well as backported some need e18/e19 backports. I did not take part in that at the time and did not really do much at all with Moksha until the BL 5.0 release when Jeff specifically asked me to incorporate a PulseAudio module and Štefan's clipboard module directly into moksha source code. It was then I noticed Moksha had a whole slew of other issues, ranging from trivial (using depreciated functions in EFL) to flat out segfaulting in certain cases. I also found issues in all our themes, fixed some and Štefan fixed many many more. Even with all that said I make no guarantees Moksha is bug-free, in fact as I maintain a list of known bugs/issues, I can assure you there is plenty of room for improvement.

But it is worth Noting that e24 is extremely stable. At least in my experience, for my workflow/settings and on my hardware.


Since we forked e17, I have always made a deb file to make it possible to install a more recent version of Enlightenment on Bodhi. Demand seems small for it tho based on forum responses, msgs and conversations elsewhere about it.

But regardless, my current plans are to include a pure Enlightenment release with the Bodhi Linux 6.0 release. I am not ditching Moksha but the pure Enlightenment release ISO will be a test to see:

• How much demand there is for such a release.
  
• How suitable e currently is for usage on a wide range of hardware.
  
• Perhaps attract some developers and or themers to help with the e version.

This decision was made as a result of a long conversation I had with Raster, in which he said among other things that "there should be greater collaboration between the Bodhi community and the enlightenment." As to this, I have tried to do my part by reporting bugs with efl or e itself. I usually report this directly to Raster himself, as if I don't it tends to be ignored. Even then, it usually takes some effort to convince Raster that there is actually an issue unless he can clearly reproduce it. That is by no means a criticism as I am the same way: I tend to ignore reported 'bugs' that I can not reproduce. Even if the bug is real it is hard to debug unless the person reporting the issue is a developer and can use strace, gdb. valgrind et al. Or unless I just flat out ssh into their machine and try to do it all remotely. I am unlikely to do the latter, too much hassle, too much trust (on their end), and it could  take me a long time: hours to days.

Possible issues with a pure enlightenment release:

• None of our themes are going to work as expected. It would be an ungodly amount of work to port them all to e24.
• There is a lack of themes for e24 that are fully functional and of course, none of them have been "Bodhized".
• Some of our modules such as our clipboard module or Štefan's sticky note module would be unavailable unless ported to e24.
• Creating a Bodhi patch to add our menu item like we used to do. If I decide to go that route that is.
• Additional work falling mostly on me unless I get some help with this project.
• Additional work providing support for two window managers/DEs.
• Possible issues with e itself, such as compositing not working correctly on some hardware as e17 had this issue.