Enlightenment looks pretty good, except that from what I've seen, it has a distinctly 90s look to it. Have they started to integrate animations and effects like Gnome and KDE have in recent years? Making a new desktop that is bereft of eye candy is unlikely to get much adoption, since everyone from Microsoft to Apple to Google has been laying it on thick with composited interfaces with "whizzy" effects. I guess you could still win over the Puppy Linux / DamnSmallLinux crowd with a simple interface, but XFCE and LXDE have already completely cornered that market IMO.
Still, more choices isn't a bad thing. The "point" of the project, if nothing else, is to have fun and release free software -- if it actually has users on top of that, it's a plus.
Announcement
Collapse
No announcement yet.
Version 1.0 Of Enlightenment Foundation Libraries
Collapse
X
-
Originally posted by Awesomeness View PostIt's not magic. It's just human psychology.
?Release early, release often? attracts testers and developers alike.
If you refuse to give it a stable version number, you also refuse to promise to not reshuffle the whole software source code from one day to the next and break everything in one go.
If 0.17 is usable, they should just ship the current state as Beta 1 and then over the course of 6 months ship 3 additional Betas, 2 RCs, and then release that thing.
Then they should take 6 to 12 additional months to tighten up the loose ends and get 1.00 out of the door.
And then instead of endless release delays, they should delay features, not releases. A 6 months release cycle served both KDE and GNOME very well.
Leave a comment:
-
Originally posted by 89c51 View PostI have no idea how easy/attractive is for developers to write Apps in EFL but now that the interfaces are not changing (stable core) things might change and the whole thing might gain momentum. Its up to the E17 people/community and what they want to achieve with it.
Leave a comment:
-
Originally posted by Joe Sixpack View PostThe question is, what did they do wrong?
KDE and Gnome weren't always this big - they picked up momentum over the years and kept growing. Even XFce came out of nowhere and made a place for itself without having any of the things you mentioned at the time. Regardless of usage numbers Enlightenment and Fluxbox had the biggest buzz in the Linux community at one point. They were the hot cool different window managers to use.
So what happened? What misstep kept them from relevancy?
I have no idea how easy/attractive is for developers to write Apps in EFL but now that the interfaces are not changing (stable core) things might change and the whole thing might gain momentum. Its up to the E17 people/community and what they want to achieve with it.
Leave a comment:
-
Originally posted by Joe Sixpack View PostSo what happened? What misstep kept them from relevancy?
Leave a comment:
-
Originally posted by 89c51 View PostThe adoption (in distros etc) i think has to do with not being release quality and by that i mean that although it was stable a lot of things could have changed until its official release.
What is also needed is native apps in order to be able to built a complete Desktop environment. Some might argue with native but IMO if you want to offer a pleasant quality experience you don't want your desktop to look like a patchwork.
What i would love to see in the future is: e17-XUL for mozilla apps (firefox integration and why not thinderbird), an xmms2 frontend (yes i know xmms2 is not ready), mplayer frontend, frontend for telepathy (for IM, VOIP, the lot), text editor, photo editor/manager, libre office integration, little tools here and there (ie. pulse audio mixer) etc.
KDE and Gnome weren't always this big - they picked up momentum over the years and kept growing. Even XFce came out of nowhere and made a place for itself without having any of the things you mentioned at the time. Regardless of usage numbers Enlightenment and Fluxbox had the biggest buzz in the Linux community at one point. They were the hot cool different window managers to use.
So what happened? What misstep kept them from relevancy?
Leave a comment:
-
Originally posted by Awesomeness View PostI know that I could do that. However that is not an approach for a community project to attract new people. I'm assuming they want new people, right?
If they what more, then they should get 0.17 into a state which distributors won't hesitate to put into their repos. Then people can more easily check it out. Of those some might become interested to develop it.
Currently 0.16 is the release favoured by the distributors I know.
When they feel pressure to release something after no less than 10 years, then they are the most laid back people I know.
To put things into perspective: When 0.17 was first committed to CVS, KDE 2.0 has just been released, GNOME was still at version 1.2, and Windows ME was the latest shit from Microsoft!
Either way, suppose it doesn't matter much - there's a lot of work on it recently, and it's shaping up quite nicely.
Leave a comment:
-
Originally posted by mirv View PostEverything has been available to test with for some time, and you could pull out of svn as often as you'd like.
If they what more, then they should get 0.17 into a state which distributors won't hesitate to put into their repos. Then people can more easily check it out. Of those some might become interested to develop it.
Currently 0.16 is the release favoured by the distributors I know.
Originally posted by mirv View Postdidn't want to have the pressure of releasing stuff
To put things into perspective: When 0.17 was first committed to CVS, KDE 2.0 has just been released, GNOME was still at version 1.2, and Windows ME was the latest shit from Microsoft!
Leave a comment:
-
Originally posted by Awesomeness View PostIt's not magic. It's just human psychology.
?Release early, release often? attracts testers and developers alike.
If you refuse to give it a stable version number, you also refuse to promise to not reshuffle the whole software source code from one day to the next and break everything in one go.
If 0.17 is usable, they should just ship the current state as Beta 1 and then over the course of 6 months ship 3 additional Betas, 2 RCs, and then release that thing.
Then they should take 6 to 12 additional months to tighten up the loose ends and get 1.00 out of the door.
And then instead of endless release delays, they should delay features, not releases. A 6 months release cycle served both KDE and GNOME very well.
So I guess I still don't see your point.
Leave a comment:
Leave a comment: