On Fri, 25 Jan 2008 20:46:25 +0100 (CET) Vincent Torri <[EMAIL PROTECTED]> babbled:
seems a good simple start - needs to be more complete, like actually close()ing pips on delete - also i agree with peter, ecore_pipe_add and ecore_pipe_del - also i would add ecore events for pipe data - like ecore_con, and pass the WHOLE data read (not just 1 void* size element at a time). yes - then u need to handle decode of multiple bytes - but that's reality really). so go the event + event struct with pipe data in it + ecore_pipe_add/del and finish off the free stuff and i think you have a winner :) > Hey, > > as i have succedded in integrating the gstreamer thread in the ecore main > loop on Windows, and as some of you talked about a pipe wrapper, I've > quickly written a wrapper around pipe(), read() and write(). > > I have attached the source file to put in ecore/src/lib/ecore/ and a diff. > > There is a complete example that uses that wrapper with gstreamer (the > test I used on Windows, btw) and the documentation is here too. > > That can, maybe, help people to integrate other threads or loops (like the > threaded glib loop) in the ecore main loop. > > feel free to comment :) > > Vincent -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
