Feature request: revamping config files
Re: Feature request: revamping config files
IMO I also don't think a configurator program would be useful. That's overblowing featurecreep and going against KISS principles that make PCem already elegant as it is.
Virtualizers that have them need them because they're designed for enterprise users in mind, which is more for a 'everything must be obfuscated strictly to a GUI' kind of sense especially when considering professional corporate technical support. PCem doesn't have to follow this.
Virtualizers that have them need them because they're designed for enterprise users in mind, which is more for a 'everything must be obfuscated strictly to a GUI' kind of sense especially when considering professional corporate technical support. PCem doesn't have to follow this.
- SarahWalker
- Site Admin
- Posts: 2054
- Joined: Thu 24 Apr, 2014 4:18 pm
Re: Feature request: revamping config files
While this conversation is very interesting... has anyone actually tried what I uploaded to that branch?
Re: Feature request: revamping config files
I cannot compile it, but would love the try the binary. Thanks.
Re: Feature request: revamping config files
Well, right now the configurator in PCem's settings is a bad mess.leilei wrote:IMO I also don't think a configurator program would be useful. That's overblowing featurecreep and going against KISS principles that make PCem already elegant as it is.
Virtualizers that have them need them because they're designed for enterprise users in mind, which is more for a 'everything must be obfuscated strictly to a GUI' kind of sense especially when considering professional corporate technical support. PCem doesn't have to follow this.
Re: Feature request: revamping config files
From what I understood, people have requested some sort of a configuration manager, which seems to be what Sarah is trying to implement, however rather than do it properly, ie. the way all other produces do it, it seems to be getting done in a way that will IMHO limit its usability. Sure, there's going to be a configuration selection dialog at start, but that's about it. Adding a power off ability and making it display the configuration selection dialog when you power it off would be a step forward, it still retains the drawback of making writing any kind of third party manager impossible.leilei wrote:IMO I also don't think a configurator program would be useful. That's overblowing featurecreep and going against KISS principles that make PCem already elegant as it is.
Virtualizers that have them need them because they're designed for enterprise users in mind, which is more for a 'everything must be obfuscated strictly to a GUI' kind of sense especially when considering professional corporate technical support. PCem doesn't have to follow this.
I'd look at Bochs as an example - from what I remember, it has a configuration manager of its own, which I'm quite sure is separate from the emulation core executable, but it also provides a way for the core to be launched on its own.
Another example is Qemu which doesn't provide a manager of its own at all and instead leaves that aspect to third parties.
- SA1988: While I agree the current configuration dialog leaves a lot to be desired, blurting it out like that won't achieve anything.
- SarahWalker
- Site Admin
- Posts: 2054
- Joined: Thu 24 Apr, 2014 4:18 pm
Re: Feature request: revamping config files
Yes, because Bochs and Qemu are totally known for being user friendly...
I'd view the need for any third party managers as a bug rather than a feature. In any case said managers would likely still be possible, as I could add command line options to allow that. I haven't yet, as this isn't finished. It's a work in progress. Hence why it's not on trunk. Clear enough?
I'd view the need for any third party managers as a bug rather than a feature. In any case said managers would likely still be possible, as I could add command line options to allow that. I haven't yet, as this isn't finished. It's a work in progress. Hence why it's not on trunk. Clear enough?
- SarahWalker
- Site Admin
- Posts: 2054
- Joined: Thu 24 Apr, 2014 4:18 pm
Re: Feature request: revamping config files
Well, what's your solution? Any suggestions? Or are you going to continue to just snipe from the sidelines?SA1988 wrote:Well, right now the configurator in PCem's settings is a bad mess.leilei wrote:IMO I also don't think a configurator program would be useful. That's overblowing featurecreep and going against KISS principles that make PCem already elegant as it is.
Virtualizers that have them need them because they're designed for enterprise users in mind, which is more for a 'everything must be obfuscated strictly to a GUI' kind of sense especially when considering professional corporate technical support. PCem doesn't have to follow this.
If so, can you think of any good reason why I should continue to allow you to post here?
Re: Feature request: revamping config files
fwiw i find pcem's interface fine as it is as it's similar to another Neko Project II's straight-forward simplicity. The only real difference between that and PCem is that Neko uses smaller dialogs with tabs breaking it up, and less drive image parameter configuration. Neko also doesn't need a launcher.
Re: Feature request: revamping config files
It's precisely that - smaller dialogs with tabs, and a more orderly design in general. I think PCem would greatly benefit from such a design.leilei wrote:fwiw i find pcem's interface fine as it is as it's similar to another Neko Project II's straight-forward simplicity. The only real difference between that and PCem is that Neko uses smaller dialogs with tabs breaking it up, and less drive image parameter configuration. Neko also doesn't need a launcher.
Re: Feature request: revamping config files
"Yes, because Bochs and Qemu are totally known for being user friendly..."
Sarah, you are more than right, on the spot. Some say that PCem is "fairly" difficult to configure, hm? i use to play with Bochs and Qemu and... uff, its easy once you learn, but PCem is by far EASY-est to configure, guys stop complaining, everything is "point and click" no difficulties whatsoever.
The only thing to add is , as someone mention , the power button, so PCem will not start while i try to set it up, after that PCem config is brilliant, or Diamond he he.
Sarah, you are more than right, on the spot. Some say that PCem is "fairly" difficult to configure, hm? i use to play with Bochs and Qemu and... uff, its easy once you learn, but PCem is by far EASY-est to configure, guys stop complaining, everything is "point and click" no difficulties whatsoever.
The only thing to add is , as someone mention , the power button, so PCem will not start while i try to set it up, after that PCem config is brilliant, or Diamond he he.
- SarahWalker
- Site Admin
- Posts: 2054
- Joined: Thu 24 Apr, 2014 4:18 pm
Re: Feature request: revamping config files
Okay, as of rev 714 the new_config branch now starts the configuration manager first thing, allowing for reconfiguration before starting emulation. Closing the main PCem window will re-open the configuration manager, effectively acting as a power button. And using the --config command line option will bypass the configuration manager entirely and allow you to implement an external configuration manager if that's what you really want.
Everyone happy?
Everyone happy?
-
- Posts: 183
- Joined: Wed 18 Mar, 2015 5:27 am
Re: Feature request: revamping config files
This is great, thanks Sarah!
Re: Feature request: revamping config files
- SarahWalker: I certainly am. :p
Re: Feature request: revamping config files
Quickly trying the configurator branch out of curiosity, it doesn't list the cfgs in the same folder as itself, and crashes upon quitting. It CAN make configs though
Re: Feature request: revamping config files
So, it's similar to what you'll see when you start up WinUAE?Battler wrote:It's precisely that - smaller dialogs with tabs, and a more orderly design in general. I think PCem would greatly benefit from such a design.
In any case, I am all for it. I get annoyed that I sometimes saved a custom config file without ejecting a disk first, so that would help me a lot. So great work. Sarah.
- SarahWalker
- Site Admin
- Posts: 2054
- Joined: Thu 24 Apr, 2014 4:18 pm
Re: Feature request: revamping config files
On trunk as of rev 724.
Re: Feature request: revamping config files
I just tested the latest build, it just doesn't work, it crashes when trying to load a config...
Honestly, I don't like the new dialog screen...
Just wondering... why is not like before: you open PCem, configure it the way you like, let's say a SiS 486/66 and save it to a file called "sis486.cfg" and after saving you modify PCem again and to a 430VX, then quit PCem and the last config is automatically saved to default.cfg
If you start PCem right away you'll automatically start the last config which was the 430vx, but let's say you want to run SiS 486... what you can do is: have the .cfg extension (or *.pcm extension if you like) associated to PCem, so you double click the "sis486.cfg" file or any other extension and PCem loads automatically with said configuration.
What do you all think of this?
Honestly, I don't like the new dialog screen...
Just wondering... why is not like before: you open PCem, configure it the way you like, let's say a SiS 486/66 and save it to a file called "sis486.cfg" and after saving you modify PCem again and to a 430VX, then quit PCem and the last config is automatically saved to default.cfg
If you start PCem right away you'll automatically start the last config which was the 430vx, but let's say you want to run SiS 486... what you can do is: have the .cfg extension (or *.pcm extension if you like) associated to PCem, so you double click the "sis486.cfg" file or any other extension and PCem loads automatically with said configuration.
What do you all think of this?
- SarahWalker
- Site Admin
- Posts: 2054
- Joined: Thu 24 Apr, 2014 4:18 pm
Re: Feature request: revamping config files
Well clearly people didn't like it, as I got numerous requests to change it!
And couldn't you have said this _before_ I spent time polishing it and getting it to trunk? I did make it available in a branch specifically to get feedback on it...
And couldn't you have said this _before_ I spent time polishing it and getting it to trunk? I did make it available in a branch specifically to get feedback on it...
Re: Feature request: revamping config files
I placed PCem in 'O:\EMUL\Emulator - Computer\IBM-PC\PCem'.
Is this loading cfg files to list automatically?
so I launched with --config arguments, but PCem execute --config pcem.cfg to loads default(8088) settings.
Last edited by basic2004 on Wed 17 May, 2017 5:15 pm, edited 1 time in total.
- SarahWalker
- Site Admin
- Posts: 2054
- Joined: Thu 24 Apr, 2014 4:18 pm
Re: Feature request: revamping config files
Presumably you don't have any configs in the 'configs' directory. Have you tried to create any?
Re: Feature request: revamping config files
Oh, I moved cfg files to configs folder now, and shows lists now.
This GUI is easy to choose from many machines, so this feature is very nice.
but I want make 'configs' folder if configs folder missing when PCem execute.
and make 'nvr' folder if nvr folder missing too.
PCem needs search and make essential folders.
This GUI is easy to choose from many machines, so this feature is very nice.
but I want make 'configs' folder if configs folder missing when PCem execute.
and make 'nvr' folder if nvr folder missing too.
PCem needs search and make essential folders.
- SarahWalker
- Site Admin
- Posts: 2054
- Joined: Thu 24 Apr, 2014 4:18 pm
Re: Feature request: revamping config files
The directories exist in the repo. If you use PCem from the directory that it's checked out into then it all works...
Re: Feature request: revamping config files
The emulator should still automatically create the directories it needs (nvr and config) in case they're not present.
Re: Feature request: revamping config files
I think I don't care.omarsis81 wrote:If you start PCem right away you'll automatically start the last config which was the 430vx, but let's say you want to run SiS 486... what you can do is: have the .cfg extension (or *.pcm extension if you like) associated to PCem, so you double click the "sis486.cfg" file or any other extension and PCem loads automatically with said configuration.
What do you all think of this?