Moksha Desktop environment pkgsrc port

kc9udx

wpa_gui works very well with KDE,

xbattbar is far better than any cutesy battery icon I've seen. It works perfectly no matter what DE you use.

Keyboard/mouse, and kdm of course, work as expected in KDE.

naguam

It looks like (mentioning kdm) you use KDE 4 which last release was 10 years ago and maintainance release ended in 2017.

At the time Linux developed software was more Unix-ish.

I don't mind KDE4 but I think I can add "maintained" to every sentence of my previous post.
I think it is important.

For you point on xbattbar (based on the deprecated apmd instead of envsys).
Enters in the case of having to tinker to make it work which is not the point of fully fledged desktop (and having to tinker enters in the case of having to manually configure a WM. Some people might like it, but not everyone, I myself prefer a nice out of the box experience to put my energy on the work I am actually doing with my computer)

Of course you can make some things work by tinkering, that is beside my point.
Because my point is about integration and polishing.

And I am not speaking only about a battery indicator but also integrations in DE settings menu, power management settings.

Regarding e26/e27 BSD licensed and very efficient on slow systems makes it a very good option indeed @Jay
This could be a nice DE to focus effort for a nice experience.

rvp

kc9udx xbattbar is far better than any cutesy battery icon I've seen.

New to me, and it's nice! Thx.

naguam For you point on xbattbar (based on the deprecated apmd instead of envsys).

It uses envsys, but, the older, deprecated, non-plist ioctls. I mostly ignored these when I did my survey of the battery-stuff a few years ago. These older ioctls (ENVSYS_GTREINFO & ENVSYS_GTREDATA) are much easier to program--at least if you want only the battery stats.

(Note: there seem to be 2 xbattbars in the wild: 1.4.2, the older (patched) NetBSD version; and the 1.4.9 in Debian/Ubuntu which uses external scripts to gather battery stats.)

blckmaxima

@Jay I actually took a look at packaging Moksha, but instead focused on enlightenment-0.26. I had meant to write to pkgsrc-users asking for testers, but life got in the way :-)

e26 runs nicely on my ₇ year old laptop, with minimal resources. Would love feedback from others that try it.

I'm open to collaborating with others in this area, I've been a lurker here, and elsewhere, for the past few years.

blckmaxima Ahh, so that's you working on e26, thank you!

If it's working fine, it should be possible to review and import into the main branch.
Send an e-mail to pkgsrc-users and request a review.

Just one question, what's with these? Are they really needed? What is one missing without them?

Perhaps clarify that on the e-mail you send to the list.

Jay

blckmaxima any updates on E27 front ! 😃

Jay

@naguam that's why I was keen on Moksha or E26/27 that being BSD licensed it might be easier to integrate battery UI, network UI etc not sure how it can work out.

@blckmaxima agreed do write to pkgsrc mailing list someone might be interested there too 🙂 I tried old port in pkgsrc it works well with NetBSD that's why I got interested in Moksha desktop

naguam

rvp I must have read source of the wrong version, but anyway thats besides my point and still deprecated anyway.

rvp

naguam thats besides my point and still deprecated anyway.

I called your attention to it because with these compat ioctls you need neither proplib nor something like expat (what I used for my test) to parse the XML--ie. there's one less dependency. (Not asking you to rush out and change your code 😃)

blckmaxima

Jay I had an update to 0.27 ready to go, and I saw they released 0.27.1... I'll try and put it all together. Life is a bit full right now 🙃

Jay

blckmaxima is it in stable pkgsrc release? Or still in WIP?

blckmaxima

Jay I just updated it in wip, let me know if it works!