On Tue, Apr 5, 2016 at 1:13 AM, Carsten Haitzler <[email protected]> wrote:
> Referring to:
>
> http://git.enlightenment.org/core/efl.git/commit/?id=6291c61556a531da874242830689e37362db1638
>
> and follow on commits that init this and make use of it. Welcome to...
>
> VPATH (:
>
> >From now on all EFL code will be happy.... full of smiles... OR ELSE! :)

Why so much happyness ? This is disturbing ! More serious question,
why not the more usual '$' or '${}' or '$()' ? Not a big fan of this
custom to EFL marker. $ sounds more used and understandable by
everyone I think.

[snip]

> Anyway what is VPATH?

This is something people may ask themself or never even look at what
it is, but you who like short name so much, why bother with V at all ?
I find it confusing and we are going to handle all our PATH through it
anyway. So why not just PATH ?

[snip]

> etc. - these will require vpath actually fetch/cache the file, downloading it
> and then finally waking up giving the resulting local "cached tmp file" path.
> this of course requires mainloop object support to be used/glued in ... thus
> why vpath is initted when ecore inits. i can get to this when a mainloop 
> object
> can be glued in.

Ok, I was guessing this should actually either be a property of the
main loop object or be related to it with parent/child relationship. I
will look at fixing that part when I go later on at mainloop.

I am actually thinking this could be a good use for promise. The main
loop would return you a promise to an Eina_File directly and we can
extend Efl_File to get an Eina_Promise. So you would do :

efl_path(main_loop, &promise_file,
"ssh://[email protected]/~/bork.secret");
efl_file_promise_set(image_object, &promise_loaded, promise_file);

And this would do everything asynchronously for you (I find it quite
clean and neat, but that's maybe me).
-- 
Cedric BAIL

------------------------------------------------------------------------------
_______________________________________________
enlightenment-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to