next »

[scorch]

So, I am starting with JMonkey Engine SDK, and I've been wondering what would be the best structure for the application (game) so that it would be extendible in the future, allowing me to go as further as I want and have free time to. But I'm not accostumed to it, so I just wanted to know what do you recommend me (mainly Paul).

I already have a lots of experience with .NET Framework, PHP, C, JavaScript, etc... I am familiar with EDP (Events Driven Programming) and OOP (Objects Oriented Programming). So, my question isn't about programming itself, which I am very accustomed to already, but rather to the organization of the project in the SDK, which is my first time working with.

Cumps,
Scorch

[pspeed]

Step 1) go through all of the JME tutorials.

The rest largely depends on what kind of game you are building.  The JME forums are also very helpful with these questions if you don't get what you want here... after all, there are a lot more JME developers over there.

[scorch]

Hum... Ok, I have alredy been through all of the begginers tutorials, and I though them really simple. Perhaps I need to think a little more, but it doesn't seems really hard. My biggest question is:

Packages are like namespaces in .NET, right? If so, should my game be in one package, os should the multiple components be divided into multiple packages that are the joined together in the main package?

I'm sorry for being so annoying...

[pspeed]

Go through the other tutorials also... and maybe some Java tutorials, too.

Yes, you want multiple packages... though starting out with just one isn't bad.

[scorch]

Ok, I'll follow your advice.

[pspeed]

Ok, I'll follow your advice.

Also, while it's a big pill to swallow all at once, there is the MonkeyZone project which might make a decent enough example of a whole application.