|
|
|
Allegro의 미래
Allegro has evolved into something fairly big, really nice and extremely useful,
and some dust has now settled since version 4.0 was released. The library has
thus reached that point where every little addition or modification may have
side effects on the whole library: now that we have gone multi-platform, it's
not so easy to add features which are available everywhere.
경험적으로 사용중인 라이브러리들의 충돌을 일으키는 몇가지 디자인 실수가
있거나 기존의 API를 재작성한다면 개선될 수 있음을 알 수 있습니다.
하지만 이것은 이전의 Allegro 코드가 새로운 버전에서는 컴파일 되지
않음을 의미하며, 그들의 코드를 모든 라이브러리 버전에 업데이트하려는
프로그래머들이 아무리 많다고 하여도 좋지 않은 일입니다.
그러나 대부분의 Allegro 개발자들은 조만간 적어도 한번은 하위 호환성을
포가하기로 동의하였습니다. 그리고 새로운 API의 형태를 계획하고 있습니다.
사용자 프로그래머인 당신은 현재 API의 개선, 변경, 수정 등을 제안함으로써
Allegro를 개선할 수 있는 기회를 갖고 있습니다. Allegro에서 좋아하지
않았던 것을 (좋아하지 않는 점이 많지는 않지만), 그리고 꼭
필요한 것을 말할 수 있는 기회를 갖는다는 것이 대단하지 않습니까?
To keep track of all progress in the discussion, a directory
has been created at http://alleg.sourceforge.net/future/info.html (there's a cache at
http://sunsite.dk/allegro/future/info.html), with the purpose of keeping all important
documents and design decisions, and to prepare them for the
actual day when a new Allegro will be written. Allegro developers
registered at SourceForge have access to this directory and will
put new documents there from time to time.
For user land discussion, you can use Allegro.cc's forum, where you
can freely post your thoughts, after a short online registration.
There's also a mailing list
at SourceForge, where you can browse the archives and collaborate
actively. So go ahead and make a difference. Remember,
however, that if you want your proposal to appear in
the directory above, you will have to format it in plain
text format and send it to one of the Allegro's developers
(here's a list of them).
Here you have an example on how to
format your proposal.
Finally, for those who might be afraid to use Allegro now because of all this
talk of major changes in the future: we know that there are many, many
programs written with versions 2.x, 3.x and 4.x, and we don't want them to
go to waste either. Therefore we are planning to keep Allegro 4.0 compiling
and to keep bug fixing it for as long as possible. If the new API turns out
to be not so drastically different from the current one, we may provide an
easy migration path.
Of course, development of Allegro 5 has already started. You
can see the proposed roadmap and follow its execution here: http://alleg.sourceforge.net/future/development_roadmap.txt.
|
