|Age||Commit message (Collapse)||Author|
They no longer require EFL_BETA_API_SUPPORT to be defined.
so the MAIN loop is actually an efl.app object. which inherits from
efl.loop. the idea is that other loops in threads will not be efl.app
objects. thread on the creator side return an efl.thread object.
inside the thread, like the mainloop, there is now an efl.appthread
object that is for all non-main-loop threads.
every thread (main loop or child) when it spawns a thread is the
parent. there are i/o pipes from parnet to child and back. so parents
are generally expected to, if they want to talk to child thread, so
use the efl.io interfaces on efl.thread, and the main loop's elf.app
class allows you to talk to stdio back to the parent process like the
efl.appthread does the same using the efl.io interfaces to talk to its
parent app or appthread. it's symmetrical
no tests here - sure. i have been holding off on tests until things
settle. that's why i haven't done them yet. those will come back in a
for really quick examples on using this see:
they are just my test code for this.
Please see this design document:
This reverts commit 135154303bea691c6f7f9472a5dec32d9103c38d.
Revert "efl: move signal events from efl.loop to efl.app"
This reverts commit 3dbca39f98288580c62a43c179ac11621433ec88.
Revert "efl: add test suite for efl_app"
This reverts commit 3e94be5d73256a7f5c02d3a9474173226be7beff.
Revert "efl: create Efl.App class, the parent of Efl.Loop"
This reverts commit 28fe00b94e55575c15684959b89a614d5a579309.
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
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
ecore_main_loop_get() is really a new "eo api" but it's using our old
ecore_* namespace, so move to the new efl namespace.
using BETA interface.
This should be reverted before next release as this header was only
there during this release cycle.
This reverts commit 2cea85db388d34337676466ef7f50c22e685c7d0.
Their was a typo that I made during cleanup of the patch before pushing that I didn't
notice broke some stuff. But also you may have an old efl_general.h in your elementary
directory that is now being picked instead of the one provided by the tree.
Revert "elementary: currently double declare elm_init/shutdown."
This reverts commit 44bb0c18480f5094fcd0c8be93de87be5c1d78c5.
Revert "elementary: fix efl_ui_multibutton installed headers."
This reverts commit 32a213dc722be2bfec5fb2b513dd556cfb7e9f33.
Revert "elementary: introduce Efl_Ui.h."
This reverts commit df3d3f7334a79f1ab661b31787002f50af59b3f3.
Revert "ecore: do not display error message on cancel."
This reverts commit 99654b7cd29b418e0308be350c8d26208c0905a8.
Revert "efl: and don't forget to install the new dependencies."
This reverts commit 814ffb9b6bd50d498bfd98f4b8a75f1cad3cc0cf.
Revert "ecore: remove EFL_OBJECT_BETA as Efl_Core.h is for Efl new inerfaces."
This reverts commit 619d0f3cff023414feb8f2aaeebf468806c50b44.
Revert "ecore: move EAPI_MAIN from elementary to ecore."
This reverts commit e5d84da864214b9f772808040f22e1614889a25f.
as such commit e5d84da864214b9f772808040f22e1614889a25f starts the
breaking. enlightenment, terminologya and other apps can't compile
against that efl anymore. 619d0f3cff023414feb8f2aaeebf468806c50b44
then makes this even worse with even more header errors and undefined
types. on top of this df3d3f7334a79f1ab661b31787002f50af59b3f3 then
starts making elementary_test segfault when it runs. it wont even
asu such of these 7 commits in the first 4 (that are then relied on
later) 3 of these first 4 cause serious breakage. this simply is a
complete lack of testing changes, so i've rolled fl back to before
these things so it builds and works again and you can build against it.
PLEASE test these things. this looks ot me to be obviously a lack of
any testing... :(
This make EFL_MAIN available and working with just Ecore. For simplicity
it is available with Efl_Core.h. Ideally it should also work with Efl_Net.h
alone and finally with an Efl_Ui.h.