Thank you for your work / contribution.

https://dev1galaxy.org/viewtopic.php?id=4473
https://dev1galaxy.org/viewtopic.php?id=4542

I'm glad you are "impressed" with JWMKit.  I've tried my best to create it in a way that respects the user while also creating a very usable experience.  If you haven't already done so I recommend checking out the wiki as it reveals some of JWMKit's nicer and more advanced features.

The fact that you didn't even have a fully populated menu is odd since jwmkit_easymenu only requires Python3 to work, and I seriously doubt you were missing Python3.  The JWMKit package installs it's own python module called  jwmkit_utils.py .   If this file was missing you would have the exact same experience you described.  I don't know why it would be missing as it should of been installed.  I wonder if uninstalling and reinstalling would of fix the issue?

The JWMKit package provided on my Sourceforge site should handle the dependencies. With that said I've not tested the newer builds on older versions of Devuan/Debian. It seems dpkg ignores dependencies so I advise using either apt or gdebi to install local packages.

On another note, Sourceforge is flaking out and the files have disappeared for many project.  Sadly JWMKit is one of those projects.

EDIT - The Sourceforge issue has been fixed.

I am having trouble getting the following items from the JWM-Kit to open - Freedesktops, Trays, and Menus.  These will not open and I can see no notations anywhere in any log file that might display a missing dependency message or something similar.  Also it is not picking up the .desktop files to display within the menu.  So when I click on the start button (the rocket icon in the system tray - left side) I can see the menu but all that is displaying is the word "Applications", then a double line horizontal separator, and the word "Exit".  If the menu needs to be built manually, that is fine, but I am unable to open the menu builder program of JWM-Kit. 

I feel like I am missing a dependency, but that is a guess.  What I am using is a 64-bit beowulf minimal netinstall with a dist-upgrade to chimaera.  I installed jwm and xserver-xorg, then installed the jwmkit*.deb file, and finally the programs menu and arandr.  I am using the devuan 32bit build from the above links as a guide.

Any ideas on what is needed for the missing JWM-Kit programs to display?

Edit:  I think I was accurate with the missing dependency.  If anyone knows what it is, I would like to know.  This JWM-kit works fine on a chimaera netinstall 64bit build.  Been tinkering with it some this morning, and am impressed with it.

On another note, I just realize a pretty serious bug in the initial release of JWM Kit Live. It seems the folder ~/.local belongs to root instead of the user.

Issue the following command in the terminal to fix it.
sudo chown -R $USER:$USER ~/.local

You may (or may not) need to install the firmware for your wifi card. Which is also not to complicated.  Just type lspci in the terminal and find the model of your wifi card and a simple search on duckduckgo should help you find what firmware package to install. Once again you can install it with Synaptic.

Hint: There is plenty of discussion on the web regarding wifi tools and firmware for Debian based Distros.

As for my "high regard of the users freedoms". I have a few ideas on how to deal with that.
1. Disclaimer to the user that their own config will be overwritten. If they are fine with that then it's their decision.
2. Continue to offer the method of installing that gives the user complete control . . .  and a headache.

Another message to Puppy Users
This change in direction will also improve JWM Kit on puppy. As puppy's custom JWM config causes many conflicts and the best solution is to just delete it and use a "JWM Kit default".  Also I've made changes to a few parts of JWM Kit for puppy specific solutions.  Some of the improvements have already been pushed to my codeberg account (basically it's like github) .  But not all, and more are to come.

So to sum things up. You can look forward to:
1. Out of the box experience: being able to install JWM Kit yourself with little problem
2. Better Puppy support. Maybe able to even offer an option "revert to puppy default"

So now you know my intentions moving forward with this project.  As always, my work is limited to my free time so I give not timeline and make no promises.

To All interested in JWM Kit on Puppy.

I can't ignore the fact that their is definitely an interest to seeing JWM Kit work in Puppy Linux, so I will be taking the time to not only get it working in puppy, but to share the process.  I guess you could call it a guide, but it's mostly just notes of me getting JWM KIt running in Puppy. I'm using FOSSAPUP.  But let me know what puppy core y'all are interested in so I can provide more helpful documentation.

Everything you need is here:
https://codeberg.org/JWMKit/JWM_Kit

I'll post back when I've finished my documentation.  You should be able to find it at the codeberg.org page listed above.  I'll create a folder called puppy with the info, and it will also contain any config files I create in the process.

UPDATE: Finished my Puppy documentation. You can find it on my codeberg site listed above in a folder called puppy. The file NOTES is the documentation, and the other files are examples you can use to reproduce the process.

I do know that I have lots of improvements planned for the kit. I now have a much brighter vision of what JWM Kit should be.  Lots of changes to come and it will be good.

Keep up the good work!

I created JWM Kit with the hope of it being included in JWM base distros/builds.  If fact that is why I created JWM Kit Live. For the the purpose of being an example of how to configure the kit.  So, I would be glad to see JWM Kit included in your Builds, weather they are for personal use or public distribution.

Kindest Regards, Adam

As I said there will be lots of changes coming in the future. In the future versions the menu editor will not be a global view, but will be divided by menus (and the root menu). I also plan to have newly added items place next to the current selected item instead of at the bottom.