Home » Enlightenment, Projects, SlackE17, Slackware » E17 is coming

E17 is coming

6 December 2012

Well, e17 is just around the corner.

cat in snow

I’m continuing to update SlackE17 regularly. Today, I just pushed r80174 which contains the EFL 1.7.2 and e17 alpha8. You can download it at the usual place.

Rasterman did a great work to provide a new default theme:

Enlightenment, Projects, SlackE17, Slackware

2 Comments to “E17 is coming”

  1. Oh I didn’t notice that the about page was updated!

  2. I agree that GTK+ has some limitations, but it was thoghut of with normal UIs in mind. Furthermore, there is one aspect in which GTK+ is still the best: Layout. While you complain about the layout, here are some scenarios in which GTK’s layout manager rocks the hell out of anything else on the market (FLOSS or not):- L18N. In GTK there is no form resizing. You don’t need-it. If you localize a Windows app or a web app (most of them at least), you will see cut strings and many other problems. Even if you do the form resizing manually (as you would do on Windows, mistakes can still creep in. There is no such thing on GTK.- DPI independance. Try changing the DPI in GNOME in the advanced font settings, and see if you get any problems. Now, do the same on Windows.- One XML to rule them all. Having the UI out in an XML file means that the UI designers don’t really care about the programming language at all. Furthermore, you can change that XML without having to recompile the application.I must confess that I don’t know anything about EFL, but I assume that the incredible layout manager that GTK offers is still unique.From what I can understand, you want to do to theming in EFL what js and css did to HTML. While both can be used in a right way, they are abused in most cases and to get a working result you need a lot of hacks. I am a little reticent on whether this is feasible in real life.The OpenGL support thing in GTK can refer to two things:1) Use it in the UI and theming. That is generally a bad idea from my point of view, because it’s slow as hell on a non-accelerated system. Using it optionally with a wrapper such as Cairo that can use many alternate backends, is reasonable. You don’t yet have OpenGL in POS systems, on cell phones, and in some computers.2) Use it in the app as a widget, and GTK has an OpenGL widget.Now related to X11. Here, I’m going to quote myself from a thread of Y versus X11 on /.: X11 should NOT have an integrated widget set in it. That is because, it’s multi-os, multi-platform, you can’t expect all the platforms to have the same widget set, toolkit, just think embedded devices here. One of the greatest things about it is it’s network transparency. X-Windows, is still ahead of it’s time. Microsoft introduced Terminal Services back in 97 or 98 for Windows NT Server TSE, long time after X-Windows existed, and it still is not as powerful as X11, it only draws the whole screen through a pipe, compresses it and sends-it to a client. X11 does a lot more than that, it has security is a number of forms (e.g. ACL based), it has support for extensions which is soo great, and it tells the client which extensions it supports, it has speed (when not over the network) using UNIX Sockets instead of TCP. Even over the network it’s fast. If you think that running Mozilla remotely on a 56k is slow, think of the alternatives. X11, contrarily to a very popular opinion doesn’t look, it shows. X11 wasn’t designed to be something that has bling in it. It’s up to the application to do that. Directly of you are masochistic, or using one of the many widget sets out there.

Leave a Reply