Re: What to do?
Posted: December 19th, 2019, 11:05 am
Hey, thanks for the reply.
I understand what all the patterns are trying to accomplish ( decoupling ), so maybe you're right about finding something that fits me I suppose. The couple of times I did attempt implementing the MVC pattern, one thing I noticed was I felt less restricted knowing that all the graphics related stuff was separate. I felt like I had more freedom to work on a single portion of logic. Words are failing me right now. I think I will go back and try using my own interpretation of the MVC pattern on this project and see how far I get. For one, I want to change to using transformable sprites and I have some things to change that hopefully make it easier to make the graphics changes.
One thing that I think I might get hung up on is how state changes are going to be handled. I guess the first thing I need to decide is the roles each structure will have; are Models going to be the data or the simulation step, if Models just store data then the Controllers can handle the simulation step and state changes ( basically a bridge between View and Model ). In one description, the View would inform the Model about inputs, but I think the Controllers will handle input, so when the user presses Esc during gameplay, the GameController would change the View from PlayView to PauseMenuView.
Thanks for trying the game out, glad you liked what you seen so far. I only got to play 1943 a few times when we'd go visit my aunt who lived 7 hours away, so not very often. I did play a game called Air Fortress on the NES. It was a two parter. The first part was a side scrolling space shooter and then you land on an air fortress. From there, it was a platformer of sorts, but you could fly instead of having to jump everywhere. That one would be kind of fun to clone.
Anyway thanks again and I'll definitely be posting here as often as the project allows.
I understand what all the patterns are trying to accomplish ( decoupling ), so maybe you're right about finding something that fits me I suppose. The couple of times I did attempt implementing the MVC pattern, one thing I noticed was I felt less restricted knowing that all the graphics related stuff was separate. I felt like I had more freedom to work on a single portion of logic. Words are failing me right now. I think I will go back and try using my own interpretation of the MVC pattern on this project and see how far I get. For one, I want to change to using transformable sprites and I have some things to change that hopefully make it easier to make the graphics changes.
One thing that I think I might get hung up on is how state changes are going to be handled. I guess the first thing I need to decide is the roles each structure will have; are Models going to be the data or the simulation step, if Models just store data then the Controllers can handle the simulation step and state changes ( basically a bridge between View and Model ). In one description, the View would inform the Model about inputs, but I think the Controllers will handle input, so when the user presses Esc during gameplay, the GameController would change the View from PlayView to PauseMenuView.
Thanks for trying the game out, glad you liked what you seen so far. I only got to play 1943 a few times when we'd go visit my aunt who lived 7 hours away, so not very often. I did play a game called Air Fortress on the NES. It was a two parter. The first part was a side scrolling space shooter and then you land on an air fortress. From there, it was a platformer of sorts, but you could fly instead of having to jump everywhere. That one would be kind of fun to clone.
Anyway thanks again and I'll definitely be posting here as often as the project allows.