throgh wrote:If it is okay: I stay at the point. Building first in a clean environment (chroot) as in our build-server. Afterwards I'll create another thread listing the PKGBUILD-script and the additional files. The meaning for this step is the same as for hplip-drivers. Having clear tests!
Gotcha, I have added other wm ideas and one DE...
Gotta check the DE, it looks flashy, which means it might need dbus...
Will find out soon, if it doesn't, feel free to add it if you wish.
Edit: Seems that isn't a problem, however...
there are a few building issues, that I see...
If anyone feels like fixing this up for HyperbolaBSD, or in general, that's one thing, but I somehow think this should be waited on till Hyperbola devs have more time... unless g4jc has interest...
He had interest in xynth at one point, which strangely enough, is what xfast was based on...
EDIT: Better idea, maybe I should ask jwmkit creator if he could make tjwmkit allow people to make jwm, look like that. That being said, looking like it, is fine, being as bloated, not fine whatsoever...
This is the DE I would love to emulate:
https://sourceforge.net/projects/xfast/
@jwmkit, if you see this post, let me know if you have interest in doing this.
Thank you for all your work to help make jwm even better!
Btw,
found one other idea you may have interest in:
https://sourceforge.net/projects/logout … w-manager/
I mention this, because your dialog box for jwmkit when you go to logout, is missing a few options, tell me if you are interested in this as well.
HyperbolaBSD: The Future of Secure Libre Lightweight Operating Systems!