Re: [E-devel] Re: [e-users] e16.8 pre1

Michel Briand wrote:
> It's amasing!
>
> E16 works for years, and even if I switched to Entranced one year ago, I still
> use E16 because it's a STABLE environment I can rely on.
>
> I use E16 on 4 computers, 2 at home and 2 at work, and I use the same
> customizations for more than 6 years:
>
> - all important features are keybinded (switch, maximize, shade, iconify, ...)
> - all my favorite programs are binded too (scrot, feh, rox, ... + a number of
> scripts of mine for start/pause/stop CD or XMMS)
> - my file menu and sub-menus are filled with all my fav applications too
>
> All that stuff I repeat DONT HAVE CHANGED FOR YEAR.
>
> Users that want to USE their computer to do some duty work, or even users that
> want to USE their computer to hack for other projects, need a STABLE environment.
>
> *** SO I WONDER WHY YOU HAVE CHANGED THE CONFIG FILE STRUCTURE AND SYNTAX
> RECENTLY ****
>
I did kind of expect this reaction at some point :)
e16.8 has been underway more than a year now, and the configuration file
changes were one of the first things that happened, so the changes are
only recent in the sense that e16.8 pre1 was released recently.
> *** IT'S A BIG, AN AMASING MISTAKE THAT CRIPLE THE RESPECT YOU OUGHT FOR THE
> WORK YOU'VE DONE ****
>
The configuration file changes are undoubtedly annoying in a highly
customized setup when you expect things to work entirely without changes
for decades. However, I still think the changes are an improvement, and
there has been a lot of until now exclusively positive feedback from
users about this.
> Please pardon me, but many Open Source projects are suffering the same. It's not
> your fault. You intended to improve E and I thank you for that. But why change
> things that are working for years ?
>
But it *is* my "fault" since I made the changes. There is no reason to
blame Open Source in general :)
Why did I change things?
- To make the configuration simpler and more flexible.
Compare ~/.enlightenment/...e_session-XXXXXX and ~/.e16/e_config--0.0.cfg.
Compare /usr/share/enlightenment/config/keybindings.cfg and
/usr/share/e16/config/bindings.cfg
I think the new ones are quite a bit easier to comprehend, and the
processing of these files is no longer obscured by the use of cpp.
This may be of no concern to users who don't dig into these files, but
quite a few e16 users actually do, as not every single configuration
item is exposed via configuration dialogs.
- To simplify code maintenance and implementation of new options/features.
Previously it would require adding at least 20 lines of code to add a
new configuration option, not including code to set/get the option via eesh.
Now it takes two lines, and nothing in particular to expose it to eesh.
Previously adding some action, like e.g. shade/unshade, would require
separate code for borders/keybindings and for eesh commands.
These have now been merged so that only one implementation is required.
Users who just want e16 to work as it always has probably couldn't care
less about these things. Ok, fine, stick with e16.7.
As developer I found it increasingly annoying that it was non-trivial
and tedious to add options/features. And I don't like to get annoyed ... :)
/Kim

Community

Help

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

CountryState

JavaScript is required for this form.

I agree to receive quotes, newsletters and other information from sourceforge.net and its partners regarding IT services and products. I understand that I can withdraw my consent at any time. Please refer to our Privacy Policy or Contact Us for more details