On Tue, Jun 24, 2008 at 12:55 PM, Gustavo Sverzut Barbieri <[EMAIL PROTECTED]> wrote: > On Tue, Jun 24, 2008 at 1:46 PM, Jose Gonzalez <[EMAIL PROTECTED]> wrote: >> >> >> Gustavo has a point here. This kind of thing can easily get out of hand >> in complexity and obscurity.. for what kinds of uses, effects, ....? >> I wonder if it might not be 'better' to have such (sync and/or async) >> image loading done by a separate server which would fill or hand out image >> data >> via some ipc mechanism? Then the server can do quite few more things than >> even >> evas does now such as take full paths into account, monitor src file changes, >> give better file info, error reporting, progress reporting, etc. And it can >> implement things via whatever means might be best, and possibly be useful to >> many other apps/libs as well. > > This is out of Evas scope, at least this scope. You can implement such > things for things that are usually shared among lots of apps (ie: > Open/Save/Close icons), just have the main app to do that and share > the memory (shmem or equivalent) and set the pointer of evas image > data.
Its not actually - only yesterday raster and I were talking about it (sharing image and font cache across all apps and libs using Evas), and this idea slots in nicely to fill that gap and to asynchronously load data. -- Hisham Mardam Bey http://hisham.cc/ Codito Ergo Sum (I Code Therefore I Am) ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
