It seems like beta and drity builds should have portable.txt included by default, at least myself I always keep adding one.
If not betas, or unstable, or how do you call them, then at least dirty builds, so it should be the other way around, so that the main user profile configs would only be messed with when the user consciously is aware of the risks and deletes the portable.txt file.
Absolutely not. The whole point of the global user directory is to make dev builds and upgrading more convenient. If we included portable.txt in them, we'd literally be countering the whole point of the global user directory existing in the first place. Also most of us here use dev builds as our primary means of using dolphin, so portable.txt would be annoying!
Also we don't ship dirty builds.
Okay, so if a beta build messes up the configuration that an installed stable version is using, causing an issue or even data loss in the stable version, who's going to be responsible?
This is actually an end user question, not development I guess, indeed there is no need for portable on the PC that is being used for mosly development and not enjoyment where the integrity of the configs and saves matters.
Change of question then: Should the "betas" have that.
In the GUI there's:
Stable
Beta
Development
But I've never seen Beta, so I just called the daily development ones "beta", probably not correct.
And then there's the Development Dirty.
Development daily ones are on the mains site, I just clicked a big button, so those are shipped, those are the ones I mean should have portable.txt.
So it's confusing, they're development and shipped.
They're not dirty, they're perfectly usable builds that pretty much never mess up your configuration.
(04-23-2018, 07:17 AM)JosJuice Wrote: [ -> ]They're not dirty, they're perfectly usable builds that pretty much never mess up your configuration.
I agree, that's why I was leaning toward calling them beta rather than development.
What about letting people know there is a portable mode that exists at all. There is no readme file, or any note when it's launched.
No thanks, I prefer my development builds without the portable.txt file. The whole point with the development builds is to stay up to date on the latest additions and improvements while keeping my settings. I just like to write over the new build over the old build, which is even made easier thanks to the auto-updater and the now-default QT2 interface.
A portable mode is mostly useful when you need to test a separate instance of Dolphin within an isolated environment, at least for me. You can change the location of the global user directory if that is what bothers you.
(04-23-2018, 08:00 AM)Admentus Wrote: [ -> ]No thanks, I prefer my development builds without the portable.txt file. The whole point with the development builds is to stay up to date on the latest additions and improvements while keeping my settings. I just like to write over the new build over the old build, which is even made easier thanks to the auto-updater and the now-default QT2 interface.
A portable mode is mostly useful when you need to test a separate instance of Dolphin within an isolated environment, at least for me. You can change the location of the global user directory if that is what bothers you.
Yeah I may have worded this and posted to the wrong forum. That's your development viewpoint, I take back, I'm not looking at this from development viewpoint anymore.
I would never want the various development builds to overwrite my main config data which a stable installed version would use.
Some of the developers must not be playing on the same computer, or not playing at all then.
The only reason I can see to even use the stable builds anymore is to check for a regression, since the dev builds are faster, have more features, and more stable most of the time (unless a regression gets introduced, in which case it's usually fixed pretty quickly)
(04-23-2018, 08:19 AM)Renazor Wrote: [ -> ]I would never want the various development builds to overwrite my main config data which a stable installed version would use.
Then why not add a portable.txt file to the stable install instead?
Anyway I wanted to add "Portable Mode" label to the main window title, but due to the versioning system, I can't figure it out so easily because the builders work from different source it seems than the local builds.
So who responsible for that could do this. So then it would say
Dolphin 5.0-xxxx Portable Mode
(04-23-2018, 08:36 AM)JosJuice Wrote: [ -> ]Then why not add a portable.txt file to the stable install instead?
Your thinking is the other way around, the local repo visual studio built ones should be portable ... for those who play and develop on the same PC/OS.