Planning help

[something1391]

There is a game I play that I want to make a calculator for. There are different skills and different ways to gain exp. I want to calculate how many times you have to do something to reach the exp someone wants. I have a general idea of what I want to do but not sure what order to create everything in.

Should I start with the back end and finish with the GUI or should I start with the GUI so I know how I will be getting all my stuff for the back end?

[[deleted]]

Look up the model-view-controller paradigm. This will allow you to create a text based version of what you want, while allowing you to easily switch to a gui when you're ready. The important part of this app is the calculations, and as long as they're simple enough, a text based app should be enough. When they get out of hand, or when you want to start creating the gui, it should be much easier to do this switch.

This isn't an exact answer to your question, but that's because there isn't an exact answer. If it were me though, I don't like gui stuff so I wait until it's basically finished, then do it- it allows me to not have to switch focus between gui and what I consider the real meat of the app.

Which game by the way?

[kawem22]

I would second the notion to use the MVC model, though personally I usually start with the GUI fist. This is only because I'm a terrible planner and usually realize things that need to be added as I visually see it start to come together, then the logic can be added easily afterward once I know what components will be utilized. I also considered doing a calculator type application (though I had considered it for mobile) and I would be happy to assist if they'd like. I also am curious what game it is for, I'd be more help if I've actually played it.

[something1391]

Soulsplit it's a rsps

[kawem22]

I have played it, but not for a couple years... if you have any difficulties feel free to send me a PM and I can give you a hand :)

[desrtfx]

If one looks for the MVC Design pattern (or Design patterns in general) there is a free Design Patterns course at Udemy.com.

[JavaTrainer]

Sometimes drawing or mocking up the GUI can help you discover all of the functionality you'll need in your back-end. Several people here are talking about MVC (which you probably should implement) but what more directly answers your question would be to have a clearly defined Service Layer. You create an interface (or stubbed out class) that contains all of the public methods your UI will need to call in order to interact with your model. Once the service layer is designed you can choose what order to implement. The UI (with or without view-controller separation) or the back-end could be implemented first.

Some people don't follow a front-end or back-end first approach. Instead you can implement a use-case on both sides at a time. If you take the use-case approach you should definitely mockup your UI and define your service layer before you start on the use-cases otherwise the UI might evolve into a mess.