Zsnes + Flash = SuperFlashNES

[SSJoseph]

[deleted]

[adventure_of_link]

Oh, and don't worry there is nothing illegal about it, since there is no downloading of the actual roms them selves....its basicly a ROM player, powered by zSnes.

Isn't that pretty much what an emulator is designed to do

[SSJoseph]

[deleted]

[Joe Camacho]

I don't really like it.

Lots of those features are already included in zsnes alone, also, can you really describe and have screenshots of ALL the snes roms?

Looks like alot of work with little (or no) benefits.

Edit.- But if you can do it, try it.

[snkcube]

Some of those ideas are.....bleh. Nice try though.

[Malcster]

I have a revolutionary idea. So revolutionary that... ITS ALREADY HERE!!!

For renaming roms, use NSRT! For an IRC chatroom.. use an IRC program, like mIRC! For a Web Browser, perhaps use some sort of web browsing based program! Cheats and info, perhaps find them on the Internet!

A SNES emulator, where you can play just by dropping the rom files in the rom folder, quick saves.. well, I hear there is a program called Zsnes which does that, but I don't know anything about it.

In all seriousness, out of all the stuff you list *some* of it might be worth having. I take it you mean the info and cheats to be a bit like the MAME32 use of history.dat, where you can browse screenshots and stuff with the game list. That's fair enough, and I think when the GUI is rewritten in C it has a chance of getting done.

A final point would be, don't use Flash. This is because Flash is goddamn awful.

[cdbsi]

Lol...sorry bout that part, ya I know that.
Basicly what I want to do is make a more advanced emulator, using the zSnes engine.

I said it before and I will say it again, the MAIN features are....

• SNES Emulator (Duh)
  Plug'n'Play (Just drop the ROM files into the ROM folder)
  Easy Controller Configuration
  Web Browser
  IRC Chatroom
  Cutom UI Themes
  Downloadable Info on any ROM
  Cheat List for Every ROM
  And More...

These are just the main features I want to put in it.
Monor features are from Renaming ROM's, to Quick Save, to Browse by Category.

Also, did I mention that there will be a nice song playing in the backround?



This is definatly not a bad idea...eh?

How would that make ZSNES easier to use? Isn't the current GUI already self explanatory? Maybe if people can't even understand the GUI then maybe they shouldn't even be playing roms at all. Hence, they should go to school instead. I am not sure if I like the "characters" idea because what if a user wouldn't want to see ALL of the characters in a game before they even tried the game? Also, if have they already played the game previously, then why would they need to see what the characters in the game were if they already knew?

I would rather the program display the roms in a detailed list, which could be sorted by year, author, publisher, genre, cart size, etc.

I don't really like the game description idea, either. I would rather that a cart image, box art image and screenshots were displayed.

Also, it will be plug'n'play.
Just drop the rom files into the rom folder, and you will be able to play it.
And if you want, you can download info on that game, if availble.

What, so do you think that ZSNES asks you to solve riddles before you load the rom or something? I thought ZSNES was already "plug'n'play"?

A song playing in the background? Why?

Not much, just stuff like, instead of the ESC button going to the zSnes window, it will go back to the desktop and ask you if you would like to save.

When an emulator is written almost entirely with assembler then it is a little harder than you think to modify it.

I have a revolutionary idea. So revolutionary that... ITS ALREADY HERE!!!

For renaming roms, use NSRT! For an IRC chatroom.. use an IRC program, like mIRC! For a Web Browser, perhaps use some sort of web browsing based program! Cheats and info, perhaps find them on the Internet!

A SNES emulator, where you can play just by dropping the rom files in the rom folder, quick saves.. well, I hear there is a program called Zsnes which does that, but I don't know anything about it.

In all seriousness, out of all the stuff you list *some* of it might be worth having. I take it you mean the info and cheats to be a bit like the MAME32 use of history.dat, where you can browse screenshots and stuff with the game list. That's fair enough, and I think when the GUI is rewritten in C it has a chance of getting done.

A final point would be, don't use Flash. This is because Flash is goddamn awful.

Exactly.

Flash sucks.

[cdbsi]

I think it would be better if someone were to work towards building a multi-system frontend that works off of newly created standards. It could also be a front end for GoodTools (and, if it were to work, NSRT) and load specifics about each game from a standardized database and display them in a detailed list. So that they could be sorted by title, genre, release date, publisher, developer, cart size, amount of times game has been played, etc.
It could also operate off of standardized archives where each system has its own separate file archive and in the archive various images could be stored in various folders. So you first select the system, then you have the ability to select a certain game, then select which version of the game you desire to play (such as v1.1 or v1.0 or jap etc.). When a game is selected you can see various info about the game such as: screenshots, box art scan [front+back], media/cart scan, maps, cheat codes, etc.

It could also be skinnable but by default it is the standard windows "skin".

[Agozer]

I seems that this idea was shot down pretty quickly. cdbsi and Malcster have very strong points and I do agree with them.

[darkbenny]

I like the lady he drew.

[Nach]

I think it would be better if someone were to work towards building a multi-system frontend that works off of newly created standards. It could also be a front end for GoodTools (and, if it were to work, NSRT) and load specifics about each game from a standardized database and display them in a detailed list. So that they could be sorted by title, genre, release date, publisher, developer, cart size, amount of times game has been played, etc.

My team is actually working on that, won't be out for at least another two releases though. In the mean time, take a look at MESS32 I think it can do that.

[Nightcrawler]

So that they could be sorted by title, genre, release date, publisher, developer, cart size, amount of times game has been played, etc.

Yes.. NSRT will forfill most of your wishes here when it's ready. Pat on the back to Nach.

Amount of times the game has been played seems like an interesting idea to me. I'm not sure how one would go about doing that without actually modifying the emulator.(meaning NSRT probably couldn't be made to do this by itself).

I always use the quick pick list in ZSNES of the last few ROMS I have played. It would be interesting to see this feature expanded to say the 10 most played ROMS in each directory or something like that. I can't really think of any sound ideas at the moment.

[Nach]

I'm not sure how one would go about doing that without actually modifying the emulator.(meaning NSRT probably couldn't be made to do this by itself).

Well, if it's loaded from the emulator no. But if it's loaded from NSRT...

[Nightcrawler]

I'm getting tempted to code windows GUI frontend for NSRT. I'm surprised no one has done that yet. I think people would like that.

[kieran_]

I'm getting tempted to code windows GUI frontend for NSRT. I'm surprised no one has done that yet. I think people would like that.

I would love that!

[Nach]

I'm getting tempted to code windows GUI frontend for NSRT. I'm surprised no one has done that yet. I think people would like that.

I would, in fact I'd be willing to help you how I can.
MKendora also suggested I make some sort of socket so NSRT can communicate with a frontend, which I like the idea of, but wouldn't know what data and stuff we want passed back and forth yet.

[Malcster]

I don't suppose you know any portable GUI tookits - TK or whatever? I was writing one for NSRT in Python but I discovered that laying stuff out is evil as boxes just change their shape and size for the hell of it. That project is basically dead in the water right now. A Win32 GUI would be great, especially written by someone who is actually close to the project (well, compared to the guy who wrote the Java frontend anyway), but a portable one would be even better.

[Noxious Ninja]

I don't suppose you know any portable GUI tookits - TK or whatever?

wxPython, based on wxWidgets.

I was writing one for NSRT in Python but I discovered that laying stuff out is evil as boxes just change their shape and size for the hell of it.

Um, that's kind of the point. You specify how things should be layed out, and all the window resizing logic is automatic. Or are you talking about something else?

That project is basically dead in the water right now. A Win32 GUI would be great, especially written by someone who is actually close to the project (well, compared to the guy who wrote the Java frontend anyway), but a portable one would be even better.

[Nightcrawler]

I'm getting tempted to code windows GUI frontend for NSRT. I'm surprised no one has done that yet. I think people would like that.

I would, in fact I'd be willing to help you how I can.
MKendora also suggested I make some sort of socket so NSRT can communicate with a frontend, which I like the idea of, but wouldn't know what data and stuff we want passed back and forth yet.

I think for starters, the frontend would basically just generate the command line string for NSRT based on whatever was selected in the GUI. Then, it would really only need some sort of output from NSRT.

I initially thought it could parse the normal output or just pass the normal output to the user, but when you are say moving several thousand ROMS, that's a large ouput. It might be better if there was some sort of communication from NSRT that the frontend could retreive to know what it's doing, when the command is completed, or if there were any errors etc. Maybe even something related to progress of large commands so the GUI could show a progress bar or something for commnds that take several minutes.

Windows Messaging would be simple to do this, but obviously NSRT won't be using those. There would need to be some other way to communicate between the progams. My mind is just completely dead right now. It's too early in the morning to think, so I can't think of anything. Someone give me some options!

[Nach]

Windows Messaging would be simple to do this, but obviously NSRT won't be using those. There would need to be some other way to communicate between the progams. My mind is just completely dead right now. It's too early in the morning to think, so I can't think of anything. Someone give me some options!

As MK suggested, we'd just use a socket.
TCP to 127.0.0.1, quite easy.

[Nightcrawler]

Windows Messaging would be simple to do this, but obviously NSRT won't be using those. There would need to be some other way to communicate between the progams. My mind is just completely dead right now. It's too early in the morning to think, so I can't think of anything. Someone give me some options!

As MK suggested, we'd just use a socket.
TCP to 127.0.0.1, quite easy.

Sure if you know something about that stuff. I've never programmed a single thing using TCP in my life.

[funkyass]

Sure if you know something about that stuff. I've never programmed a single thing using TCP in my life.

Its really easy.

[Nach]

I do. Basically think of it as just reading and writing to a file.

[Nightcrawler]

Wouldn't I have to deal with all that Winsock BS?

[Nach]

I wrote a lib which hides the BS from you on Windows.