| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Causes funky things like black rectangles over the lockscreen and
somewhoe kills focus of popups after unlocking.
|
| |
|
|
|
|
| |
accessible from the normal screen lock dialog
|
|
|
|
|
|
|
|
| |
move pam stuff to separate file
after this commit, the new module "lokker" (or other 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
|
|
|
|
| |
these were previously disabled because hashing a password was too much work (I guess?), but now they're back. config dialog has changed accordingly
|
|
|
|
| |
add a black rect to cover the screen during desklock
|
|
|
|
| |
if we're running in a non-X environment, we can't very well expect that using X calls to hide/show windows for desklock is going to work as expected. now a compositor backend can add a pre or post desklock hook to hide/show its clients as necessary
|
|
|
|
| |
desktop fileman should only receive focus if there is no client currently visible on the active desktop
|
|
|
|
| |
this is a pretty useful function overall, and I found that I was duplicating its functionality in a number of places, so I broke it out
|
|
|
|
| |
if a client's X attributes fail to be fetched on the first attempt, it's possible that we might succeed on a second attempt, which would prevent us from losing a client
|
|
|
|
| |
in some cases, it may be desirable to block shape cutting for an amount of time to reduce cpu calculations. this should be set when performing any non-interactive compositor effects
|
|
|
|
| |
if using an external moveresize implementation, this function is very handy
|
|
|
|
|
|
| |
"just do it" for cool effects
this flag allows a client's layer to be changed instantly with no protocol-level checks or work, allowing compositor effects to do their work more easily
|
|
|
|
| |
the existing moveresize popup infrastructure is very limiting in that it requires you to create a popup. if you don't want to create a popup, now you don't have to.
|
|
|
|
| |
by exposing desk flip as a hookable api, it becomes easy to write custom flip effects such as in the external "desksanity" module
|
| |
|
|
|
|
|
|
|
|
|
|
| |
broken
p16 is a pager replacement module which uses deskmirror to show you live views of each desktop. it has a separate theme and reuses a lot of pager code.
not sure if original pager should be kept, but it's still around for now.
pager and pager16 both provide the same gadget and cannot be loaded simultaneously
|
|
|
|
|
|
| |
recalc gadcons during stop when unpopulating
this caused a lot of slowdown, and even possible crashes, during restarts
|
|
|
|
| |
this is mostly cosmetic, but I thought it might be a little more descriptive?
|
|
|
|
|
|
|
|
|
|
|
|
| |
* finish updating for E19 api
* fix visibility changing on sources
** use that shelf data item added in previous commit to detect shelf visibility
* fix sizing (but not scaling :() and positioning of sources
* also fix stacking
|
|
|
|
| |
allows wayland clients, which only set class here, to find their desktop
|
|
|
|
|
|
| |
terminology
creating phony e_exec instances based on name/class allows wayland clients to show up normally in ibar
|
|
|
|
| |
this fixes a case where cursors would be permanently broken (along with the world) when changing cursor settings
|
|
|
|
|
|
|
|
|
|
| |
pointers in E now come in two flavors, one for each protocol that we currently support. each is created from the owner compositor backend:
X pointers still work as usual
Wayland pointers are actually surfaces that we dump image data into periodically to render them as evas images
some small amounts of hack is necessary to make this work, namely blocking X pointers when a Wayland one is in use if we're running a multi-protocol compositor
|
|
|
|
|
|
|
|
|
| |
adds a probably-working wayland framebuffer output module
Additional authors:
Chris Michael <cp.michael@samsung.com>
Signed-off-by: Chris Michael <cp.michael@samsung.com>
|
|
|
|
|
|
|
|
|
|
| |
module during init
variable takes the name of the output module s/wl_// ; example: E_WL_FORCE=x11
this module allows easy loading of a wayland output module to override any detection which may occur by force-loading the module during startup
in a later commit, an actual output detection mechanism needs to be added to run through all the possible output modes
|
|
|
|
| |
this is the first of the wayland output modules, and it is extremely simple as a result of the compositor rewrite. for any other wayland output modules, it should be enough to simply create an ecore_evas canvas and do startup in this way.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* try to clear up build system for separating out ecore-x
* add #ifdefs for lots of ecore-x stuff
* break out some internal e wl functions for reuse in api
* store wl surface buffers as an inlist
* add protocol-specific client compositor data
** move lots of X client attributes here
* add pixmap type checks to a number of X-specific things, such as grabinput, to block them for non-X clients
* rearrange startup order to work with wayland
* move X screensaver code to e_comp_x
* flag modules still requiring X with -DNEED_X
|
| |
|
|
|
|
| |
this was used in illume, which is now dead.
|
| |
|
| |
|
| |
|
|
|
|
| |
illume 100% requires X, thus illume is dead. replacements are semi-underway.
|
| |
|
|
|
|
|
|
| |
for the default theme
similar to E_MODULE_SRC_PATH, this allows editing a theme without contaminating the current system
|
|
|
|
| |
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 be
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
requested by cedric for profiling, works just like similar elm variable
|
|
|
|
| |
directly from the git directory without installing anything
|
|
|
|
| |
probably good practice to set object data to comp objects? anyway, this makes it easier to use with deskmirror
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
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
|
| |
|
|
|
|
|
|
| |
needing to install modules
this is a useful feature when working on and debugging modules so that contamination of the running system can be avoided
|
|
|
|
|
|
|
|
| |
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>
|
| |
|