Carsten Haitzler 1c74aaa7e9 Revert "cxx: Fix manual code after efl_app change." ... This reverts commit 135154303b. Revert "efl: move signal events from efl.loop to efl.app" This reverts commit 3dbca39f98. Revert "efl: add test suite for efl_app" This reverts commit 3e94be5d73. Revert "efl: create Efl.App class, the parent of Efl.Loop" This reverts commit 28fe00b94e. Go back to before efl.app because I think this should be done with superclassing here not a parent object. reasons? 1. multiple loops per single thread make no sense. so if multilpe loop objects they wont be contained in a single app object and then deleted like this. 2. the app object is not really sharable in this design so it cant be accessed from other threads 3. it makes it harder to get the main loop or app object (well 2 func calls one calling the other and more typing. it is longer to type and more work where it is not necessary, and again it can't work from other threads unless we go duplicating efl.app per thread and then what is the point of splittyign out the signal events from efl.loop then?) etc.		2018-03-03 13:40:33 +09:00
..
eeze_disk_ls	eeze: move binaries into subdirectories	2017-02-03 10:59:04 +01:00
eeze_mount	cmake: add eeze	2017-02-03 10:59:04 +01:00
eeze_scanner	Revert "cxx: Fix manual code after efl_app change."	2018-03-03 13:40:33 +09:00
eeze_scanner_monitor	Revert "cxx: Fix manual code after efl_app change."	2018-03-03 13:40:33 +09:00
eeze_sensor_test	cmake: add eeze	2017-02-03 10:59:04 +01:00
eeze_udev_test	eeze: move binaries into subdirectories	2017-02-03 10:59:04 +01:00
eeze_umount	cmake: add eeze	2017-02-03 10:59:04 +01:00
.gitignore	eeze: move binaries into subdirectories	2017-02-03 10:59:04 +01:00