Sorry not yet, but maybe soon, in the meantime there is just the screenshots and this thread.

I don't know why anybody wants GTK anyway. Bloated now, it is a classic example of a house that's never done. At some point you have to stop adding features and put software in maintenance mode.

I prefer gtk2 over qt4/5. Compiling qt takes way too long.

qt5 does take a looooonnnngggg time to compile I admit but it is worth it I am slowly swapping to qt5 apps but again they also take a bit longer to compile

QT written in C++, GTK written in standard C, that's why the massively different compile times. The OO paradigm is as conceptually far away from how processors actually work as Pluto. C, on the other hand, is more like Mars. It's different, but at least procedural/imperative, just like machine language. I read a quote from Torvolds once where he explained what happened when he tried C++ and he couldn't get predictable assembly of any kind out of the compiler.

I'm not saying C++ doesn't have uses. But, I do like to point out that all that structure costs a great deal to implement.

I think most people, certainly on this forum would be aware of that
You pay your money an takes your choice, c++ has advantages over c, c has advantages over c++, I tend to use a mix, c for speed c++ for eass of use.

Not everyone here is a programmer... :P

for such people the diffs between c and c++ are largly acedemic, and this is reaaly a discussion for a seperate thread asit bears no real relevence to this project as i dont intend to be using gtk or qt anyway

