if you have ephysics installed, a new module 'Physics' will be available under Look which provides some fun physics effects on windows such as:
*velocity based on drag direction/speed
*collisions
*gravity
note that the edges of the screen are considered boundaries, and so windows will bounce off or get stuck in them; you will have to drag a window out if it gets stuck because I've disabled physics effects in edge areas to both 1) prevent windows from sneaking past the screen limits and flying off into space 2) actually getting stuck to the point that you can't get them out
help needed!
SVN revision: 73365
it can open files using XDG specification, including defaults.list
(~/.local/share/applications/defaults.list and
/usr/share/applications/defaults.list) and mime type handlers known by
your system.
Now we should get xdg people to detect enlightenment and call this
binary.
SVN revision: 73317
This is used to open a file manager window from another process. It
will use DBus interface:
org.enlightenment.FileManager.OpenDirectory(path)
It returns immediately, but we could enhance the DBus interface and
make it act like a real file manager process if that is needed.
SVN revision: 73084
have done here beyond just "copy the code" is:
1. fix up some code that was useless (didnt need to be done).
2. reformat all the code to be closer to efl/e style guidelines
3. add flags to the gadget popup menu to change keyboard
4. fix lots of warnings
5. fix some correctness in c - () vs (void)
6. added q66 to AUTHORS
7. made it use _() intl macro, not D_() (needed)
8. put xkbswitch module stuff in theme (need some prettying/work)
9. added some XXX: comments on things to do
right now xkbswithc is actually very powerful (thanks q66) but its not
that user-friendly. it lets you add a short-list of "keyboard layouts"
you nee/duse. the gagdet lets you quick-switch between them. this
actually works. it has nice little flaggy things to try help you out.
what we probably need to do is:
1. fix a buffer overflow waiting to happen in the kbdswitch changing.
XXX'd
2. add a wizard page asking for kbd layout
3. double-check that "last used kbdlayout" is actually turned on
4. move xkbd config to core e config (not separate in module)
5. pretty up the gagdet (add a shadow around the flag, some
placeholder if no flag is selected etc.)
6. go over the xkb parser - it looks fragile from a read
:)
SVN revision: 70531
one more todo item being knocked off. but there.
also no proper icon for it yet. mostly code from the old taskbar with
lots of little things fixed.
SVN revision: 64518
it's own utility (as per raster's request/idea). Remove explicit
x_clags in Makefile.am(s) as they are no longer needed.
NB: I added some additional libs to the precache stuffs (even tho it's
not used right now). Also a newer e_main (more optimized).
NB: IF you are brave and want to test this, build evas w/ xcb, build
ecore w/ xcb, then rebuild E. Also, disable building opengl in both
evas & ecore (it's not ready for public consumption when paired w/ xcb).
SVN revision: 61680
full file upload ability on e.org for sharing shot url's, as well as
selecting local file tyo save to, selecting which screen to screenshot
etc.
SVN revision: 59766
enotify is not a hard-dep of e17. The only thing currently using it
correctly is illume-indicator, and that's optionally supported at
compile time of illume-indicator.
SVN revision: 58496
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
to be loaded @ the same time (causes bad things to happen).
This is for Lutin ;) so that users can have some time to transition
their setups to Illume2.
SVN revision: 51908
Vincent Torri
Mike Blumenkrantz
Gustavo Sverzut Barbieri
Sebastian Dransfeld
Christopher Michael
Cedric BAIL
Carsten Haitzler
Eric Schuele
Tom Hacohen
Iván Briano
Hannes Janetzek
Michael BOUCHAUD
Rafael Antognolli
Daniel Kolesa