I got started on one using Evas since I was only able to fix some linker errors. However, it won't be a library, it will be a command-line app since making text appear in OSD form is only a few lines of code. But, I have a question: how does one make an Evas transparent (so that only the text on it is seen)? That's pretty much all I'm missing (except maybe I'll implement a way to manipulate the text's properties in different places later, like a green word between two orange ones). Thanks!
On Mon, 25 Jul 2005 18:45:11 +0200 Tilman Sauerbeck <[EMAIL PROTECTED]> wrote: > Mike Frysinger <[EMAIL PROTECTED]> [2005-07-22 13:39]: > > On Friday 22 July 2005 04:20 pm, Brian Sakal wrote: > > > I figured I may get > > > started on a xosd clone (eosd) since one needs gnome crap for xosd... > > > > esod already exists ... it probably needs to be updated to the new api's > > though ... > > Yeah (Brian contacted me by mail about the compilation error). > Also, eOSD should probably use Evas instead of Ecore_X and Imlib2. > > > last i checked though, it was a drop-in replacment for xosd (which would be > > sweet i think ... have it install an optional xosd.h which provides wrapper > > API to eosd calls) > > I never intended to copy xosd's API 100% (their API sucks balls IMHO). > > Regards, > Tilman > ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
