search

HypeSwarm / EVE-Indy-Offline

4 stars 0 forks source link

Consider seperating the code with MVC #1

Open Kad1n opened 4 years ago

Kad1n commented 4 years ago

MVC (Model View Controller) would be a great way to separate the UI, data models and control structure of this application. As it is now, its a mix of UI functions, data functions and conversion functions. I would suggest working on the data model first, and then write the UI on top on that foundation.

With different views, we can easily add different functionality for the user. For instance manufacturing could be a view. If need be we can simply create a new view, for example invention. We would only need to pass the raw data objects from the model in order for the view to present it in the GUI.

For more information about MVC, see the wiki page on Wikipedia.

HypeSwarm commented 4 years ago

Well I got no idea how to do something like that yet. (Don't think we have gotten to that in the TAFE Course I am doing yet).

Though the whole UI -> Listeners -> Separate Classes are areas of the UI (That get/modify the Data and update UI)-> DataArrayLists sorta works. But probably could try a MVC at some point. This is Alpha for a reason :P