SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
So E17 turned into beta. Final release is still due to the end of the World in less than two weeks. But before, it would be great to test it on different systems.
SlackE17 provides Slackware 14.0 packages (i486 and x86_64) of this beta. There are the EFL 1.7.3, E17 0.17-beta, some extra modules, terminology, eperiodique and elemines, some themes, etc.
The extra modules are not really supported by E17 (though they come from the same svn repository) so you shouldn't load them if you like to help debugging. The binaries contain debug symbols.
It's a good time to ask for comments about SlackE17. After 7 years packaging for Slackware, E17 is going to be released. If there are things you'd like to see in the SlackE17 packages, it's a good time to talk about it.
It would be nice to see some more apps written for enlightenment - there are some listed on the main site, but from what I can tell they're not really under very active development compared to e itself. I'm working on one or two things using the elementary widget set but they won't be ready to see the light of day for a long time yet.
ev is on the applications->graphics menu alongside
geeqie, gwenview, and the gimp. ev will start from
the console when given the parameter of a filename
or folder, but after clicking on the desktop menu I see
an error dialogue: "ev stopped running unexpectedly."
I edited the "Exec=" line of
/usr/share/applications/ev.desktop by changing ev %F to
something like "ev /path/to/file", and the desktop shows
the same results. I noticed many binary configuration
files in the local ~/.e/e/ directory. Maybe one of these
data files could be patched.
ev is on the applications->graphics menu alongside
geeqie, gwenview, and the gimp. ev will start from
the console when given the parameter of a filename
or folder, but after clicking on the desktop menu I see
an error dialogue: "ev stopped running unexpectedly."
I edited the "Exec=" line of
/usr/share/applications/ev.desktop by changing ev %F to
something like "ev /path/to/file", and the desktop shows
the same results. I noticed many binary configuration
files in the local ~/.e/e/ directory. Maybe one of these
data files could be patched.
Actually, ev is not yet ready for this. You can only open file(s) if you pass them to the command line. The .desktop file is useful when you want to add ev as the default application for viewing pictures. It will work as expected with the file manager. Then you can, for instance, select a lot of pictures and open them with ev in one click. Don't expect too much of it for now. If it's confusing for users, I may remove it from the release.
BTW, I uploaded SlackE17 r81015, with enlightenment 0.17-lucky (beta3) and terminology 0.2.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.