@seiyas
Quote:
seiyas wrote:
now question is: When?
Right now it's "When it's Done". I'll try to qualify this a bit.
What we are working on right now is 'widget'. That is the part of Mozilla/Gecko that copes with mapping to the native window system. Gecko assumes a hierarchical system where you have windows and child windows, which we don't have on AmigaOS so we need to simulate this. This has repercussions in the way that e.g. input events are handled (they need to go the "child" window).
Widget is really the biggest chunk in getting the Browser to work on AmigaOS. Once that is done, most of the browser should work. Most of the browser actually DOES work already, however, it will freeze after a second or two trying to display something.
We'd also like to adapt as many Amiga-specific features as possible. For example, I hope we can make the menus work like AmigaOS menus. This will mostly depend on the requirements for menus, and how much needs to be changed within the system to get this to work. Early versions might work without such features and go for the plain stuff.
All in all, we
hope to have an alpha version by the end of the year. HOPE because for one thing we cannot really predict the amount of work left and what kind of problems are still there, and also because the MAP ("most ambitious project") is taking up a lot of time, and will do so even more in the coming weeks, meaning Timberwolf will be going down in terms of time spend on it.
Hope this answers it a bit. As it is now, we cannot give any firm commitment to a date, since all of this
is a hobby project, and I have ArmA II installed on my PC as well