1 Jan 2008 08:56
Re: [E-devel] E CVS: apps/e devilhorns
Vincent Torri <vtorri <at> univ-evry.fr>
2008-01-01 07:56:12 GMT
2008-01-01 07:56:12 GMT
On Mon, 31 Dec 2007, Hisham Mardam Bey wrote: > Thanks for the links, but that is really not my point here. My point > is that if someone walks in and tries to figure out what these > functions really do, there's no way of doing so (unless you consider > reading the source code then jumping over to the FDO documentation a > good way). which functions ? * ecore_x_screen_is_composited : i've not added it, and you can see a description in ecore_xcb_netwm.c. The doc in ecore_x_netwm.c is not that detailed. * all the _prefetch functions : I've documented ALL the code in the xcb backend, using sometimes the X specifications to describe the functions. in both cases, doxygen documentation can be generated to see what these functions do. Is it sufficient ? Should we detail more those documentations ? anyway, happy new year :) Vincent ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005.(Continue reading)
I also tend to agree with
> > raster's API choice of using the existing event model.
> >
> > I would like to see the removal of the _async calls entirely and get
> > this to the point where we have essentially 2 exposed calls. The first
> > is the traditional blocking call, while the second is a _request or
> > _prefetch call. Below are my ideas of how this could work, but you are
> > far more familiar with the XCB specifics so please let me know if a
> > part of this is not feasible. There is also the possibility that
> > extensions could be made to XCB to support some of this behavior.
RSS Feed