Announcement

Collapse
No announcement yet.

Version 1.0 Of Enlightenment Foundation Libraries

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Version 1.0 Of Enlightenment Foundation Libraries

    Phoronix: Version 1.0 Of Enlightenment Foundation Libraries

    If you missed it this Friday night, version 1.0 of the core Enlightenment Foundation Libraries (EFL) have been released...

    http://www.phoronix.com/vr.php?view=OTA1Nw

  • #2
    Well I'll be damned. With hell frozen, Duke Nukem Forever shipping, and e17 reaching 1.0, what the heck are we supposed to use as a metaphor for "never"?

    Comment


    • #3
      Originally posted by curaga View Post
      Well I'll be damned. With hell frozen, Duke Nukem Forever shipping, and e17 reaching 1.0, what the heck are we supposed to use as a metaphor for "never"?
      yep

      the enlightenment people just created a BIIIIIIIIIIG problem for all of us.


      On topic with "correct" native apps it can become a really attractive choice as a Desktop Environment

      Comment


      • #4
        Originally posted by curaga View Post
        Well I'll be damned. With hell frozen, Duke Nukem Forever shipping, and e17 reaching 1.0, what the heck are we supposed to use as a metaphor for "never"?
        I think this is just the libraries, not the whole desktop? Still, never thought I'd see the day.

        Comment


        • #5
          Come, now. Hell be definitely frozen, but we've only been told Duke Nukem Forever be shipping. And While EFL has hit 1.0, Enlightenment itself?

          Comment


          • #6
            Originally posted by curaga View Post
            Well I'll be damned. With hell frozen, Duke Nukem Forever shipping, and e17 reaching 1.0, what the heck are we supposed to use as a metaphor for "never"?
            Hahahaha damn, you did the Duke Nukem reference before I had the chance

            Comment


            • #7
              Originally posted by 89c51 View Post
              yep the enlightenment people just created a BIIIIIIIIIIG problem for all of us.

              On topic with "correct" native apps it can become a really attractive choice as a Desktop Environment
              I guess it's cool that they're still working their way forward, but what I don't get is why we're not seeing a bigger adoption of E17. I know I'm repeating things that people has said a hundred times, but E16 is a million years old and looks like crap (imho) and E17 was a really nice and ambitious idea when it was spawned, but that's also 10 years ago.

              Why hasn't E17 been pushed into repos and package handlers more fervently? I mean, Gentoo for instance doesn't have a E17 package, except via an overlay (which is of course a nice way of handling it since overlays was introduced). I seems like the e17 dev(s) should have done an "release-early-release-often"-approach and also should have been working to get e17 into distributions, just to get the user-base numbers up.

              Or am I completely wrong here?

              Comment


              • #8
                The 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.

                Also a backend for Wayland when its ready

                However knowing that they have extremely limited manpower and far less support from companies i don't expect that much except if they manage to built a big community.

                Comment


                • #9
                  How many decades will it take until Enlightenment finally hits 1.0? I mean, they started developing version 0.17 (yes, there is a leading zero) 10 years ago.
                  Does this mean that with the release of EFL 1.0 they're halfway though with finishing 0.17? If it takes them 20 years to develop a 0.01 version jump and they plan to release 0.18…0.99, then it will be 1660 years before they hit 1.00.

                  Call me old-fashioned but I'd like to use software that actually hits a stable release at least once in my life time and not waits for the second coming of Jesus to hit 1.0…

                  Comment


                  • #10
                    Originally posted by Awesomeness View Post
                    How many decades will it take until Enlightenment finally hits 1.0? I mean, they started developing version 0.17 (yes, there is a leading zero) 10 years ago.
                    Does this mean that with the release of EFL 1.0 they're halfway though with finishing 0.17? If it takes them 20 years to develop a 0.01 version jump and they plan to release 0.18…0.99, then it will be 1660 years before they hit 1.00.

                    Call me old-fashioned but I'd like to use software that actually hits a stable release at least once in my life time and not waits for the second coming of Jesus to hit 1.0…
                    Changing the numbering system won't do much - making it 1.00 doesn't magically make something "stable".

                    Comment


                    • #11
                      Originally posted by mirv View Post
                      Changing the numbering system won't do much - making it 1.00 doesn't magically make something "stable".
                      It'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.

                      Comment


                      • #12
                        Originally posted by Awesomeness View Post
                        It'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.
                        Everything has been available to test with for some time, and you could pull out of svn as often as you'd like. They notified when the interfaces became stable, and I'm guessing didn't want to have the pressure of releasing stuff when they knew the interfaces would change. Also, E17 was originally never intended to take on KDE or GNOME, though that seems to have changed by now. The project kind of grew.
                        So I guess I still don't see your point.

                        Comment


                        • #13
                          Originally posted by mirv View Post
                          Everything has been available to test with for some time, and you could pull out of svn as often as you'd like.
                          I 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.

                          Originally posted by mirv View Post
                          didn't want to have the pressure of releasing stuff
                          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!

                          Comment


                          • #14
                            Originally posted by curaga View Post
                            Well I'll be damned. With hell frozen, Duke Nukem Forever shipping, and e17 reaching 1.0, what the heck are we supposed to use as a metaphor for "never"?
                            Year of the Linux Desktop.

                            Comment


                            • #15
                              Originally posted by Awesomeness View Post
                              I 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!
                              I don't think it was being developed as anything other than "this is fun" - at least that's the impression I had. Plus it seems to have grown. I think they're after people to develop applications now though...which is why the push for some stable base libraries recently.
                              Either way, suppose it doesn't matter much - there's a lot of work on it recently, and it's shaping up quite nicely.

                              Comment

                              Working...
                              X