Hard Light Productions Forums
Modding, Mission Design, and Coding => FS2 Open Coding - The Source Code Project (SCP) => Topic started by: captain-custard on May 31, 2009, 06:08:12 am
-
In IRC the other evening i was talking with a few other ppl and after a day of helping ppl sort out setting issues for linux , Mac , windows , single and multiplayer.... i realised that this would be so much easier if we had a truly cross platform launcher ..; and as this seems like we will need a new launcher soon anyway , i was wondering how hard it would be to make a launcher that would run on all 3 platforms without too many hassles , just drop it in the folder and choose your options .....;
so as most ppl know i am completely useless when it comes to any thing more complicated than flying in circles and eating cake , im looking for honest opinions and ideas...
so , lets throw this one out there and hope that it intersts some ppl
-
I've been chatting with Goober recently about this exact topic.
Looks like it'll be in the pipeline and starting work on after 3.6.10 is released.
(hope you're OK with me mentioning this, Goob)
-
Sure. I hadn't planned on mentioning it until it was released, but there's no reason to keep it secret.
The plan is to release Launcher 6.0 for 3.6.10 (basically a hardened/rewritten/bugfixed version of 5.5d) and then convert it to wxWidgets for 3.6.11. This kills two birds with one stone: it provides a single SCP-supported launcher for all three platforms, and it gives us wxWidgets practice and experience for wxFRED.
-
thanks guys , this will really make a big difference when helping ppl set things up ....
is there any chance that there wll be a couple of new features in the launcher ?
-
We should move the standalone GUI over to wxWidgets at about the same time. It's a much smaller task than FRED. In fact it's probably smaller than the launcher.
-
I hadn't even thought about that; that's a great idea. That could even be something that portej could work on now, so he doesn't have to wait for me to finish Launcher 6.0. :)
-
Yep. Just start in network/stand_gui and stand_gui.unix and with the resource options for the Freespace2 project.
-
With a move to wx, will that make compiling on Windows a bigger pain than it already is? I'm guessing we wouldn't be able to add the wx libs to the SVN like we do with other stuff since they're probably a lot bigger?
-
With a move to wx, will that make compiling on Windows a bigger pain than it already is?
Probably - it needs to be compiled before you can use it, but we'll only be using one or two configurations, not the gazillion in the workspace.
I'm guessing we wouldn't be able to add the wx libs to the SVN like we do with other stuff since they're probably a lot bigger?
No. wx is about 18mb, and a hell of a lot larger once unzipped and compiled.
We shouldn't really be keeping the other stuff in SVN - it makes upgrading to the next version slightly harder, and there's always the chance that someone will edit headers they're not supposed to, and then when they're replaced with the next version things break.
-
Would it be too hard to make the launcher also be able to run FRED for the currently selected mod?
-
That might be a feature in the launcher 6.0 that's being talked about, although I'm pretty sure if you just run FRED right now it uses the launcher's settings. You just can't run it straight from the launcher.
-
I thought that was only a feature of some of the branches and not implemented in trunk.
-
Fred does currently read the launcher to some extent.
This can be ignored or over-ridden by the command line options set by shortcut. However, sometimes it will attempt to do both.
I had not remembered this until just now, so I am a bit fuzzy on the details.
-
Are you going to get rid of registry hack at some point and move over to INI stuff?
-
The idea is to get rid of as much registry stuff from everything over the next little while
-
We've also discussed making sure this is done in a backwards compatible manner, such that when the FSO builds start reading from another source besides HKLM, they report that to the launcher, so the launcher can be changed and still maintain compatibility with old builds, and even retail FS2 executables like it does now. That's one reason I decided against switching to HKCU right now to solve some problems, it would just create more.
-
It would make sense - right now you write values into virtual registry on Vista/Win 7 systems I believe.
-
Anybody got a list of EXACTLY what is written into the registry by each application?
I tried breaking the registry stuff (deliberately...) in a build, and didn't notice much go wrong.
Backwards compatibility is going to make a ***** of maintenance of this if we go down that path.
-
Everything on the graphics, network, and Sound/Joystick tabs I believe, is in the registry. That's resolutions, what joystick, what type of internet connection, what port, I think even your PXO information that's set in game is in the registry (and there was talk about letting you configure that in the launcher as well, not sure what happened with that). Maybe one or two of the options on those tabs is in a config file, but I'm pretty sure most of that is registry-bound. Easiest way to tell is when the screen resolution changes don't seem to have any effect.
-
Language gets written there as well I believe.
-
Don't forget that FRED writes all its preferences to the registry too. Not that it matters much until we move from Windows but we might as well go completely registry free now.
-
Even some of the in game stuff like the default for single/multi at start up go to the registry. That's the one that always kills me when switching between TBP an FS2.
-
Yep. We really need to add a PXO on/off button to the launcher actually as it's ****ing annoying having to launch FS2 just so I can turn off the registry setting for PXO in order to test the standalone without using PXO.