[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
On Friday 06 August 2004 01:49, Bobby Ferris wrote:
> Is there anything besides what is in todo.txt to be done? i was thinking
> about (if it is ok and there isnt anything else that is needed) a better
> grabber/virtual file system setup or a gui rewrite.
I personally think we should look into making the GUI like a default plugin
that isn't part of the core Allegro DLL or .so library, but this is really
something that would need to be discussed properly.
I suspect it's possible to pull out the GUI code and build a shared library
without it already. Not a prime issue though, I guess...
If you have ideas for the grabber/datafile system, by all means discuss
them. This reminds me that Chris send in a patch dealing with # in
filenames that I don't remember being applied, so I'll have to look at
that one again.
Other than that, we have been discussing evolving the API to something like
the originally proposed Allegro 5. If there is consensus on this (I'd
personally like to have another look at the draft or discussion to
familiarize myself with it), we could always use a hand with that.
Initially, this would be wrappers around the current API, with the tables
being turned at some later point.
Personally I think the setup program is in bad need of an update too.
Another thing that was discussed recently is getting rid of set_gfx_mode/
set_color_depth and make a more robuste graphics system that could handle
things like triple/double buffering automatically. This may actually be
something that should be done in the context of evolving to Allegro 5
rather than redesigning things from scratch.
Then there's always feature requests dealing with improved hardware
acceleration on Allegro.cc, so I guess that is something that could be
looked into aswell.
These are just some things off teh top of my head. Not suggesting you get
round and do them all ;)
Some discussion on these points and comments from other developers may also
be useful.
Evert