Yeah, like pf's screenshot uses it too.Noxious Ninja wrote:That's a status bar. Tons of GUI programs use those.KaOSoFt wrote:I like Nach's one because it's simpler, but there is something I don't like. The bottom edge at emulation screen, I think game image should limit with windows one, not like that not-filled space there.
In development
Moderator: ZSNES Mods
-
- ZSNES Developer
- Posts: 3904
- Joined: Tue Jul 27, 2004 10:54 pm
- Location: Solar powered park bench
- Contact:
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________
Insane Coding
_____________
Insane Coding
-
- Romhacking God
- Posts: 922
- Joined: Wed Jul 28, 2004 11:27 pm
- Contact:
Well, he said it would use the standard windows Open File dialog box.. so that fixes that in Windows. I could care less about any other version.Noxious Ninja wrote:You... like the file chooser?Nightcrawler wrote:Nice to see ZSNES is finally catching up to the new millenium.
Perhaps this will pave the way for a debugging interface in ZSNES.
If I had to choose, I think I like Pagefault's GUI better.

Besides, you can add a shortcut to your ROMs directory on the left hand side. I don't think it's that bad even if that is the one.
[url=http://transcorp.romhacking.net]TransCorp[/url] - Home of the Dual Orb 2, Cho Mahou Tairyku Wozz, and Emerald Dragon SFC/SNES translations.
[url=http://www.romhacking.net]ROMhacking.net[/url] - The central hub of the ROM hacking community.
[url=http://www.romhacking.net]ROMhacking.net[/url] - The central hub of the ROM hacking community.
YES! Please god don't make every setting menu-based like VBA. Or at least have both menu-based and dialog-box based (seen somewhat in Snes9x). It's very time-consuming and annoying to change multiple settings when browsing through a menu.creaothceann wrote:Personally, I don't like menus (especially as in VBA) - they have the annoying nature to vanish after selecting an option. Why not make one menu button called "Settings", and open a window with tabs...
Last edited by Jipcy on Wed Jul 13, 2005 5:38 pm, edited 1 time in total.
[url=http://zsnes-docs.sf.net]Official ZSNES Docs[/url] | [url=http://zsnes-docs.sf.net/nsrt]NSRT Guide[/url] | [url=http://endoftransmission.net/phpBB3/viewtopic.php?t=394]Using a Wiimote w/ emulators[/url]
-
- Dark Wind
- Posts: 1271
- Joined: Thu Jul 29, 2004 8:58 pm
- Location: Texas
- Contact:
-
- Veteran
- Posts: 970
- Joined: Fri Jan 21, 2005 11:15 am
- Location: Montana, United States
I don't suppose there will be a command line only version?
Damnit all to hell I am a moron. I vote QT. Though PF's looks just as good.
Damnit all to hell I am a moron. I vote QT. Though PF's looks just as good.
Last edited by SquareHead on Thu Jul 14, 2005 10:53 am, edited 1 time in total.
So this is the top secret stuff you were talking about in IRC? Nice work but a main reason I've always used zsnes instead of snes9x is because of its conveniant interface. With a few keys you can do anything you need to. The new interface would change all that... When the new GUI is used is it possible to also update the old interface?
pagefault wrote:Also the old original GUI should be still available in all ports as long as the DOS version is around.
[url=http://zsnes-docs.sf.net]Official ZSNES Docs[/url] | [url=http://zsnes-docs.sf.net/nsrt]NSRT Guide[/url] | [url=http://endoftransmission.net/phpBB3/viewtopic.php?t=394]Using a Wiimote w/ emulators[/url]
My question is:
Will you be able to load roms with just a controller (with an arcade machine for example)? With the current GUI you can assign a key to "load" and then use joypad1 to select a rom. If you can use joypad1 in the select rom dialog boxes, than I'm all for the gui change.
Also, can you use the menu (and the load rom dialog box) in fullscreen? Or does it have to go to windowed mode first? Honestly, this is the thing I like most about the current GUI: you never have to change resolutions once zsnes has loaded. I vote for whichever gui can do this.
An excellent example is kega fusion's load rom dialog box -- it comes up in full screen. If this would work with a controller, it would be perfect.
Will you be able to load roms with just a controller (with an arcade machine for example)? With the current GUI you can assign a key to "load" and then use joypad1 to select a rom. If you can use joypad1 in the select rom dialog boxes, than I'm all for the gui change.
Also, can you use the menu (and the load rom dialog box) in fullscreen? Or does it have to go to windowed mode first? Honestly, this is the thing I like most about the current GUI: you never have to change resolutions once zsnes has loaded. I vote for whichever gui can do this.
An excellent example is kega fusion's load rom dialog box -- it comes up in full screen. If this would work with a controller, it would be perfect.
To truly own, you must own at all games.
-
- ZSNES Developer
- Posts: 3904
- Joined: Tue Jul 27, 2004 10:54 pm
- Location: Solar powered park bench
- Contact:
I don't think it's fair to vote until pagefault shows off what he did with his.IceFox wrote:I added a poll for determining which API is more popular.
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________
Insane Coding
_____________
Insane Coding
-
- Dark Wind
- Posts: 1271
- Joined: Thu Jul 29, 2004 8:58 pm
- Location: Texas
- Contact:
The GTK folks need to get with the times and write a skinning engine to use Qt themes.tehnick wrote:Definitely GTK, just about all of the popular Linux programs use it. I would like it to fit in with my other skinned GTK apps.
Last edited by Noxious Ninja on Fri Jul 15, 2005 1:37 am, edited 1 time in total.
[u][url=http://bash.org/?577451]#577451[/url][/u]
Great work guys! I don't mind what you guys do to the GUI, just as long as you keep the GUI background effects such as snow, water, and the burning effect. If the new version didn't have the snow effect, then it wouldn't feel like ZSNES to me!
I am sure that someone could create a skin that could be a good replacement to the old GUI.
I really like the GUI for Project 64, where there is a mixture of options in a menu, and in settings windows. I also like the way that the rom is selected, with the sortable detailed list.
AWESOME!
Keep up the great work guys!
I am sure that someone could create a skin that could be a good replacement to the old GUI.
I really like the GUI for Project 64, where there is a mixture of options in a menu, and in settings windows. I also like the way that the rom is selected, with the sortable detailed list.
AWESOME!

Last edited by cdbsi on Fri Jul 15, 2005 7:43 am, edited 1 time in total.
-
- Regular
- Posts: 271
- Joined: Tue Jun 14, 2005 8:35 pm
-
- Dark Wind
- Posts: 1271
- Joined: Thu Jul 29, 2004 8:58 pm
- Location: Texas
- Contact:
-
- Rookie
- Posts: 12
- Joined: Tue Jul 12, 2005 11:40 pm
- Location: Victoria, BC Canada
- Contact:
-
- ZNES Developer
- Posts: 215
- Joined: Mon Aug 02, 2004 11:22 pm
-
- ZSNES Developer
- Posts: 3904
- Joined: Tue Jul 27, 2004 10:54 pm
- Location: Solar powered park bench
- Contact:
Qt 4 does not have 1 MB overhead. Only a few hundred KB.c61746961 wrote:Qt feels a little stiff to me (can't explain better), plus it has more than 1 Mb overhead.
What's the overhead for each version?
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________
Insane Coding
_____________
Insane Coding
Go with Qt.
For all the claims that Qt is bloated, there is little evidence to support it. Qt does take longer to compile than GTK2 with the GNU compiler collection, but there's a more significant reason for that. Qt is primarily C++, and GTK is primarily C. Comparing their compilation times (which differ by about fifteen minutes on my newest machine) is an invalid comparison -- the compiler is not the same. There have been assertions that GCC 4 has a much improved g++ compiler (as far as speed goes), but there is little experimental data for that as well.
Qt is a more robust and responsive toolkit from what I've seen in programs that use it. Simple elements such as the drawing of widgets meld better with the overall operating system. This is part of the actual library itself, not any individual cross-platform implementations. Use GTK and Qt in both win32 and several linux distributions to see what I mean.
Comparing the runtime libraries of GTK and Qt is often folly, because both have optional dependencies. GTK's runtimes can get up beyond 20 mbyte if one starts taking in code from GNOME, for example. How large either toolkit is depends on several factors: what components are built, whether the library is compiled for debugging, and whether you statically link the runtime or create shared libraries. From my experience, Qt has been somewhat smaller.
Qt 4 is GPL'ed, so GTK advocates no longer have that as any sort of advantage.
Many programmers support both toolkits, with most of the modern thinkers leaning towards Qt. A C++ API means extensibility (such as the creation of new widgets) is simpler and thus easier for programmers who like object-orientation.
For all the claims that Qt is bloated, there is little evidence to support it. Qt does take longer to compile than GTK2 with the GNU compiler collection, but there's a more significant reason for that. Qt is primarily C++, and GTK is primarily C. Comparing their compilation times (which differ by about fifteen minutes on my newest machine) is an invalid comparison -- the compiler is not the same. There have been assertions that GCC 4 has a much improved g++ compiler (as far as speed goes), but there is little experimental data for that as well.
Qt is a more robust and responsive toolkit from what I've seen in programs that use it. Simple elements such as the drawing of widgets meld better with the overall operating system. This is part of the actual library itself, not any individual cross-platform implementations. Use GTK and Qt in both win32 and several linux distributions to see what I mean.
Comparing the runtime libraries of GTK and Qt is often folly, because both have optional dependencies. GTK's runtimes can get up beyond 20 mbyte if one starts taking in code from GNOME, for example. How large either toolkit is depends on several factors: what components are built, whether the library is compiled for debugging, and whether you statically link the runtime or create shared libraries. From my experience, Qt has been somewhat smaller.
Qt 4 is GPL'ed, so GTK advocates no longer have that as any sort of advantage.
Many programmers support both toolkits, with most of the modern thinkers leaning towards Qt. A C++ API means extensibility (such as the creation of new widgets) is simpler and thus easier for programmers who like object-orientation.
-
- ZSNES Developer
- Posts: 3904
- Joined: Tue Jul 27, 2004 10:54 pm
- Location: Solar powered park bench
- Contact:
As is Qt 3.Kagerato wrote: Qt 4 is GPL'ed, so GTK advocates no longer have that as any sort of advantage.
May 9 2007 - NSRT 3.4, now with lots of hashing and even more accurate information! Go download it.
_____________
Insane Coding
_____________
Insane Coding
-
- Dark Wind
- Posts: 1271
- Joined: Thu Jul 29, 2004 8:58 pm
- Location: Texas
- Contact:
Don't forget that the scope of Qt is far more than GTK - Qt is equivalent to GTK + Cairo + STLPort + libxml2, at least.Kagerato wrote:Qt does take longer to compile than GTK2 with the GNU compiler collection, but there's a more significant reason for that. Qt is primarily C++, and GTK is primarily C. Comparing their compilation times (which differ by about fifteen minutes on my newest machine) is an invalid comparison -- the compiler is not the same. There have been assertions that GCC 4 has a much improved g++ compiler (as far as speed goes), but there is little experimental data for that as well.
[u][url=http://bash.org/?577451]#577451[/url][/u]