DarkJezter
New member
Well one of the things that kinda concerns me about the directions this emulator is going is that right now, we have two separate graphical frontends, and with the win32 branch I suspect there may be another around the corner (unless I'm just totally wrong about how that project's going) On top of this, there are many components that need graphical frontends, for example the debugger and the cheat code interface, heck, even the plugins.
Right now, if we want to add a feature that needs a gui, to some extent we either have to either pick a toolkit, or implement a seperate gui for each toolkit.
Either we need to make sure we have a nice clean segregation between the functional code, and frontend code to make it easy to code multiple gui's, or else we need to come up with a framework that will allow backends to create their own frontends irrespective of the toolkit used.
Just some thoughts I've had. The easiest solution is no doubt to scrape as much functionality as possible out of the frontend code and try to define some kind of guidelines for what the backend interfaces to the various frontends should look like.
Any thoughts or impressions?
Right now, if we want to add a feature that needs a gui, to some extent we either have to either pick a toolkit, or implement a seperate gui for each toolkit.
Either we need to make sure we have a nice clean segregation between the functional code, and frontend code to make it easy to code multiple gui's, or else we need to come up with a framework that will allow backends to create their own frontends irrespective of the toolkit used.
Just some thoughts I've had. The easiest solution is no doubt to scrape as much functionality as possible out of the frontend code and try to define some kind of guidelines for what the backend interfaces to the various frontends should look like.
Any thoughts or impressions?