On Wed, 19 Aug 2015 22:47:57 +0200 Daniel Christopher Würl <[email protected]> said:
> Voilà, > > e19 up and running ;D > > I took a look at edje, and right now I'm not fully decided if it scares > the hell out of me or makes me happy. Probably both ;D > > But that brings me to another question: Where are the responsibilities > for key-bindings? I could enable my 'scroll left/right to switch > desk'-binding in the settings-dialog, but couldn't set 'right click at > title to send window to the back'. Would I need to do this in > border.edc ? that's in signal bindings. :) > And completely unrelated, I wrote some dialogs in gtk-perl and feel > like replacing them with elementary based ones. Obviously, there is no > perl binding (or at least I could not find one), so I might use python > for the beginning. In the long run C might be better suited, but all > these pointers and very annoying hacks for not having a > proper string-type have been keeping me away from that language. Does > the EFL somehow ease the pain in that regard? i've never seen the problem with strings - i just avoid them like the plague. yes the unix world loves its strings and everything must be a string (text file) or you will be damned to hell, but... bah - i just avoid them by design. eg edje files are binary. config files are binary. there's a while library to deal with that for you and make it fast, efficient and convenient. no string parsing needed. :) > And Davide, you made my life much easier ;) > > > Best Regards, > Daniel > > > Am Sun, 9 Aug 2015 14:08:49 +0200 > schrieb Davide Andreoli <[email protected]>: > > > 2015-08-09 12:33 GMT+02:00 Daniel Christopher Würl > > <[email protected]>: > > > > > Am Sun, 9 Aug 2015 14:37:26 +1000 > > > schrieb David Seikel <[email protected]>: > > > > > > > On Sun, 9 Aug 2015 12:35:56 +0900 Carsten Haitzler (The Rasterman) > > > > <[email protected]> wrote: > > > > > > > > > On Sun, 9 Aug 2015 03:19:07 +0200 Daniel Christopher Würl > > > > > <[email protected]> said: > > > > > > > > > > > Hello, > > > > > > > > > > > > as a long-term e16 user who migrated to fvwm some eight months > > > > > > ago, I'm toying with the idea of installing e19. > > > > > > > > > > > > Since I currently run debian 8 this would be a time consuming > > > > > > task, so I'd like to ask some questions before I spend some > > > > > > hours in vein ;) > > > > > > > > > > > > How stable is the API / theming API ? > > > > > > I really love to create my own themes, but I'm not motivated > > > > > > to fix them over every minor revision. Same goes for EFL, I'm > > > > > > perfectly happy to hack together some tools I need, but I'm > > > > > > not ready to adapt them to a moving target all the time. > > > > > > > > > > > > How long does a release of enlightenment "live" ? > > > > > > > > > > there were some minor breaks (little things changed) between > > > > > e17 and e18. we're keeping things stable since then though > > > > > theme expands and thus there are new things to theme if you > > > > > want a complete look, so over time it requires work anyway to > > > > > keep up. > > > > > > > > > > > Mostly part of above questions, but having to compile the > > > > > > whole efl / enlightenment stack every other month would be a > > > > > > bit off-putting. > > > > > > > > > > compiling efl is easy. if you bother once to write the > > > > > procedure in a script and then just re-run it every time. the > > > > > script clones/updates git repos and walks through n dirs > > > > > re-building each one maybe with specific options. if you bother > > > > > doing it just once for yourself, then everything after that is > > > > > gravy. what that script has may vary from person to person, > > > > > distro to distro, but the raw content of it is on the > > > > > enlightenment.org docs on how to get/build e and efl. i > > > > > scripted my builds so long ago i'ts not funny. i just don't get > > > > > this "oh but it's SOOOOOOOOOO hard" line. it's an excuse for > > > > > not having simply written down the commands in a script for > > > > > yourself ONCE. i just use my scripts and for me it's: > > > > > > > > > > svup.sh > > > > > rbe.sh > > > > > > > > > > (yes my svup.sh script was from svn days - i modified it for > > > > > git - i have 2 as i want to update separately to building). > > > > > > > > Many of the EFL developers have their own build script in git. I > > > > have one in the Enlightenment git at > > > > > > > > > > > https://git.enlightenment.org/admin/devs.git/tree/developers/onefang/build_efl.lua > > > > > > > > Which tries to compile most of the stuff we host in git. Other > > > > developers have their build scripts in the admin/devs area of the > > > > git as well. > > > > > > > > > the biggest bit of work is getting your dependencies installed > > > > > (once). that is the real work. not rebuilding or updating. > > > > > > > > Yep, a build script wont help with that, as it's generally only > > > > done once. Most of the dependencies are listed on the > > > > https://www.enlightenment.org/download page that includes basic > > > > build instructions. > > > > > > > > > > Ok, > > > thanks for the explanation ;) > > > Aside from the file manager everything sounds good so far, so I'll > > > give it a try ;D > > > > > > > The places module (https://phab.enlightenment.org/w/emodules/places/) > > lets you choose your preferred filemanager to run when clicking on > > devices :) > > > > Indeed the more time-consuming operation when installing efl are the > > dependencies, > > this is the list of packages I use in debian8, maybe it's not really > > up-to-date, but > > it should do the biggest work: > > build-essential automake autoconf libtool autopoint gettext > > check gdb valgrind doxygen > > libpam-dev libdbus-1-dev libpulse-dev libsndfile-dev libudev-dev > > libblkid-dev libmount-dev > > libx11-dev libx11-xcb-dev libxcursor-dev libxrender-dev libxrandr-dev > > libxfixes-dev libxdamage-dev libxcomposite-dev libxss-dev libxp-dev > > libxext-dev libxinerama-dev libxkbfile-dev libxtst-dev libxcb1-dev > > libxcb-shape0-dev libxcb-keysyms1-dev > > libfontconfig1-dev libfreetype6-dev libfribidi-dev libgif-dev > > libjpeg62-turbo-dev > > libpng-dev libtiff-dev zlib1g-dev librsvg2-dev libraw-dev > > libluajit-5.1-dev libbullet-dev libspectre-dev libpoppler-dev > > libpoppler-private-dev > > libcurl4-dev libcurl4-openssl-dev libssl-dev > > libgl1-mesa-dev > > gstreamer1.0-libav libgstreamer1.0-dev > > libgstreamer-plugins-base1.0-dev gstreamer1.0-plugins-good > > gstreamer1.0-plugins-base python-dev python3-dev python-sphinx > > python3-sphinx > > > > cheers > > > > > > > > > > Best wishes, > > > Daniel > > > > > > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > > > enlightenment-users mailing list > > > [email protected] > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > enlightenment-users mailing list > > [email protected] > > https://lists.sourceforge.net/lists/listinfo/enlightenment-users > > > ------------------------------------------------------------------------------ > _______________________________________________ > enlightenment-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/enlightenment-users -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] ------------------------------------------------------------------------------ _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
