aboutsummaryrefslogtreecommitdiffstats
path: root/config (follow)
Commit message (Collapse)AuthorAgeFilesLines
* remove configs for illume modulesMike Blumenkrantz2016-01-147-178/+0
| | | | | | these have been out of the tree for years but I forgot to remove the corresponding configs, leading to error messages when the mobile profile attempts to load them
* Set cached xkb context/keymapJengHyun Kang2016-01-054-0/+4
| | | | | | | | | | | | | | | | | Summary: Set xkb context and keymap to Ecore_Drm. In enlightenment (used in wayland with drm backend), keymap is used only one. So for avoid unnecessary open keymap files, set cached context and keymap. But for this, enlightenment must compile keymap before init ecore_drm. So I changed booting sequence also. Test Plan: Distinguish time between before and after during add a keyboard device. Reviewers: raster, devilhorns, zmike Subscribers: cedric, input.hacker, ohduna Differential Revision: https://phab.enlightenment.org/D3504
* (1) e_config.c/e_comp_wl.c: add code for making repeat values configurableSung-Jin Park2015-11-304-0/+8
| | | | | | | | | | | | | | | | | | | | | | (2) e.src(s): add keyboard.repeat_delay, keyboard.repeat_rate into e.src files Summary: As of now, the default values of repeat delay/rate are being set in e_comp_wl.c. Those values need to be configurable and will be used in e_comp_wl_init(). The limit of each of the values is defined from -1 to 1000. (maximum 1s). If one of the two is negative, it means default repeat delay/rate are going to be used. (e.g. delay:400, rate:25) Test Plan: N/A Signed-off-by: Sung-Jin Park <input.hacker@gmail.com> Reviewers: raster, stefan_schmidt, gwanglim, devilhorns, zmike Subscribers: Jeon, ohduna, cedric Differential Revision: https://phab.enlightenment.org/D3364
* e - fix profiles to have correct adjust value for bl adjust in bindingsCarsten Haitzler (Rasterman)2015-05-212-4/+4
| | | | @fix
* change default icon theme to hicolorMike Blumenkrantz2015-04-304-4/+4
| | | | ref T2142
* remove shelf manager config vals from profilesMike Blumenkrantz2015-03-192-2/+0
|
* Bugfix: e backlight: use saner default values.Chidambar Zinnoury2015-02-233-6/+6
| | | | The brightness scale goes from 0 (well, 1) to 100: 0.1 thus seems too low a step, 10 being better and is actually already used.
* fix: Add more desktops to be tiled by default in the tiling config.Tom Hacohen2014-09-261-26/+98
| | | | | | Now the first 4X4 are tiled by default. Fixes T1682.
* Restore translated strings accidentally dropped in fac4e89Igor Murzov2014-09-121-5/+3
|
* Updating desktop files, eo.po and fr.pomaxerba2014-09-114-4/+49
|
* Update russian translationIgor Murzov2014-09-031-0/+2
|
* e config - make all configs have full backlight config (and the same)Carsten Haitzler (Rasterman)2014-06-163-5/+11
|
* completely revert all eo/eolian usageMike Blumenkrantz2014-06-041-1/+1
| | | | | | this was a neat experiment, but apparently it's not going to be usable for a long time in anything outside efl/elm This reverts commits f87b9900faab9686b35f55606ebaf48279fe431f, a49cede7905bf2fac6aba29ffe5686fad27ce211, 81038f8d02a65b5693fad6e8d6a7ef9d229ac2a0, 47cfb31752db02c12aa36020f0c6ddeb931d4b5f.
* Updating translationsmaxerba2014-05-191-0/+5
|
* Tiling profile: remove conflicting bindings.Tom Hacohen2014-05-121-16/+0
| | | | | | Win + Left/Right were used in the tiling bindigs as well as max left/right. Those are not needed in a tiling environment, and it's better to get rid of those.
* comp_object now uses eo, e_comp_object_signal* -> edje_object_signal*Mike Blumenkrantz2014-04-101-1/+1
| | | | also cw->clip is gone
* Italian translation for Tiling profilemaxerba2014-03-301-0/+2
|
* tiling: Fixed Typo.Marcel Hollerbach2014-03-101-1/+1
| | | | | | | | | | Summary: There was onfiguration instead of configuration Reviewers: tasn CC: cedric Differential Revision: https://phab.enlightenment.org/D620
* feature: Add a tiling config.Tom Hacohen2014-03-0415-0/+2378
| | | | | | This was requested by Cedric, and actually makes sense to have. It's a profile that loads the tiling module by default, puts the gadget in the shelf, and sets some key bindings.
* feature: make desklock hookable, break out current desklock into module, ↵Mike Blumenkrantz2014-01-142-0/+12
| | | | | | | | move pam stuff to separate file after this commit, the new-but-invisible module "lokker" (or other custom loaded module) is in charge of creating all graphics for the lock screen, and it will be added to the user's config. failure to load a lockscreen module will just result in a black screen desklock subsystem now handles all the pre/post lock stuff while the modules themselves are responsible for creating visuals and calling auth functions to determine whether to unlock the screen
* feature: comp config is no longer a moduleMike Blumenkrantz2014-01-142-12/+0
| | | | given that compositing is always enabled and that it's crucial to be able to change these settings, potentially having them unavailable is not a great way to live
* update config for v14Mike Blumenkrantz2014-01-143-26/+4
|
* compositor rewrite / charlie-foxtrot situationMike Blumenkrantz2014-01-142-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | huge fustercluck commit because there wasn't really a way to separate out the changes. better to just rip it all out at once. * compositor and window management completely rewritten. this was the goal for E19, but it pretty much required everything existing to be scrapped since it wasn't optimized, streamlined, or sensible. now instead of having the compositor strapped to the window manager like an outboard motor, it's housed more like an automobile engine. ** various comp structs have been merged into other places (eg. E_Comp_Zone is now just part of E_Zone where applicable), leading to a large deduplication of attributes ** awful E_Comp_Win is totally dead, having been replaced with e_comp_object smart objects which work just like normal canvas objects ** protocol-specific window management and compositor functionality is now kept exclusively in backend files ** e_pixmap api provides generic client finding and rendering api ** screen/xinerama screens are now provided directly by compositor on startup and re-set on change ** e_comp_render_update finally replaced with eina_tiler ** wayland compositor no longer creates X windows ** compositor e_layout removed entirely * e_container is gone. this was made unnecessary in E18, but I kept it to avoid having too much code churn in one release. its sole purpose was to catch some events and handle window stacking, both of which are now just done by the compositor infra * e_manager is just for screensaver and keybind stuff now, possibly remove later? * e_border is gone along with a lot of its api. e_client has replaced it, and e_client has been rewritten completely; some parts may be similar, but the design now relies upon having a functional compositor ** window configuration/focus functions are all removed. all windows are now managed solely with evas_object_X functions on the "frame" member of a client, just as any other canvas object can be managed. *** do NOT set interceptors on a client's comp_object. seriously. * startup order rewritten: compositor now starts much earlier, other things just use attrs and members of the compositor * ecore_x_pointer_xy_get usage replaced with ecore_evas_pointer_xy_get * e_popup is totally gone, existing usage replaced by e_comp_object_util_add where applicable, otherwise just placed normally on the canvas * deskmirror is (more) broken for now * illume is totally fucked * Ecore_X_Window replaced with Ecore_Window in most cases * edge binding XWindows replaced with regular canvas objects * some E_Win functionality has changed such that delete callbacks are now correctly called in ALL cases. various dialogs have been updated to not crash as a result comp files and descriptions: e_comp.c - overall compositor functions, rendering/update loop, shape cutting e_comp_x.c - X window management and compositor functionality e_comp_wl.c - Wayland surface management and compositor functionality e_comp_canvas.c - general compositor canvas functions and utilities e_comp_object.c - E_Client->frame member for managing clients as Evas_Objects, utility functions for adding objects to the compositor rendering systems additional authors: ivan.briano@intel.com feature: new compositor removal: e_border, e_container, e_popup
* feature: use non-recursive makefiles for entire build systemMike Blumenkrantz2014-01-148-130/+91
| | | | | | | | this is the correct way to write a build system. one toplevel Makefile.am with the rest of the directories having include Makefile.mk files. additional authors: Iván Briano <ivan.briano@intel.com>
* update standard config for v12Mike Blumenkrantz2014-01-141-1/+2
|
* thumbs - add more mime types that can thumbnail and have e_thumb do it rightCarsten Haitzler (Rasterman)2013-11-222-0/+88
|
* remove "border_raise_on_focus" config optionMike Blumenkrantz2013-10-073-3/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | buckle up. for the first time in history, a config option is getting removed instead of added. the reasons for this removal are many, but let's go way back to the beginning and see why it was added: oh wait, we can't because the commit message (from 2006) is >> patches that i said were in - commit. (see my reply emails) >> also finish off a TODO item or 2 reading through the TODO items which were also crossed off in that commit, I'm assuming that this was the "option to NOT raise on focus in click to focus" item. == REASON 1 == the problem here is that there's another, BETTER option called "click raises window" (always_click_to_raise) which does the same thing, except it doesn't totally fuck you when you get a random X focus event, which happens more often than you might think. this means that, to avoid broken behavior which might cause your windows to spastically raise for a few frames in common cases (using winlist...) with click-to-focus, you have to know that this is the default-enabled option that's fucking you, and you have to remember to manually disable it every time. if you DON'T know that this is the option that's fucking you, and you just see windows randomly raising on their own, you'll probably either ignore it or file a bug, when this is supposed to be a "feature" that actually worked in reverse, since it was intended only for disabling. == REASON 2 == there's also auto-raise, which can be set to 0.0s, which is effectively the same thing since it also triggers on focus but can be configured not to fuck your window stack == REASON 3 == aaand finally, this option makes any sort of pointer focus model impossible to use, since your windows will constantly be raising all over as you move the mouse tl;dr: I'm removing it, e-dealwithit.gif
* Revert "updating desktop files"Igor Murzov2013-09-042-2/+1
| | | | This reverts commit 22f7a34e2368de7693efee812c1d4d83604e76a4.
* enable teamwork module by default in standard configMike Blumenkrantz2013-09-021-0/+6
|
* show efm toolbar+sidebar by default in standard profile, same as in codeMike Blumenkrantz2013-08-301-2/+2
| | | | T337
* set some better focus-raise defaults after recent raise-on-focus fixMike Blumenkrantz2013-08-211-1/+1
|
* updating desktop filesmaxerba2013-07-312-1/+2
|
* Fixed sorting in desktop filesmaxerba2013-07-053-29/+32
|
* font previews in efm - in thumbnails and in efm previewCarsten Haitzler (Rasterman)2013-07-022-0/+104
|
* Add serbian translation of desktop files.Igor Murzov2013-06-283-0/+5
| | | | Found these uncommited files while cleaning up my temporary files :/
* fix png's with icc profile oddnessDoug Newgard2013-06-221-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | I'm sure some of you have seen the warnings generated by libpng 1.6: "known incorrect sRGB profile". Now, this is no big deal, it's just a warning, but I still wanted to look into it further. By my count, there are 800 png files in Enlightenment, of which only 6 have embedded iCC profiles, all from HP. The rest are sRGB colorspace, but do not include a profile. There are some good arguments for this (http://imageoptim.com/color-profiles.html http://www.gballard.net/psd/save_for_web_embed_ICC_profile.html) and since this seems to be the default, I've attached the 6 files with the profiles stripped out. As you can see, it doesn't change the image or the colorspace, it just leaves the calibration up to the end user's system. I haven't been able to find just what's wrong with the HP iCC profile being used that the authors of libpng don't like, but it makes sense to standardize the way profiles are handled anyway. And it has the nice side effect of silencing warnings, even if the Debian/Ubuntu users aren't likely to see them for a couple of years. I can just change the iCC profile instead if you would prefer. I've seen multiple people recommend the Argyll sRGB profile, which is still "sRGB IEC61966-2.1" and is public domain.
* disable notification module for mobile profiles...just no.Mike Blumenkrantz2013-03-061-6/+0
|
* correctly update all the stock configs to current version and fix up default ↵Mike Blumenkrantz2013-02-064-1366/+6
| | | | | | profile signal bindings list SVN revision: 83657
* merge all bindings dialogs into single module: conf_bindingsMike Blumenkrantz2013-02-051-7/+1
| | | | | | | configs have been updated to load correct module and modapi version has been bumped to invalidate old modules SVN revision: 83632
* whoops, wrong binding version in default configsMike Blumenkrantz2013-02-053-3/+3
| | | | SVN revision: 83621
* add profile types to config so it will be possible to determine what type of ↵Mike Blumenkrantz2013-02-043-0/+3
| | | | | | config the user started with SVN revision: 83588
* remove dropshadow module configMike Blumenkrantz2013-02-041-7/+0
| | | | SVN revision: 83587
* forgot to add binding config file sourcesMike Blumenkrantz2013-02-013-0/+2322
| | | | SVN revision: 83562
* giant commit that wipes all bindi^W^W^Wsplits out binding configs into a ↵Mike Blumenkrantz2013-02-014-1009/+8
| | | | | | | | | separate config domain so they can be more easily copied and so they won't be wiped in the event that primary config is wiped also splits all binding lists out of e_config: they are now conveniently located in the global "e_bindings" struct SVN revision: 83544
* added missing conf for screen_limits (new lost windows)Samuel F. Baggen2013-01-172-0/+2
| | | | SVN revision: 82913
* comp module config is dead, long live conf_comp!Mike Blumenkrantz2013-01-112-2/+2
| | | | SVN revision: 82617
* patch from Deon Thomas fixing incorrect variable name for base conf module ↵Mike Blumenkrantz2013-01-102-2/+2
| | | | | | config version SVN revision: 82515
* e: rename option use_composite to use_shaped_winLucas De Marchi2013-01-093-3/+3
| | | | | | | | | | | | | | | | In order to move composite inside the core we need to kill the use_composite option. However in some places it is being used to switch between ARGB and shaped windows. It doesn't make much sense to keep the advanced/engine dialog to let the user toggle this options if we have composite always enabledm, but lets allow the user to shoot himself on the foot (for now). Next step will be to move the comp module files to core so user can't unload it anymore. SVN revision: 82433
* e: don't allow to disable composite in wizardLucas De Marchi2013-01-043-3/+3
| | | | SVN revision: 82226
* e: remove dropshadow moduleLucas De Marchi2013-01-041-2/+0
| | | | | | | | | | dropshadow module conflicts with composite, which will be always enabled by future commits. Remove the module to allow turning composite as always-enabled. SVN revision: 82224