Go to file
Carsten Haitzler 7d39369434 bluez5 - add device specific options like unlock and force connect
i added 2 more device specific options, so i had to move all of the
device controls to an expandable button set. it's not brilliant
actually. the icons are poor and these probably should become toggle
like states rather than a button with an action. it's just not that
intuitive. this i think needs more theme styles in elm core theme
though, so for now keep what's there. but this was necessary due to
the ever expanding set to keep space usage sane.

now the 2 features are "force connect" for any device that is
discovered and responds to pings - connect to it if not connected.
this seems to not always work and maybe this should eventually be
removed, but this leads to there needing to be config per device so we
now have config storage for that like adapters.

the other feature which is much more interesting is the unlock
feature. this means if that bt device is around and responds to pings,
e will unlock (and only explicit manual locking will lock it), but
when that bt device stops responding to pings, e will lock. you could
use your phone, or smartwatch or any other bt device you have on your
all the time as some unlock device.

this required the fixing of the l2ping support in e_sys and i've fixed
it to properly work now and added an optional timeout value as input.
the unlock feature uses this and it pings bt devices on a frequency
that depends on e's powersave state which is dependent on if on ac, or
battery and what battery level is if you have the battery module
running. a handy feature to have just there at the click of a button.

i've kept the printf logging in for now so people trying it out get
some semblance of logging and state so they could figure out why
things are doing what they do and maybe debug it more easily.
2018-12-15 16:13:28 +00:00
data add rfkill actions to sysactions.conf - necessary for bluez 2018-05-18 21:45:20 +09:00
doc remove autotools 2017-11-20 07:05:36 -05:00
meson meson: make those scripts executable 2017-11-04 10:40:55 +00:00
po Updating italian translation 2018-11-07 08:03:26 +01:00
src bluez5 - add device specific options like unlock and force connect 2018-12-15 16:13:28 +00:00
.arcconfig update arcconfig key:values for new phabricator api 2018-05-11 09:47:20 +02:00
.gitignore remove autotools 2017-11-20 07:05:36 -05:00
.mailmap More mailmapping 2016-09-13 15:14:21 +09:30
AUTHORS AUTHORS: use netstar's real name. 2018-03-22 15:38:43 +00:00
BUGS Fix common misspellings 2010-09-08 23:59:07 +00:00
COPYING E17: Update copyright year. 2012-07-03 06:54:49 +00:00
ChangeLog E18.0 release 2013-12-21 17:08:47 -05:00
INSTALL readme/install - use standard INSTALL file like autofoo projects 2017-12-17 09:53:54 +09:00
NEWS 0.22.0 NEWS updates 2017-11-02 08:59:37 -04:00
README readme/install - use standard INSTALL file like autofoo projects 2017-12-17 09:53:54 +09:00
README.wayland remove autotools 2017-11-20 07:05:36 -05:00
autogen.sh add back an autogen.sh to help minimize confusion 2017-12-17 09:49:20 +09:00
e19_workdir_setup.sh feature: add script to set some debug vars 2014-01-14 20:28:29 -05:00
meson.build meson: bump required version 2018-11-01 23:16:23 +01:00
meson_options.txt bluez5 support - a new module with gadget etc. 2018-05-18 21:45:20 +09:00
netwm.txt add support for new netwm csd X atoms 2015-01-03 00:42:42 -05:00
x-ui.sh remove e17 preload/precache hacks 2012-10-10 07:39:08 +00:00
xdebug.sh xdebug: add clouseau_start 2016-01-08 19:19:06 +01:00

README

Please report bugs and send patches to phab.enlightenment.org

Enlightenment

Requirements:
-------------

Must:
  efl
  libc libm libX11 libXext
  xcb xcb-shape xcb-keysyms

Heavily suggested:
  evas_generic_loaders (all loaders)

NOTE: Users of DR16 will need to rename the $prefix/bin/enlightenment
file prior to installing this release or it will be overwritten.

NOTES:

* if you do not want security issues make sure sysactions.conf is in
/etc/enlightenment (not PREFIX/etc/enlightenment) as this is the first place
it looks at. This file is intended to be customized by packagers and
system integrators to match your policies and scripts/tools.