Other Enhanced Motif Window Manager

OK thats is too much for me. I need basic C skills first.

Code:
  Cardinal
   MrmRegisterClass(class_code, class_name, proc_name, create_proc,
                    widget_class)
       MrmType     class_code;
       String      class_name;
       String      proc_name;
       Widget    (*create_proc)();
       WidgetClass widget_class;
This is pre-Ansi-C, very old and probably not accepted by modern compilers. If you do the Motif tutorial, you will need to convert such constructs into something like this:
Code:
Cardinal
MrmRegisterClass(
    MrmType class_code,
    String class_name,
    String proc_name,
    Widget (*create_proc)(),
    WidgetClass widget_class);
That is, put the variable types directly in front of the parameter names.
 
Back on topic. Would you actually use the drm drivers or is that un-needed fluff on EMWM?

Is there any advantage to using drm drivers versus scfb for this lightweight desktop?

I see Firefox in a screenshot so that would need drm drivers to work right?

Seems like it might make a nice kiosk desktop like OpenBox..
The desktop itself (i.e. EMWM) will run fine with scfb. There won't be any hardware acceleration, however. So it depends on your CPU and on what applications you are planning to run. If these applications need, e.g., OpenGL, then you'll need the DRM drivers.
 
I think motif would make a nice Arm desktop environment.

I don't understand the xfile part.
Is it ideologically correct choice?(aka motif all around)
xfm is not that big right?
Why make new stuff?
Maybe xfm drags in gtk+?
 
My bad. That port expired.
x11-fm/xfm
What a shame. What exactly needs maintenance on a file manager.
Its like people complain about OpenBox is dead.... Stable don't mean dead.
 
My opinion, programming with Motif libs is really not any harder than programming with any other GUI toolkit. think like gtk, qt, all have their own learning curves, all have their own set of gotchas. The toolkits hide a lot of the lower details from you which can make it harder to figure out why something is not working.
Using Motif is like using the various X libraries directly: you have complete control, but you do need to keep track of details.
 
It's hard to find ressources on how to program with it
Not sure, if I agree with that assessment. A simple Google query leads you to the almost 800 page developer book on Motif: https://www.oreilly.com/openbook/motif/vol6a/Vol6a.pdf
Then again, I can't speak on usability of said resource. Maybe its sheer volume makes it an insurmountable challenge.

Also, I'd like to use this opportunity to pitch NsCDE (https://github.com/NsCDE/NsCDE) as modern alternative to CDE. Unfortunately, being built on top of fvwm, one could argue whether it's really "lightweight"... Disclaimer: I'm the port maintainer (and yes, I need to bring it to the most recent version already...)
 
Is there any advantage to using drm drivers versus scfb for this lightweight desktop?
drm drivers can achieve a wider range of resolutions than scfb (both more than vesa i.e 640x480-1024x768)

drm drivers seem to be heavily related to power management (i.e screen brightness hotkey and suspend resume). For a laptop, scfb isn't ideal.
I see Firefox in a screenshot so that would need drm drivers to work right?
Firefox will work with scfb. It won't be hardware accelerated (i.e for webgl, html5 canvas, scrolling, etc) but it will work using LLVMpipe.
 
Motif is super lightweight, right?

It's hard to find ressources on how to program with it. That's why I chose the "easier" gtk3 in my project. ?
Motif still alive too? Wow. The books you need for a jump-start into motif programming are freely available from oreilly here:-


And it really helps to have the oreily xlib and Xt books from the same series. But to get a first taste, get 6A and 6B.

I wouldn't call it super-lightweight... more like a behemoth. To do real work in it you really need to know all three layers ... xlib, Xt and motif itself. And then there are resource files... and possibly custom widgets. Make sure you have some coffee nearby. :)
 
Motif is super lightweight, right?

It's hard to find ressources on how to program with it. That's why I chose the "easier" gtk3 in my project. ?
Back in the day it wasn't. CDE was considered more heavyweight that the alternatives. FVWM2 was the choice for a lightweight wm. But compared to today's windowing environments, Motif and CDE are lean.
 
Back
Top