RE: [AL] GUI Idea

[Vincent Penquerc'h <vi...@ca...>]

> It's not that it's not good; your suggestion of having a specific field
> would be better. But this would break 95% of the GUI code out there,
> issuing page after page of warnings (or errors depending on chosen
> compiler options), so it isn't practical. Then again, the GUI system was
> built for the sole purpose of serving the grabber, so it's not exactly
> efficent for more complex tasks.

The base of it is certainly helpful. I coded my own widgetset, who have
a few dozens fields each (*relief*), so I have as much space I need. But
I still use update_dialog, which does the heart of the work. When used
like this, it is certainly good at it. And I might add that this approach
seems quite satisfying to me, neat as my map viewer is a widget that is
handled by Allegro (including clicks on it, etc, etc). But I digress.

> Perhaps it's not too late for a major overhaul of the gui ? Somehow, I
> doubt Shawn would agree...

Someone (Revin Guillen) had begun the work of redoing a whole load of it,
but I haven't heard from him for long. I suspect he ran out of spare
time for it, unfortunately. This means Shawn would probably not be
against it, though I think he'd prefer it to be more 'separate' from
Allegro itself. I can't speak for him tough, so don't take my word for it.

-- 
Lyrian