How is it different from other desktop environments?
> Designed to work best with TrueOS®, but specifically works very well for the BSD community at large. Lumina® can also be easily ported to any OS, including Linux distros).
> Does not require any of the commonly-used desktop implementation frameworks (DBUS, policykit, consolekit, systemd, HALD, etc..).
> Does not come bundled with any "end-user" applications (web browsers, email clients, multimedia software, office suites, etc..). The only utilities that Lumina brings to the table by default are the ones written specifically for the project and are generally for background/utilitarian functionality (the largest utility is the file manager).
> Simple text-based configuration file for setting system-wide defaults for new users. This allows distributors of the desktop to easily pre-set the system defaults/interface so it just works for the end user.
> Plugin-based interface design. This allows the user to make the desktop as light/heavy as desired (within reason) simply by choosing which plugins to have running on their desktop/panels.
> Designed to function as a general-purpose system interface - easily pre-configured to run on any type/size of device or screen.
I used a previous version for a month. It was clunky, but functional. The font rendering had issues, though I understand that has improved in newer versions, which I have not tried.
Thats because most of those expects some kind of linux-isms to be present. Lumina is by BSD for BSD, and thus, perhaps ironically, works even on Linux.
> Does not come bundled with any "end-user" applications (web browsers, email clients, multimedia software, office suites, etc..). The only utilities that Lumina brings to the table by default are the ones written specifically for the project and are generally for background/utilitarian functionality (the largest utility is the file manager).
Indeed, though as I understand it, Lumina still bundles a file manager. How necessary is this? I don't have a good understanding of how e.g. Nautilus integrates into things like the file save dialog for Chrome.
The alternative would be to bundle a terminal, I think - a window manager that doesn't offer a way to run programs, is a window manager that fails as an interface.
In theory it sounds very good to me. Site is down but overall idea is very sound. Don't give me more then I apsolutely need and let me take what I really need.
Does anyone know how this compares to configuring Openbox? (and adding things like desktop icons, background image, conky, panel, etc)? From the perspective of a *nix power user, of course.
I already get my level of desired configuration through Openbox (with other programs), and retaining the benefit of idling at less than 450mb RAM usage and not having any unwanted components.
I think lumina is based on Fluxbox, which is very similar to openbox. Lumina isn't a currently window manager, it you wouldn't compare it dirrectly. Think of it as openbox plus a a start-menu and system tools like a network manager.
I say it "isn't a currently window manager" because the devs have said they are looking at making their own, but I haven't heard that they have started.
I'll contend that they need "good" designers. And maybe not a team.
Sometimes the result of one opinionated designer far exceeds the democratic team model (which tends to rely on the charisma of one vs. vision and skill).
I think those types of designers tend not to get too interested in design entire OS interfaces, however.
29 comments
[ 5.2 ms ] story [ 78.7 ms ] threadHow is it different from other desktop environments?
> Designed to work best with TrueOS®, but specifically works very well for the BSD community at large. Lumina® can also be easily ported to any OS, including Linux distros).
> Does not require any of the commonly-used desktop implementation frameworks (DBUS, policykit, consolekit, systemd, HALD, etc..).
> Does not come bundled with any "end-user" applications (web browsers, email clients, multimedia software, office suites, etc..). The only utilities that Lumina brings to the table by default are the ones written specifically for the project and are generally for background/utilitarian functionality (the largest utility is the file manager).
> Simple text-based configuration file for setting system-wide defaults for new users. This allows distributors of the desktop to easily pre-set the system defaults/interface so it just works for the end user.
> Plugin-based interface design. This allows the user to make the desktop as light/heavy as desired (within reason) simply by choosing which plugins to have running on their desktop/panels.
> Designed to function as a general-purpose system interface - easily pre-configured to run on any type/size of device or screen.
It's in the same dropdown list that lists the FaQ page.
If this is the case, I wonder why the banner on https://lumina-desktop.org/ has a link to "Development Preview: lumina-mediaplayer" (https://lumina-desktop.org/1-3-0-development-preview-lumina-...)?
The window manager is Fluxbox.
I already get my level of desired configuration through Openbox (with other programs), and retaining the benefit of idling at less than 450mb RAM usage and not having any unwanted components.
I say it "isn't a currently window manager" because the devs have said they are looking at making their own, but I haven't heard that they have started.
When designers moved into Gnome and KDE, they effectively crapified.
Sometimes the result of one opinionated designer far exceeds the democratic team model (which tends to rely on the charisma of one vs. vision and skill).
I think those types of designers tend not to get too interested in design entire OS interfaces, however.