Re: [AD] new API: sub-bitmaps and GUI?

["Eric Botcazou" <ebotcazou@xxxxxxxxxx>]

> Will there be an easy way to change the position of a sub-bitmap relative
> to it's parent?

Given that it would have to work for any type of bitmap, I think it could
not be much simpler than destroying and recreating the sub-bitmap.

> So, if I could move the sub-bitmap around the parent, this problem would
> be solved. It could also be solved if the new API would allow to specify a
> sub-rect for those functions which are "sprite" only right now.

Couldn't you simply define n sub-bitmaps of your root bitmap ?

> Issue2: How's the planning for the new GUI comming along? Once there's
> something you have agreed on, I'd like to help coding in this area. I've
> developed commercial widgetsets for a couple of embeded devices, so I
> think I might be of help in this area.

There is a parallel on-going project, AGUP, that could form the basis for a
more versatile GUI:
    http://www.alphalink.com.au/~tjaden/agup
At some point, it was even suggested to merge it into the 4.2 version.
However, it only deals with the look-n-feel of the GUI.

I'm not a specialist, but I think we shoud make two separate decisions here:
- core GUI engine: should it be rewritten from scratch ? This would require
a clear design, preferably from someone already experienced in this field.
- look-n-feel: AGUP integration ? Skin engine ?

> If the gui routines are moved away from the allegro core, I'd like to join
> the group coding the GUI add-on lib :-)

A basic (at least) GUI is required for the utilities bundled with Allegro
(in particular the grabber), so the core GUI engine is very unlikely to be
spun off from the library.

--
Eric Botcazou
ebotcazou@xxxxxxxxxx