Hello jME community,
the jME 3 standard class for applications seems to be SimpleApplication. My first question is: Is SimpleApplication only meant for testing/playing around or is it also meant for advanced and a bit more complex games?
Second question: How do I turn off the display dialog? (I can’t find the thread where this was asked already)
My next question concerns the jME3 api. The engine version 3 is currently in alpha. Will the api from alpha to beta to final drastically change or can I code stuff now without having to recode it in a later version?
the jME 3 standard class for applications seems to be SimpleApplication. My first question is: Is SimpleApplication only meant for testing/playing around or is it also meant for advanced and
a bit more complex games?
You didn't write your experience level about java and coding game, so I don't know your target. But, anyway, I can tell you that the "Simple" word is a bit misleading, if you are thinking about limit in you development. In effect extending this class you can setup a complete working game, with graphics, GUI, physics, network and all that you want to put in.
SimpleApplication gives you the possibility to start immediatly writing code and see what you've done.
It hides some difficult things about the lower level "Application" [which it extends by the way] and so it allows you to concentrate on shaping your game and forget for a while the true magic which runs under.
Definitely, I recommend to you to start with SimpleApplication and when it will be time to pass on the next level, you will feel it by yourself.
Second question: How do I turn off the display dialog? (I can’t find the thread where this was asked already)
public class Main extends SimpleApplication {
public static void main(String[] args) {
Main app = new Main();
app.setShowSettings(false);
app.start();
}
...
}
My next question concerns the jME3 api. The engine version 3 is currently in alpha. Will the api from alpha to beta to final drastically change or can I code stuff now without having to recode it in a later version?
I leave this response to the devCore Team, even if I think it would be an uncommon trend to change drastically.
c.
myamo said:My next question concerns the jME3 api. The engine version 3 is currently in alpha. Will the api from alpha to beta to final drastically change or can I code stuff now without having to recode it in a later version?
jME3 Alpha-4 is due out late February. As our last alpha we also intend this release to introduce an API-freeze until we reach stable. So after alpha-4 is out, you should be relatively safe, yeah. We can't guarantee there won't be some small changes along the way, but nothing critical. Several people are already developing their games with jME3 and we haven't had any breaking commits that haven't been attended to by and large within 24 hours.
Most of the big API changes should already be in, so if you want to get started right away you probably can. One of the developers should be able to tell you if there is anything in particular to watch out for still.
We are trying to get all API changes implemented in alpha-4 already, beta should be API stable, svn already has some API changes in the physics section as opposed to alpha-3.
In the worse case, changed methods are tagged as deprecated, and will stay as this until final release.