fungostar
Still Fresh
@PSyMastR:
nope, niet, niente, nada, kaine docs...
the sdljava project on sourceforge is the only one piece commented and its javadoc are included in the devkit pack, along with all Java source code, that you can use as a starting point for your project
I'm sure that with so many examples, you will find the whole thing really easy to work with
Edit: I mean java documentation, for normal SDL there is LOT of docs as Pickle said.
@Pickle:
yes, AWT and SWING are still unsupported because of their architecture.
AWT and SWING are event based, they rely on the presence of a windowing system that draws the UI and fires "events" like the mouse click, the application just waits for events to come in.
Instead, SDL is the exact opposite, the application draws the screen, move the mouse and manages all UI components.
Porting an application from AWT to SDL is not so simple, because of the different approach they uses, you must rewrite the whole UI that in some cases is the 90% af the application.
IMHO the best is to write a brand new backend for the standard AWT/SWING that drops X11 and "draws the screen"...
by the way, this is the same work to be able to run midlets, write a new backend for the standard MIDP API.
Unfortunately I'm only one, I would be pleased to have time to make AWT and MIDP work, but its a LOT of work, so don't expect this for tomorrow
nope, niet, niente, nada, kaine docs...
the sdljava project on sourceforge is the only one piece commented and its javadoc are included in the devkit pack, along with all Java source code, that you can use as a starting point for your project
I'm sure that with so many examples, you will find the whole thing really easy to work with
Edit: I mean java documentation, for normal SDL there is LOT of docs as Pickle said.
@Pickle:
yes, AWT and SWING are still unsupported because of their architecture.
AWT and SWING are event based, they rely on the presence of a windowing system that draws the UI and fires "events" like the mouse click, the application just waits for events to come in.
Instead, SDL is the exact opposite, the application draws the screen, move the mouse and manages all UI components.
Porting an application from AWT to SDL is not so simple, because of the different approach they uses, you must rewrite the whole UI that in some cases is the 90% af the application.
IMHO the best is to write a brand new backend for the standard AWT/SWING that drops X11 and "draws the screen"...
by the way, this is the same work to be able to run midlets, write a new backend for the standard MIDP API.
Unfortunately I'm only one, I would be pleased to have time to make AWT and MIDP work, but its a LOT of work, so don't expect this for tomorrow