On Sun, 26 Nov 2017 09:26:16 +0100 Pierre Couderc <pie...@couderc.eu> said:
> On 11/26/2017 04:53 AM, Carsten Haitzler wrote: > > On Sat, 25 Nov 2017 11:05:07 +0100 Pierre Couderc <pie...@couderc.eu> said: > > > >> I am trying to develop a first efl application. > >> > >> Wow. It is no so simple... > > I guess I can only talk about: > > > > https://www.enlightenment.org/develop/efl/start > > https://www.enlightenment.org/docs/c/start > > https://www.enlightenment.org/develop/efl/mainloop > > https://www.enlightenment.org/develop/efl/ecore_idlers > > > > I wrote those. I didn't get around to filling in any of the other > > links/pages there. I did try and cover C as a language in practice (which > > wasn't a short document), and hello world and some loop basics. > > > > Beware the docs/links that are covering our EO beta APIs - do not pay > > attention to them yet. > > > >> 1 - Basic tutorial are sometimes wrong or unreadable. I correct them > >> when possible... > > I just looked at your wiki commits. You're right. Whoever wrote these didn't > > even compile+run their examples. That's bad. > > > >> 2- Some basic tutorials are missing and particularly on Elementary > > A lot is missing. Also there isn't a lot of "impetus" to go write lots more > > because Work is going on for our EO API stuff which actually is a fairly > > different API (though feels similar), and until that's stable and > > released... things are kind of "on hold" as documenting "legacy API" is > > documenting an API we want people to move away from over time to the EO > > based one. > > > >> 2a : Where "container" are introduced ? > > https://www.enlightenment.org/develop/legacy/api/c/start#containerslist.html > > > > Technically it's just a reference, But containers are pretty simple. They > > contain child widgets and control their position/size, etc. etc. > > > >> I seem to understand an horizontal box would be fine for me. Is there a > >> tutorial on that, or a introduction somewhere ? > > https://www.enlightenment.org/develop/legacy/api/c/start#group__Elm__Box.html > > > > also beware elm_obj_* API's - they are the EO API's and are an intermediate > > stage of working on EO for EFL... stick to elm_box* API's > > > >> 2b : I have discovered (not in https://www.enlightenment.org/...) that a > >> fine elementary_test exists. > >> > >> It is a fine tutorial on possibilities of elementary. > >> > >> Where is its source so I can copy/paste elements of it ? > > In the EFL source tree. src/bin/elementary/test*.[ch] files. > > > >> I have soon found a test_entry.c in some bin (???) directory (by a very > >> subtle grep)... > >> > >> Is there some introduction to it ? > > yes. those are the files. They aren't a clean document on their own but a > > very good and well rounded "here is everything and how to put it together > > and make it work. Read this". elementary_test ships with efl. efl installs > > a .desktop file for it so it appears in your app menus (under Development). > > The src is as above. > > > > Our docs do need cleaning up and work. For sure. But the best thing to do is > > ask a question. Get a pointer to something and it'll help you a lot. Like > > elementary_test and it's source. > > > > FYI if I have to work with a library (I have worked with many in the past) I > > first look at on-line docs, if there, if not, I grab the source and look for > > examples, docs etc. dirs or test apps/tools and find the src in the tree. > > EFL has docs panning all these areas. We have an examples dir > > (src/examples). We have tests in src/tests, and tools and whatever are > > src/bin/LIBNAME per library ... and elementary houses elementary_test :). > > > > You can also look at full applications like terminology, Rage, EDI, Ephoto, > > Ecrire ... etc. etc. etc. (Enlightenment itself too but it's huge and > > complex... start with the smaller ones). > After 3 days "à la bite et au couteau", I am more at ease now, and 3 > days is not so much for such a world. > I have improved slightly the wiki where possible. > > Is there an global index independent of the library, allowing to point > on the reference manual ? > For example where do I find the reference for : > evas_object_smart_callback_add ? Gladly, google helps... These are the reference docs for our legacy api's - the complete, but it's separated out library by library: https://www.enlightenment.org/develop/legacy/api/c/start -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- Carsten Haitzler - ras...@rasterman.com ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ enlightenment-users mailing list enlightenment-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-users
