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

Ideas #85

Open
Anuskuss opened this issue Apr 5, 2016 · 18 comments
Open

Ideas #85

Anuskuss opened this issue Apr 5, 2016 · 18 comments

Comments

@Anuskuss
Copy link

Anuskuss commented Apr 5, 2016

Hey @WilliamLCobb, nice to see that you're actively working on iNDS again. Here are some ideas you could include in iNDS:

General / Bugs
  • More information on what a specific option does (e.g. Bicubic Interpolation). Either in iNDS or in a seperate wiki
  • When game is on landscape, the DS touchscreen recognizes touches which are outside of the actual DS touchscreen
  • Sometimes when you're in landscape, and rotate your device to portrait again, the statusbar appers and the app covers it
  • Navigate menu with controller
  • Auto profiles (different games, connected controller etc) -> different layout, different settings
  • Improve translations (I can help you with german but there isn't much to translate in Localizable.strings 😜)
  • Get metadata from thegamesdb (only usefull when you make more design choices)
  • This one is way way down on the to-do list but it might happen: Metal support
Menu layout
  • Add Performance, Audio and Sync section (iCloud, DropBox, Google Drive) / overall redesign
  • [Option] Close rom / restart rom
  • [Option] Enabling/disabling microphone (I hope you can get it to work ☺️)
  • [Option] Advanced Bus-Level Timing (can reduce performance)
  • [Option] Change NDS profile information (Nickname, Message, Favorite Color, Birthday, Language) Edit: since most of them are useless, make sure Language is iOS default language and Nickname is iNDS
  • More game list layouts
In-game layout
  • Hide layout / only show specific buttons (eg Pause) [[Request] hide/unhide controls overlays in real time #45]
  • Enable unhiding layout when a controller is connected
  • Microphone button (if it's too heavy on the framerate)
  • Close lid button (it shouldn't be a flipswitch tbh)
  • Fast-forward button
Functionality
Layout Editor
  • Several crashes like Launch Rom -> Layout Settings -> Edit Profile Layout -> Options -> Discard Changes -> Press a button
  • Resize in Landscape mode (crash)
  • Ability to move Options and Framerate
  • Swap A/B and X/Y
  • Should be accessible from main menu

Hope you can implement some of my ideas.

P.S. Nice work so far. Keep it up!

Edit: I don't know if you want this, but I would like to make a checklist out of the things I described above. Everytime something gets fulfilled, I will edit this post. I hope you like this structure ☺️

@WilliamLCobb
Copy link
Owner

I really like all of these suggestions. I hope to get the microphone working soon and then reorganize the entire interface since it's become pretty clunky. These are some really nice feature that can be added when I do that

@DarknesGaming
Copy link
Contributor

Those seem like really good ideas. And it's nice to see WilliamLCobb developing iNDS again.
I saw your commit to remain at 0.9.10. I don't know how to upload folders without getting the message "This folder is empty."

@WilliamLCobb
Copy link
Owner

The problem is the DeSmuME core was modified quite a bit to make it run on iOS and it's much more complicated than just dropping the newer version in. Also most of the fixes of 0.9.11 were for big endian machines and the iPhone is little endian and doesn't benefit from them. Save states also seem to be working pretty well so the fixes there aren't very helpful either. I'm going to try to update DeSmuME at some point but for now it's at the bottom of my todo list.

@DarknesGaming
Copy link
Contributor

I just managed to build iNDS on Xcode. How does the app alone have over 300 issues?
I'm going to add to the list of ideas: A video on how to build iNDS. What's a release configuration?!

@ghost
Copy link

ghost commented Apr 7, 2016

@DarknesGaming most of the "issues" are actually just apple warnings about what isn't correct syntax or correct use of the programming . They aren't relevant because the app isn't going to be in the app store.

@DarknesGaming
Copy link
Contributor

Ok then. Most or all the issues were only in the DeSmuME files, and I thought they weren't entirely important.

@DarknesGaming
Copy link
Contributor

Let's add to this idea: a button that allows us to delete selected or all save files for ROMs, because swiping to delete over 300 save files that are unnecessary takes forever.
@WilliamLCobb what do you think?

@her
Copy link

her commented Apr 13, 2016

@pmp174 The problem I have with a high issue count is that when we have an issue that may really need to be corrected, we won't know because it's being drowned out by all the other frivolous issues.

So much of DeSmuMe is in Objective-C which could do well to be updated into swift but like @WilliamLCobb is saying... bottom of to-do list

I would like to see an effort to lower this high issue count

@DarknesGaming
Copy link
Contributor

@her most of these issues are Apple warnings. They are not important, and do you really think @WilliamLCobb has the time to fix over 400 issues when they barely matter?
Besides, there's no point in trying because at some point, he might update to DeSmuME 0.9.11 and modify it so it works with iOS. He will probably do that after he finishes the other stuff on the to-do list.

@her
Copy link

her commented Apr 14, 2016

@DarknesGaming they're important from a maintainability standpoint. Additionally the code base could use more comments.

If we made an effort to do some of this it would make it easier for people to contribute which would benefit the project.

@DarknesGaming
Copy link
Contributor

The code base is Xcode and the comments that program makes tells us how we can fix it.
Also, I can make an effort to remove the issues that Xcode has found. I can only reduce the number, not eliminate all issues.

@DarknesGaming
Copy link
Contributor

Since DeSmuME is written in C++, maybe I can learn the code and fix these issues easily using Xcode. I'm assuming it does C++, so this shouldn't be hard, right?
@WilliamLCobb do you think it's better to resolve all the issues that @pmp174 has described unimportant or would it be worth the time to grab the DeSmuME 0.9.11 source code, and modify it so that it would work with iOS?

@Anuskuss
Copy link
Author

@WilliamLCobb What do you think?

@DarknesGaming
Copy link
Contributor

@Anuskuss your updates list on ideas are incredibly awesome!
We should put these on the to-do list. xD

@DarknesGaming
Copy link
Contributor

I'm going to start working on DeSmuME 0.9.11 with Xcode. C++ shouldn't be too hard.
@WilliamLCobb if I manage to get DeSmuME 0.9.11 to run at full speed on an iOS device through a series of tests, would you actually upgrade iNDS to DeSmuME 0.9.11?

@DarknesGaming
Copy link
Contributor

@WilliamLCobb Would you need the source code for Mac OS X or Windows?

@DarknesGaming
Copy link
Contributor

@WilliamLCobb the frame skip option is gone. You think you can bring it back?
It is super useful, you know.

@DarknesGaming
Copy link
Contributor

Too bad this app isn't compatible with Android. All the emulators on the Google Play Store are based off of the same app (nds4droid) and people hardly ever work on them.

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

No branches or pull requests

4 participants