[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> I can see how resizing doesnt really fit with the current API, but I
> think it could be worked in.
Yes, but I'm starting to think that it will mostly be a hack job: trying to
fit Allegro into a jacket it was never supposed to wear. Given that we
plan to redo the graphics system and drivers after 4.2 anyway, I'm not
sure its worth hacking it in at this point.
> callbacks wont go away till at least 4.2.0,
> right?
They'll be in 4.2, but as Peter said, we don't want to add more stuff to
the compatibility layer later on than we have to.
> Additional functionality that uses callbacks should be able to go
> into the current API.
Yes, but I'm not sure now if this is the right time to do so for resizable
windows. I think we should put the current API in feature freeze sometime
next week and prepare for RC1 if we want to have a 4.2.0 in (mid/late)
Januari. This leaves preciously little time for something as large and
drastic as this... so at this point, I'm tempted to say that we should
postpone this for 4.3.0, at least.
Evert