I am about to start coding the "Select your miner software / algorithm" but first i wanted to ask:
What will you prefer:
1) Having one copy of miner soft (cgminer/sgminer/cgminer_keccak) in a separate path each with a separate config file, and choose which one to use from phpminer. This means adding one set of options to phpminer config file per algo/soft.
2) Make it so you setup the command to run each algorithm so you set the soft and algo yourself for each like:
"/path/to/scrypt_cgminer/cgminer -a scrypt"
"/path/to/sha_cgminer/cgminer -a sha256d"
"/path/to/cgminer_keccak/cgminer -a keccak"
3) any other better way
What will you prefer:
1) Having one copy of miner soft (cgminer/sgminer/cgminer_keccak) in a separate path each with a separate config file, and choose which one to use from phpminer. This means adding one set of options to phpminer config file per algo/soft.
2) Make it so you setup the command to run each algorithm so you set the soft and algo yourself for each like:
"/path/to/scrypt_cgminer/cgminer -a scrypt"
"/path/to/sha_cgminer/cgminer -a sha256d"
"/path/to/cgminer_keccak/cgminer -a keccak"
3) any other better way
Ok, I think we need to work together with this feature, because today and i think i will need tomorrow too, I will change that phpminer only needs to connect to the rpc client and the rpc client will do all the api commands. With this change, i will enhance the code for the rpc client to a class structure, to have a better overview against the current one.
Since you need to call the rpc client to kill/restart miner to ensure new algo is used you should wait this evening, i will push the new class structure (without the additinal api commands if I am not fast enough). So you will have the correct rpc structure to work with.
I think the config should be that each miner has it's own sub folder, but only the miner itself, not the algo too. Then you have to configurate within the rpc client config file the available miners and what algo's they can handle.
An rpc command should return the possible miners + their algo's.
Currently within phpminer you have a tabbed view of all rig's to configurate cgminer, there an inner tabbed view should be created with all available miners.
Then there are 2 possibilities.
First one is, if a different algo does not require a new option or can not have an option which is available on a different algo, then the cgminer config is finished here. The normal config options should directly appear.
Second one is, when the options can differ from algo to algo, then there should be another inner tab view with one tab which is called "global" and then as many algo's available a seperate tab.
The global one is the base, the algo tab will override the global option.
On save I would think within the rpc client config file, you have to provide, as it is now, the path to miner config file.
The option for config file it self (cgminer_config_path) can be removed, instead rpc client will create for each algo a seperate config file within this directoy. For example "config_scrypt.conf", "config_sha.conf" and so on.
What you think?
Hope my english is not too bad
