Re: [E-devel] Edje and DirectFB

[Carsten H. (T. R. <ra...@ra...>]

On Fri, 31 Oct 2003 04:07:17 +0100 Hallvar Helleseth <ha...@ii...>
babbled:

> On Fri, 2003-10-31 at 01:21, Carsten Haitzler wrote:
> > > Does your text in DirectFB-evas show up correct? Doesnt here, tried
> > > differnt stuff with the code but just wont work.... 
> > 
> > last time i looked (like 6 months ago) it did! :)
> 
> May I ask which version of freetype you use? could that be the reason
> you think? anyways, Ill look into into.

2.1.4

> > aaah yeah. dfb's loaders... yup yup. forgot.. :) for now i'd just let evas
> > do the loading and just dump the pixel data to a dfb surface :)
> 
> Maybe its a good idea to load all images with evas not using the
> DFBImageProviders..?

probably. especially since in he future i will add more loaders & add modular
loader thingy :)

> > > oh and it be REALLY helpfull if evas was more verbose on errors such as
> > > not beeing able to load an image of a certain format.. or some other
> > > sort of error handling (or am I missing something as always..?) maybe
> > > edje should be the one telling about the error..
> > 
> > yeah. it does have error checking. but its pretty damn basic :) i need to
> > formalize the whole loader api at some point - thats when i'll fix all of
> > that up :)
> Not to complain about your coding style, but DFB really has nice error
> checking, although not possible to do it the way DFB does with evas
> though...

yeah... but hey :) for now "it works" has been important to me. detailed error
handling is a LOT of work (to do overall) and so often gets a bit skipped :)

> > hmm yup. works. definitely. but its synchronous lock-step. dont think i like
> > that. heres' what i'd do. i would have the "event" thread wait for the next
> > event and when it happens read the event info and write a data struct down
> > the socket to the main thread and then have the main thread read the data
> > form the socket and use that. now you get pipelining and buffering and no
> > need to lock-step back and forth PER event. :) that'd be the way imho to do
> > it :)
> Ill leave it for now, actually I think it works the way you want, but
> not sure. You can take a look if you want when I finish the patches.


yeah - but it does mean lock-step :( and thats awful for performance and
idle-time rendering etc. :(

> Hallvar Helleseth
> 
> 
> 
> -------------------------------------------------------
> This SF.net email is sponsored by: SF.net Giveback Program.
> Does SourceForge.net help you be more productive?  Does it
> help you create better code?   SHARE THE LOVE, and help us help
> YOU!  Click Here: http://sourceforge.net/donate/
> _______________________________________________
> enlightenment-devel mailing list
> enl...@li...
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel


-- 
--------------- Codito, ergo sum - "I code, therefore I am" --------------------
The Rasterman (Carsten Haitzler)    ra...@ra...
熊耳 - 車君                         ra...@de...
Mobile Phone: +61 (0)413 451 899    Home Phone: 02 9698 8615