Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MacOS GUI #4

Open
hopskipnfall opened this issue Jul 23, 2017 · 2 comments
Open

MacOS GUI #4

hopskipnfall opened this issue Jul 23, 2017 · 2 comments
Assignees

Comments

@hopskipnfall
Copy link
Collaborator

We need a quick and dirty MacOS GUI for netplay configuration. Basic requirements are:

  1. Choose a server
  2. Enter a console ID or create a new one
  3. Wait until the game start or start it

The next step from there would be to add support for querying what ports are occupied so you can know when to press start
The next step after that would be to add some extraneous mupen config, most notably plugin selection

@hopskipnfall hopskipnfall self-assigned this Jul 23, 2017
@jhertz
Copy link

jhertz commented Jan 8, 2018

assuming no one else is working on this, this is probably something i can do. OSX is my native dev environment, and while i can't write a beautiful GUI, i can definitely do something "acceptable".

just let me know what toolkit we're planning on using the GUI, and when i have some time (probably not til later in jan), i can start working on this

@hopskipnfall
Copy link
Collaborator Author

Hey Jesse this is what I'm working on currently. I'm a stranger to client (especially non-web) dev so I'd be happy get help here if you've got time.

Here are the options we have:

  1. Make a simple (hacky) MacOS application that is easy to run and gives basic editing features for mupen configuration (controller mappings, frame delay settings, etc.).
    • Big issue is I'm having trouble bundling the compiled C++ binary into a macos app that also includes a GUI.
  2. Fork https://github.com/mupen64plus/mupen64plus-ui-python to support our new netplay plugin.
    • Probably a better option for the long run, but probably would take longer.

I've done some work on both of these options. I was waiting until January to get started in earnest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants