Nice, I've been thinking about a java-based multiplayer fronted, now I don't have to redo the frontend part 😀

Downloading now...

Good thing I've never bothered to setup profiles for my games otherwise I'd have alot of work to do.

/Nelson Ha Ha! Avatar_58

Yeah for Java!!! I havan't bothered with the other frontends because they were platform specific. And required strange compilers like Delphi Pascal.

I want to learn Java, so this will be an excellent opportunity to learn by building on something that already works. Any plans on setting up a CVS-repository for this?

MiniMax wrote:

... Any plans on setting up a CVS-repository for this?

Hehe, well, I have CVSNT running at home, specifically for this project. But I guess you mean setting up something like a SourceForge project for this?! I think that may be a good idea if there is interest from the community. If you know how to set up a SourceForge project, please, be my guest.

In case anyone needs help compiling the source, just let me know. I've been developing in Eclipse 3.2, BTW.

Ronald

..Attaching a couple more screenshots..
EDIT: removed them, they're on the site.

Good, zip file support is probably the first thing for frontend.

Is it possible to let your frontend know about dosbox version automatically?
For instance, "dosbox.exe -version" will write an output about version number to stdout.txt.
Then, the frontend will load stdout.txt to know which version of dosbox.exe is being used.
Furthermore, for accurancy, it can also see the creation date of dosbox.exe so that it guesses whether the dosbox.exe is official or cvs one.

ykhwong wrote:

Is it possible to let your frontend know about dosbox version automatically?

Hi ykhwong,

Surely this can be done, but for what purpose exactly?

Ronald

It's for convenience for any dosbox user.
Your frontend already has preconfigured profile included, so I hoped it automatically decides to use one of the profiles by analyzing the stdout.txt
DOSBox developer created such a parameter (readme says that it can be useful for frontends), but there are no frontends that have used the feature as far as I know.

Hi,

Are there many more commands showing information in the stdout.txt?
I tried the -version command and it shows 0.65. What do CVS builds return?

Erik.

0.65 😀

we might want to change that indeed 😀

DosFreak wrote:

Downloading now...

Good thing I've never bothered to setup profiles for my games otherwise I'd have alot of work to do.

/Nelson Ha Ha! Avatar_58

You missed:

rcblanke wrote:

* D-Fend profiles importing

😉 Instant sale for me. You've taken all the work away and are attempting to best D-fend at the same time. Kudos. I'll definately be watching this one closely. That multiple version feature also is music to my ears.

And this is for Dosfreak 😉

Very cool.

@ykhwong & Qbix: Maybe when we get so far that dosbox can exactly report on its features, such as physfs support, scalers that are supported and so on, we can use that in a front-end such as mine. For the moment, I don't really see the usefulness of retrieving only it's version number, unless I'm missing something..

@avatar_58 & DosFreak: Thank you. I realized D-Fend profile importing was an important feature for many people because of the popularity of that front-end...Not to mention the nightmarish idea of having to copy hundreds of profiles by hand, myself 🙄

BTW, DBGL currently does some cleanup when importing D-Fend profiles. During import, all bogus settings ([gus]base, [gus]rate, [sblaster]base and [sblaster]type) are removed. Midi settings are redefined as to match the changed configuration specifications for the midi section, and a couple of sections are stripped entirely. Those sections are: [directserial], [modem], [ipx] and [sdl]. I choose to do this because I think either:

* these settings should be choosen in the main dosbox.conf file (so to be able to change these kind of settings for all underlying games)
* they clutter up the profile's configuration file too much

I can imagine that this decision is not what is to be expected when doing a direct import, so, if anybody wants that, I can make this 'section-stripping' optional.

Regards,
Ronald

DosFreak wrote:

Downloading now...

Good thing I've never bothered to setup profiles for my games otherwise I'd have alot of work to do.

/Nelson Ha Ha! Avatar_58

You mean you just use/have .conf files for each and every game, right?!
Would it be handy to have importing functionality for this situation as well? So that you can point to an existing configuration file, and just have that inserted in the profiles list in DBGL, instantly?!

Or maybe even better, you copy all your conf files to one dir and have that be inserted all at once. Of course, this will only work if you have given all your configuration files a unique name (probably the game's title)...

I was thinking about two optional ways.
This is just my opinion. (I am sorry if I bother Dosbox developers and/or rcblanke for this.)

1) The first thing is....
Adding ALL the lines connected to dosbox configs/features that have been changed since official version released is possible like this.

gui/sdlmain.cpp

1printf(VERSION "\n\n");
2printf("Since dosbox 0.65 official (for frontends)\n");
3printf("Configuration :\n");
4printf("[sdl] : output=++direct3d,++openglhq\n");
5printf("[sdl] : ++overscan=++0,++number\n");
6printf("[render] : scaler=++hq2x,++hq3x,++2xsai,++super2xsai,++supereagle,++advinterp2x,++advinterp3x,++tv2x,++tv3x,++rgb2x,++scan2x,++scan3x\n");
7printf("++[vsync] : ++vsyncmode=++off,++on,++force\n");
8printf("++[vsync] : ++vsyncrate=++75.023426,++number\n");
9printf("Features :\n");
10printf("++zip mount, ++multiple config\n");

Frontend will see & add only the words after ++. (That would be a little bit hard?)

2) Another thing is...

There will be only the following lines:

gui/sdlmain.cpp

1printf(VERSION "\n\n");
2printf("Features :\n");
3printf("zip mount, multiple config\n");

Frontend will load texts "version number 0.6x", "zip mount", and "multiple config" with the help of '-version'.

Afterwards, frontend will run dosbox.exe with parameters below.
-c "config -writeconf frontend.conf" -c "exit"

Then it will load & analyze newly created frontend.conf for configuration of profiles.

I wonder if the effort of providing support for things not in the CVS is worth it?

Those using the CVS probably don't bother to use frontends anyway (well mostly).

Rcblanke - No, thank YOU 😉 You actually listened to what people wanted and implemented it. Very nice. What I also like is how editing profiles no longer blinks my whole screen or returns to the top like it does in D-fend.

A nice feature would be if the program memorized how I resized the window upon closing. In other words if my list was small I can leave it a little squished, if I have a giant list (which I do) I want it maximized at all times. Just a thought.

A feature I love with d-fend is making external shortcuts. You can quickly have an icon on the desktop which launches dosbox with specific settings, which is great when I make shortcuts for people who do not even know dosbox is running at all. I don't use it too often, but whenever I set it up for others I try to make dosbox as transparent as possible and this is THE easiest way (batch files and seperate configs work just as well, but this way is as painless for me as possible)

A couple of thoughts, it might be nice to have the option to save the conf file in either a single directory or in the game's directory. The ability to launch a game in DOSBox from the GUI for test purposes to make decisions on settings would be handy.

Although this would not be part of this frontend, it would be nice to be able to invoke the frontend from the simple GUI of the menu bar like ykhwong includes in his builds.

But, what would make it a clear winner for me would be the ability to access it from a right click on a DOS executable, à la VDMS Launchpad and for it be able to generate a DOSBox shortcut to the game.