first place anyway. shoudl replace the entire dialgo one at a time by
an elm version not try and stuff elm widgets into where e widgets used
to be. this doesnt improve e's config dialogs, just makes them buggy
as all hell in the name of a move to elm.
Revert "e_widget_button -> elm_button conversion"
This reverts commit b1c976d80d.
Revert "update widget size hints when setting a resize object"
This reverts commit fdab0218b2.
Revert "remove no-longer-necessary size hinting in list widgets"
This reverts commit 21479f5019.
Revert "e_widget_textblock -> elm_entry conversion"
This reverts commit 8fe2f00f75.
Revert "e frame -> elm_frame conversion"
This reverts commit e9da6a02fc.
Revert "remove unnecessary size hinting"
This reverts commit b596623efd.
Revert "e_label -> elm_label conversion"
This reverts commit 049b318679.
Revert "set evas size hint min in widget min size"
This reverts commit 2f09aa2fda.
Revert "e_table -> elm_table conversion"
This reverts commit 6434012982.
Revert "remove unused vars"
This reverts commit b19e706b23.
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
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
Mike Blumenkrantz
Carsten Haitzler
Wonguk Jeong
Mike Blumenkrantz
Mike Blumenkrantz
Cedric BAIL