they form more of a logical group, so nothing lost here, just now its
ALL inside conf_display (like conf_applications actually).
ths does NOT mean we merge every category entirely.
for example (this is kind of a plan):
in input i'd merge key bindings, mouse bindings AND i'd bring over
acpi bindings. edge bindings i'd keep alone for now. interaction and
mouse settings i'd merge.
in windows i'd merge everything except window list and window
remembers. window list i'd merge into the winlist module itself as its
the configuration FOR that module (and then config for it i'd move to
its own config file). window rememebrs i'd keep on its own because its
a complex thing that might want to be totally hidden or re-vamped on
its own.
in menus i'd merge client list menu over to the merged "windows"
module (change its name to Window List Menu too).
in language i'd merge both language and input method setting. both
are related to dealing with multiple languages (input and display).
in look i'd leave wallpaper2, and merge wallpaper, theme, colors, fonts,
startup, icon theme, transitions and scaling. i'd merge merge mouse
cursor look over to the mouse settings + interaction module up in
input (but keep it in the look category). borders i'd merge over to
the "big windows merged module" but keep it in the look category.
in advanced i'd merge performance and engine. leave the rest.
in settings i'd leave it as-is.
in extensions i'd move shelves over to the screen category, but keep
it as a module of its own. pager i'd move to the screen category.
leave mixer and connman where they are. everything i'd keep here
- but i'd be tempted to say all the evry modules should be merged into
a single everything modules. they can keep their entries though.
gadgets i'd move over to the screen category
in files i'd merge file icons and file manager modules. keep 2 conf
entries tho (ie conf_mime joins fileman module). yes - i know e has
file selectors and they use the mime conf too, but to most people they
will just accept the file selector as-is and if they want to configure
icons per file tyope.. well.. load fileman module (can turn off
desktop icons if u want).
-------
why do this? fewer modules to load for e. as such e does spend a
fair bit of its startup time thrashing the disk around loading tonnes
of miniature modules. merging them means less thrashing. there is an
argument to be made that these should even become external processes,
but then we'd need to allow them to remote configure e and thats a
complex beastie in and of itself. we could also load and unload some
modules on the fly. this requires extra features in e17's module
setup, but can be done. worry about this for e18/19 etc. for e17 just
reduce the module count to a saner number (outside of the conf modules
which were the worst here, everything and illume are the next worst.
as above - evry could merge i think. illume vs illume2 cant merge, but
i'd consider merging the toggle modules, blutetooth, indicator and home
modules and then the keyboard and softkey modules (as they occupy the same
screen space basically). so that'd take it to illume, illume2,
illume-home, illume-key
how's that for a plan? who wants to help. this is easy stuff really.
just re-shuffling files and makefile.am content and some module
desktop.in files, and inserting some hooks. in module main setup funcs
and.. fixing e config profiles to not load the removed mods.
SVN revision: 58282
Initial module written by Gustavo F. Padovan, I changed it quite a lot
to change some issues... but still many pending, see TODO at the start
of e_mod_main.c
SVN revision: 47160
Remove some commented lines in quickpanel.
Add some printfs to quickpanel sort.
Remove dead code line in illume2 layout.
Separate illume and illume2 modules in build process (this allows illume &
illume2 to be enabled/disabled separately)
SVN revision: 44841
much cleaner.
Remove mode icon from illume2 edj.
Remove gadcon files from illume2 (in own gadget now).
Modify illume2 e.cfg to include illume-mode-toggle gadget and reorder gadgets.
SVN revision: 44671
Do NOT include dirs in EXTRA_DIST (embryo, eet, ecore, evas, edje,
efreet) as it will include .svn directories!
EXTRA_DIST does not take a glob as ETK did, use $(wildcard glob) to
expand it.
And do not forget about adding extra files to EXTRA_DIST (wizard) and
DIST_SUBDIRS (fileman_opinfo).
SVN revision: 40247
* configure.ac:
- require C99 compiler;
- disable F77 and CXX checks;
- per-binary (program) flags, reduce linkage;
- every module can be optionally compiled;
* src/bin:
- Makefile.am: per-binary libs, reduce linkage;
- just add LIBS to LDADD and LIBADD, not LDFLAGS!
- e_sys_main.c: rewrite using proper eina, avoid linking with evas.
* src/modules:
- just add LIBS to LDADD and LIBADD, not LDFLAGS!
- every module can be optionally compiled;
SVN revision: 38009
now). syscon has a poup with buttons (configurale) that offer all the
logout/reboot etc. stuff. also able to extend with more items or inline them
into the theme too.
not complete. need config for being able to extend the syscon popup (and use
it) and no gui config for configuring what should appear and how it should
look. possibly theme should have custon elements for the ones curently using
button + icon look. also no keyboard control.
SVN revision: 37797
can select yourself as a user). also any scaling either calculated from dpi
or set by the user is limited to the min/max values a user can impose (thus
even if you have very low dpi, e doesn't go below a scaling factor you set -
eg 1.0 or 0.5, and same for upscaling).
this should
1. keep all the people who want scalable UI's happy (enable scaling).
2. make e able to (if u want) to adapt to pretty much any dpi screen and
selectively scale just what u want it to.
3. allw you - the user, to be the final controller of just how much to scale
- if you like scaling but think it scales too much - then limit it or set
your own.
right now this will onyl work if your theme supports it... the b&w one does
(mostly). so try that and test. other bits of e need to adapt to this too
(shelf, icon sizes, etc. etc.) as they are not done via edje but code sets
them.
SVN revision: 36211
(well working up to the point whre you can select a network - at that point
connman itself just stares dumbly at you and does nothing - so right now it's
some form of connman bug i suspect). it doesnt save config or load - so you
need to re-init each time and the graphcis are... let's just say.. sucky. for
now theyare test graphics only. suto-connect if network found etc. doesnt
work as well.. can't even connect first time... i can clean the rest up so in
theory it works - but in practice, won't be useful until connmand (back end)
works properly.
SVN revision: 35755
This is the mixer modules as in:
git://staff.get-e.org/users/barbieri/e_module-mixer.git
it's being used with ALSA backend for some time without problems and
it's ready for inclusion. We still lack OSS4 engine.
SVN revision: 35282
Carsten Haitzler
Hannes Janetzek
Christopher Michael
Gustavo Sverzut Barbieri
Joel Klinghed
Vincent Torri
Horms
Viktor Kojouharov