Lots of updates this time!
To start off with the Setwallpaper has been renamed to LFSSetWallpaper to keep in line with the other parts of this project, which means the config files have changed name too, to, yes you guessed, lfsmonitors.rc and lfssetwallpaper.rc, other than the name change no changes to the actual code but it still needs to be reinstalled, make sure you uninstall the old version first.
Just a reminder if you have come to this thread without reading the start, all modules are compiled/installed the same ie ( after untaring the source and CD'ing to the extracted folder )LFSSetWallpaper here:
https://dl.dropboxusercontent.com/s/...r-0.0.5.tar.gz

Next install the LFSToolkit, please uninstall the old version first, here:
https://dl.dropboxusercontent.com/s/...t-0.0.7.tar.gz
Quite a lot of changes here, please note you MUST install the toolkit before the rest of the modules, you may have to manually run ldconfig if you have installed to a non standard location0.0.7
Added reload colours to gadget class.
Added hide window.
Fixed race condition if mouse is in line edit gadget on start up.
Added getgeom to gadget class.
Fixed getgeom in window class not getting global values.
Added get buffer to line edit class.
Moved load font to lib class.
Added show window to window class.
Added get/set label to base gadget class.
Added get stick state to window class.
Fixed not setting window active in constructor.
Added Label class.
Added auto colour for button labels chhoses black/white depending on ( guessed ) brightness.
Fixed manual window resize event loop.
Fixed not getting font colours from loaded vars.
Added load vars from default rc file when creating window, defaults true.
Minor revision bump.
Made global names in lib class private.
Added default colour/font names.
Added set/get active to window class.
Fixed is Active not being set on window class constructor.
Removed redundant init routines.
Code clean.
Added LFSTK_lib class.
Cursor set to end of line in line edit when first shown.
Added inactive states to prefs file.
Added 'inactive' state to gadgets.
Fixed too many refreshes in line edit.

Now install the rest.
LFSDesktop here:
https://dl.dropboxusercontent.com/s/...-0.0.12.tar.gz
0.0.12
Added '--back-alpha' or '-A' option to command line.
Colour specs now the same as the wm and tool kit ie use #RGB insatead of 0xRGBA.
Added 'labelalpha' to prefs to set alpha of label indepenent of colour.
Removed lfstooolkit prefs code.
Updated to use new tool kit.

LFSWManager here:
https://dl.dropboxusercontent.com/s/...-0.0.14.tar.gz
0.0.14
Theme now uses just a theme name OR a full path to theme.
Removed 'k' option.
Removed manual load of prefs file from appmenu.
Code clean.
Updated for new tool kit.

NEW STUFF!
LFSApplications here:
https://dl.dropboxusercontent.com/s/...s-0.0.7.tar.gz
0.0.2
Dialogs now reflect changes in toolkti prefs.
Renamed lfsprefsgroup.
Renamed lfstkappearance.
Added lfsdesktopprefs.desktop
Added lfsprefsgroup.desktop
Added lfstkappearance.desktop
Added lfswallpaperprefs.desktop
Added lfswmprefs.desktop
Added lfsprefsgroup.
Exit from lfsdesktopprefs prints settings to stdout.
Apply in lfsdesktopprefs now restarts desktop.
Exit from lfstkappearance prints settings to stdout.
Apply in lfstkappearance now writes tool kit prefs.
Exit from lfswmprefs prints settings to stdout.
Apply in lfswmprefs now restarts window manager.
Fixed keep above in all prefs dialogs.
Added desktop prefs.
Added window manager prefs.
Added labels.
Apply prints config to stdout.
Save save to ~/.config/LFS/lfstooltik.rc.
Added LFS Toolkit prefs.

0.0.1
First commit of lfs toolkit apps.

The above applications at the moment just contain some GUI's for setting the various prefs, .desktop files are installed in /usr/share/applications so you can launch the prefs from athe appmenu, the main one lfsappearance will allow you to launch the others, you can from here create a 'set' which can be quickly loaded allowing you to set all the prefs at one go, just enter a set name in the edit box click 'New Set' and a new set will be created with all the current prefs, to select a different set click the 'Load Set' button and you will get a drop down selection just select what set you want and click 'Apply' to load it, after selecting a set and making changes you need to click update to update the settings in the new set.
As you can see the wallpaper settings is greyed out 'cos I haven't doen that one yet!
Be aware that there is no check for overwiting an old set with a new set, that will change later, also to delete a set you need to remove it manually from ~/.config/LFS/lfsgroupsprefs, again this is to be done.

Some screenshots of the prefs dialogs are here:
https://dl.dropboxusercontent.com/s/...groupprefs.png
https://dl.dropboxusercontent.com/s/.../deskprefs.png
https://dl.dropboxusercontent.com/s/...2a/tkprefs.png
https://dl.dropboxusercontent.com/s/...kw/wmprefs.png

Still to come:
Panels.
Dock.
Etc.

How about some md5sums?

Wayne Sallee
Wayne@WayneSallee.com

Why? Trust me I'm a doctor
Ok I'll do some and post them in a day or so.

As requested

Oh cool, I'm going to have to look at your code... particularly the WM. My next project is to start playing around with Wayland.

From what I gather the internals of wayland are completly different from X so Xlib code probably won't do you a lot of good, but let me know how it goes, I haven't even looked at wayland so don't know how eay/difficult it would be to make a WM for it, also I believe ( but I may be wrong ) that wayland depends on systemd, if so I wont touch it with a 10' battle lance.

Wayland is a protocol and not a bad one. This guy impresses me and in spite of some of the humor he uses, I do not see the egomania present in some of the other freedesktop developers.

As for Wayland, the reference implementation with the Weston compositor does require systemdik, but people have it running on android and raspberry pi without the Cthulhu tendrils of certain systemd developers being involved. I say that tongue-in-cheek because I don't think systemd is actually malicious. I think some of the people involved in it have ego issues and that the project suffers from the kind of feature-creep that a carpenter's house does. The good part about that is feature creep introduces more and more bugs, which the developers have already shown they are disinclined to fix, and at some point those bugs are going to be exploited. Finally, when that news ends up on cnet, pcworld, arstechnica, etc. it will be all over for the systemd developers who think it should be free to absorb any subsystem in it's path. Just look what happened to OpenSSL.

As far as libwayland.server, I think its only requirements are KMS in the kernel and udev, which can obviously be eudev on non-systemd builds.