Slashdot Mirror
Enlightenment E19 To Have Full Wayland Support
An anonymous reader writes "Full Wayland support has been added to Enlightenment 0.19. Building upon earlier Wayland support, Enlightenment can now act as its own Wayland compositor by communicating directly with the kernel's DRM drivers instead of having to rely upon Weston. The Wayland support is still considered experimental but it's now the first Linux desktop with full Wayland support."
Quick README on building and using it.
Oh great, another acronym overload. The first thing I thought of was Digital Restrictions Management drivers, which was plausible because stuff that plays the crap that comes from Hollywood usually wants to be paranoid about DRM. Do we really have to overload this acronym with something related to screen display?
#naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
The main wayland API docs are pretty meh and any others I can find are also not great. Does anyone know of a site gives proper C/C++ examples akin to the venerable Xlib Programming Manual?
e17 took almost 10 years? or just 6? :P
Hawaii was the first, I think.
http://en.wikipedia.org/wiki/H...
Well.. maybe. Or Maybe not. But Definitely not sort of.
There is also a Wayland distro called Rebecca Black OS. Although when I tested it last time, it was super glitchy and crashed all the time. It has been recently updated so it might be worth another shot.
Anyway, great to see the Wayland stuff rolling in.
enjoy your lols. e17 -> e18 took 12 months. it's been about 4 months since e18.
--------------- Codito, ergo sum - "I code, therefore I am" --------------------
E developers apparently never have to remotely access anything. Gee.
I'm sticking with E17.
Think you're confusing the acronym.. DRM in this context is Direct Rendering Manager.
I love how the Enlightenment project is still at version 0 :)
EPIC!
Can somebody explain please, for those who've been under a rock like me, what this wayland exactly is, what's its place is in the system architecture, and why it's so different/better/newer than traditional x-server+window manager yet apparently so hard to interface with.
I have absolutely no idea what the summary is talking about, but I did recognize the word "Linux" at least. And "DRM", but apparently it's not that DRM.
Better known as 318230.
I have no, zero, nada idea what's being discussed here. Am I the only un-enlightened person on /. and it has been the latest craze and buzz and just I'm so far out of the loop that I have never ever heard of it?
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Enlightment is one of those things which always seems great from an distance but somehow I never get around to really using. I've been playing with terminology recently and it seems pretty good (shiny effects are even smooth on my venerable eee 900).
But lots of people Ive spoken to share the same sentiment. Does anone here use it and is it any good in practice? Ultimately I'm not very sold by merely shiny things. Terminology does at least seem to be really functional.
SJW n. One who posts facts.
12 years, in fact. But E18 was only 1 year. I doubt they are eager to do another ground-up project like E17 any time soon, so E19 may well be ready in a reasonable time like E18 was.
Considering how long it took for them to get V17 out, will we see V19 in 2050 or 2055?
Yes, the example is called Weston.
NB: The message above might reflect my opinion right now, but not necessarily tomorrow or next year.
I'm dying to find out whether Wayland is faster and smoother than X. Anyone have any evidence?
ayottesoftware.com
Oh right. So if I wanted a decent reference guide for the unix system APIs you'd tell me to go and read the linux source code instead of getting hold of a copy of Stevens?
@rsehole.
I realize this is a specialized subject and that the people who are really interested in this already know what is being discussed. However, I feel your audience would be much wider if you added a short paragraph on what Enlightenment is, what Wayland is and why what you are discussing is a big deal. I'm not being sarcastic, the title is intriguing, but I don't have the time to dig through all the available resources to really understand what is being discussed. Just a suggestion.
So the X11 "trolls" where right and it took 15 years to figure it out?
If that's so, perhaps the general public, the real trolls, shouldn't mock enlightenment?
Never. Going. To Happen. Not with the current crowd...
these days, like most high end users we are fleeing gnome/unity/kde (tho kde is still my choice for non-lightweight) to use e17 or xfce or lxde etc
i do admit that e17 hits many sweet notes of art :)
WTF... look away for a few months and it skips two wole versions after having sat on 0.16 for years...
Anyway, the enlightenment website itself only mentions Enlightenment 0.17... so where the heck is this 0.19?
Donald 'Duck' Dunn: We had a band powerful enough to turn goat piss into gasoline.
No it will not take a decade to see E19 final. Once the project started back up again, they went from E16 to E17 in one year. E18 was quickly on it's heels and now a functional beta of E19 is already out. I am on their mailing list and follow the project closely. They are developing at warp speed. To all the people who install a recent version of E, play with it for a few hours, declare it crap and purge it from their systems: you have no idea what you are missing. If Enlightenment has a problem, it is that to use it to it's full potential - which is vast - one must endure one of the, if not the, steepest learning curves of any DE out there. Once mastered, there is no GUI\DE more powerful and flexible. I am currently running Bodhi 4.2 with E 17.4 and out 16 years of using Linux and every other DE\WM that has come along over that duration, this is the greatest setup I have ever had. I have one display setup with four workspaces, each setup in it's own tiling configuration and my other display setup in a more traditional, but heavily customized way. The window tiling abilities in E are no joke and one of the primary reasons I use it. Being able to use it both ways, one on each monitor is more than I could ever ask for. Now, if all E could do right after an install was limited to what you are presented with, then yes, it would be silly. But it is up to the user, perhaps with a little Googling, forum searching, and getting the mailing list to make it do whatever your hearts content. Because of this, Enlightenment is not for everyone: power users only need apply. I keep going, but i will stop here before I get too carried away. My only gripe is the current lack of documentation for Elementary, which makes writing software for it difficult since you can only learning by studying source code, but standard tutorials are on the way.
Brought to you by Carl's Junior.
Finally Wayland will start to approach what the fanboys said it was already doing two years ago!
Jabs at the very weird fanboys aside, I wish the developers the best of luck (even the one that likes to make fun of Enlightenment) and hope it goes well. We need a range of options and not "one true desktop" like some of the fanboys want.
He's not telling you to read the linux source code, he's telling you to read the "Reference" compositor. i.e. it is meant to be the example code.
This is a good test of whether you should be reading this thread. If you don't realize that DRM in this context is "Direct Rendering Manager", then this thread is way too technical for you, in fact probably the entire site is.
I've used it since 1997 or 98 and still have e16 with the same theme I've been using since 1999 on a new work pc. I've put a variety of things on other machines but keep coming back to e16/17 and fluxbox. There are many things better about e17, which I have at home, but I've got too comfortable with different coloured window borders meaning different things and haven't found or put together a e17 theme like the "ganymede" theme I'm used to.
The window snapshot thing is nice but even win7 has that now so it's bound to be in a few other X window managers.
reference code != reference documentation
The code IS the documentation.
Especially if it is in C++, the most readable and unobfuscatable language in history....
No, it seems that half of the people reading this article crawled out from under a rock in the last couple weeks.
Well, it *is* spring in the northern hemisphere, that might have something to do with it.
:-P
"What in the name of Fats Waller is that?"
"A four-foot prune."
Who cares?
Fuck all of those...openbox and fluxbox are waaaay better for so many reasons it isn't funny.
OpenBox FTW.
Makes sense since Tizen IVI uses Wayland and EFL
There are some docs (they aren't terrible but certainly incomplete), that are not the source code. Wayland/Weston is written in C currently, though it's a protocol so a C++ implementation isn't out of the question.
I don't want to write a damn compositor - I want to learn the user API FFS!
I'm glad you posted this, but note that the tittle of the article is wrong: the RDP backend was merged into the *Weston* compositor not into the Wayland protocol.
Which means that if you're using E19's own Wayland compositor then of course you **don't** have access to this this RDP backend, unless there is a way to stack compositors?
Please try to understand what you've written and then try relating it back to my post above. Sadly there don't seem the be many "modern applications" in use by that definition so you are describing the minority of situations.
That's an opinion of what is possible - it's a goal and not a description of something that has been implemented and shown to save time.
Just because using a strawman like the latest piece of crap gedit is slow to start does not mean X is a failure.
I'm not convinced by this argument. Last time I used Enlightenment was years before DRM in either context had been coined. In the intervening years, Digital Rights Management has been covered extensively everywhere (even slashdot) and Wayland has been banged on about for a long time too (especially slashdot).
The only reason I know DRM exists in an X context is that I saw it once in an X.org config file. And given that this article is fussing over moving away from X, there's no real reason to connect the dots.