"Brian S. Julin" wrote:
>
> I guess someone has to step up to the plate here... please
> everyone forward me lists of TODOs and bugs. If you have
> the time, try to divide them into these categories:
>
> 1) Critical for a LibGGI major version bump (e.g. non-beta release)
ok, I guess in order to get a non-beta release out the door, we should
restrict the TODO list for this one to real bugs and regressions
(introduced
by the changes to the extension loading for example).
> 2) Critical for another LibGGI BETA release
> 3) Not critical, but definitely broken
here is one thing that I consider broken (but which is arguable):
The visual structure contains a `size` member, yet it is currently not
used. As we already discussed (and agreed !) a couple of months ago, we
should find a way to fill these variables in a meaningful way. For some
visuals this is accessible from h/w, on others we have to put it into a
(central !) config file. The point is really that a user of libGGI
should
be able to expect to query the physical dimentions of the visual,
instead
of all applications having to provide their own calibration window.
> 4) Wishlist.
I`d like to finalize the IPC target as soon as possible. Unfortunately,
it currently doesn`t draw anything. The communication works, i.e.
ggiFlush
correctly wakes up the other side, which crossblits the visual into its
own, but
nothing gets drawn. If anyone wants to help debugging, he would be very
welcome.
A demo is in programs/demos/wrap.c.
In fact, I would hope that the issue os only a minor one, such that we
can fix
it even for the next release. But if it is not, I won`t hold you back
either.
Regards, Stefan
