i love mupen64

[Braindead]

Hi Hacktarux, mupen64 is great (for real).
If you are working on a 0.5 version you may keep following in mind:
For a system wide install its nessersary that mupen64 and and its plugins search their config files from certain places and not only from the executable path or current/working directory. (ie first try $(HOME)/.mupen64/ then /usr/share/mupen64 then . for read/write mupen/plugin config files)
Write a no gui version of mupen64. Do not waste your time and talent on a sophisticated gui. That hold also for plugins. Why needs a sound plugin needs a gui configurator? it shoud be seperated.
I think there are many talented, experienced and willing gtk/gtk2/qt/swing/winmx etc coders on this forum, they can do it better and you avoid the gui toolkit flamewar and save your time for core improvement, and i think thats your strenght. I see a future with many coders working on guis with mp3/png or avi previews and ... wait stop ... i think i'm dreaming ...
Anyway, more then a template gui for other gui programers is not nessersary, or using an frontend like 'advance menu'.
btw playing with the joystick does not deactivate the X11 screensaver. My workaroud is to run xset -dpms s off before, but maybe you know a better solution.

 

[blight]

Hi Hacktarux, mupen64 is great (for real).
If you are working on a 0.5 version you may keep following in mind:
For a system wide install its nessersary that mupen64 and and its plugins search their config files from certain places and not only from the executable path or current/working directory. (ie first try $(HOME)/.mupen64/ then /usr/share/mupen64 then . for read/write mupen/plugin config files)
Write a no gui version of mupen64. Do not waste your time and talent on a sophisticated gui. That hold also for plugins. Why needs a sound plugin needs a gui configurator? it shoud be seperated.
I think there are many talented, experienced and willing gtk/gtk2/qt/swing/winmx etc coders on this forum, they can do it better and you avoid the gui toolkit flamewar and save your time for core improvement, and i think thats your strenght. I see a future with many coders working on guis with mp3/png or avi previews and ... wait stop ... i think i'm dreaming ...
Anyway, more then a template gui for other gui programers is not nessersary, or using an frontend like 'advance menu'.
btw playing with the joystick does not deactivate the X11 screensaver. My workaroud is to run xset -dpms s off before, but maybe you know a better solution.

Just FYI: The current GUI of mupen was written by me, and it supports capturing of AVI movies.

 

[matthew]

I don't agree any gui is better than no gui at all even if its in Java
Linux is a graphical desktop system and so the applications should have a gui just like MACOS or Windows back in the days when every linux user was a programmer it made sense to leave it everything Command line but these days GUI's are a must if Linux is to achieve more market share

 

[ciruZ]

Linux is a graphical desktop system

Wrong. Linux is still a unix system. And unices aren't graphical. Well, it's actually not a unix, but it's a unixish system. But Mupen also runs on *BSD - and that are real Unices .
Noone needs more then a terminal, screen, a XServer and evilwm as Window Manager, that should be enough for everyone. On Windows, it's different. There everything really needs a nice GUI.

I would support the idea to have a command line version of Mupen64.
Eg. ./mupen64 ../roms/Mario_Kart_64.v64.gz
That would be much more user friendly since you don't need to click around in the GUI.

Even for KDE Users (Sigh! Who needs KDE?) this could be an improvement: They could just add the mupen64 binary for *.v64 and *.z64! And then with one click launch the game.

So this could make terminal-lovers like me and KDE users happy.

But that doesn't meen that the GUI needs to be removed, oh no! I just thought about having a way to compile it without the GUI and a way to compile it with GTK+ or Win32 GUI. That would be nice as an option for the ./configure Script, for example --disable-gui, --enable-gui=gtk, --enable-gui=win32 and so on.

 

[blight]

What do you guys think the first version of mupen64 had? It was a command line interface. So there already is one - the questions is wether it is still usable (with all the changes in the core)

 

[ciruZ]

Well, then it would be a good idea to bring that CLI back to live.
But are there still parts of the CLI left in the current sourcecode? I have the bad feeling that it was removed and has to be done from scratch .

 

[matthew]

Wrong. Linux is still a unix system. And unices aren't graphical. Well, it's actually not a unix, but it's a unixish system. But Mupen also runs on *BSD - and that are real Unices .
Noone needs more then a terminal, screen, a XServer and evilwm as Window Manager, that should be enough for everyone. On Windows, it's different. There everything really needs a nice GUI.

I would support the idea to have a command line version of Mupen64.
Eg. ./mupen64 ../roms/Mario_Kart_64.v64.gz
That would be much more user friendly since you don't need to click around in the GUI.

Even for KDE Users (Sigh! Who needs KDE?) this could be an improvement: They could just add the mupen64 binary for *.v64 and *.z64! And then with one click launch the game.

So this could make terminal-lovers like me and KDE users happy.

But that doesn't meen that the GUI needs to be removed, oh no! I just thought about having a way to compile it without the GUI and a way to compile it with GTK+ or Win32 GUI. That would be nice as an option for the ./configure Script, for example --disable-gui, --enable-gui=gtk, --enable-gui=win32 and so on.

yeh i see since visualboy advance already has this option

I would support the idea to have a command line version of Mupen64.
Eg. ./mupen64 ../roms/Mario_Kart_64.v64.gz
That would be much more user friendly since you don't need to click around in the GUI.

Why is clicking around in a gui a chore ?
I don't actually believe that many people use Linux these days without an Xserver and Desktop environment hence Linux = graphical or at least these days it is

example would be the mencoder commands to rip a file to avi
or maybe the multiple options of the commandline cd writing tools

my worst quibble with commandline would be that i'd have to open up the folder of where the roms were held and then do the command for mupen and the file

But in the gui i could simply click on the Mupen Icon on the Menubar where the rest of my emulators are held and then find a gui where i could just choose roms as if they were on a playlist

I really don't see how command line beats Gui for ease of use for end users

 

[Hacktarux]

try typing "make mupen64_nogui" in the mupen64 source code. It still exists and it works.

 

[ciruZ]

@matthew: The way VisualBoyAdvance does it - that was exactly the way I was thinking about .
Ah, ok, thx hacktarux. Is it possible to config the plugins et cetera there, too?