Currently SD or SDX can be used by using a different binary name. This was the easiest way to allow for certain workflows, such as "I only care about DragonX, I want to click an icon and a DragonX GUI wallet to start" OR "I only care about Hush, I want to start just the Hush GUI wallet". Some people might have both a Hush + DragonX full node running on the same machine, so looking at which full node is running would not work when both are running.
A dedicated binary also means you can run SD + SDX at the same time.
Making users download/install both SD + SDX binaries is somewhat wasteful of bandwidth and disk space for certain users. If a user wants to run both SD and SDX (but not at the same time) we could offer an option to change between them at run-time.
It could be that nobody would use this feature and it's not worth the time to do it. Would any Hush devs use this feature or do you prefer to have dedicated binaries with the ability to run SD+SDX at the same time?
Currently SD or SDX can be used by using a different binary name. This was the easiest way to allow for certain workflows, such as "I only care about DragonX, I want to click an icon and a DragonX GUI wallet to start" OR "I only care about Hush, I want to start just the Hush GUI wallet". Some people might have both a Hush + DragonX full node running on the same machine, so looking at which full node is running would not work when both are running.
A dedicated binary also means you can run SD + SDX at the same time.
Making users download/install both SD + SDX binaries is somewhat wasteful of bandwidth and disk space for certain users. If a user wants to run both SD and SDX (but not at the same time) we could offer an option to change between them at run-time.
It could be that nobody would use this feature and it's not worth the time to do it. Would any Hush devs use this feature or do you prefer to have dedicated binaries with the ability to run SD+SDX at the same time?
I don't mind the dedicated binaries and think they may be better for marketing and distinguishing which coin you're using. I'd still find it useful.
Trying to envision how it would work from the GUI with stopping/starting node and detecting which is running. Will SD always default to HUSH and SDX always default to DRGX when opening? Would there be a more advanced check to save and then display the GUI for the last changed coin?
Occasionally the node doesn't always stop when closing GUI so that's something to think about. You wouldn't want to open SDX expecting to see DRGX but then see HUSH because the HUSH node is still running. At the same time, if you last changed to HUSH in SDX, you might not want to see DRGX when re-opening.
I don't mind the dedicated binaries and think they may be better for marketing and distinguishing which coin you're using. I'd still find it useful.
Trying to envision how it would work from the GUI with stopping/starting node and detecting which is running. Will SD always default to HUSH and SDX always default to DRGX when opening? Would there be a more advanced check to save and then display the GUI for the last changed coin?
Occasionally the node doesn't always stop when closing GUI so that's something to think about. You wouldn't want to open SDX expecting to see DRGX but then see HUSH because the HUSH node is still running. At the same time, if you last changed to HUSH in SDX, you might not want to see DRGX when re-opening.
@fekt you bring up some good points. There are a lot of edge cases to deal with if this feature existed, and we could come up with some solution to them, but they likely would not be intuitive for many users. I don't think this feature is worth implementing. We have plenty of other stuff that is much more important to work on.
@fekt you bring up some good points. There are a lot of edge cases to deal with if this feature existed, and we could come up with some solution to them, but they likely would not be intuitive for many users. I don't think this feature is worth implementing. We have plenty of other stuff that is much more important to work on.
Currently SD or SDX can be used by using a different binary name. This was the easiest way to allow for certain workflows, such as "I only care about DragonX, I want to click an icon and a DragonX GUI wallet to start" OR "I only care about Hush, I want to start just the Hush GUI wallet". Some people might have both a Hush + DragonX full node running on the same machine, so looking at which full node is running would not work when both are running.
A dedicated binary also means you can run SD + SDX at the same time.
Making users download/install both SD + SDX binaries is somewhat wasteful of bandwidth and disk space for certain users. If a user wants to run both SD and SDX (but not at the same time) we could offer an option to change between them at run-time.
It could be that nobody would use this feature and it's not worth the time to do it. Would any Hush devs use this feature or do you prefer to have dedicated binaries with the ability to run SD+SDX at the same time?
I don't mind the dedicated binaries and think they may be better for marketing and distinguishing which coin you're using. I'd still find it useful.
Trying to envision how it would work from the GUI with stopping/starting node and detecting which is running. Will SD always default to HUSH and SDX always default to DRGX when opening? Would there be a more advanced check to save and then display the GUI for the last changed coin?
Occasionally the node doesn't always stop when closing GUI so that's something to think about. You wouldn't want to open SDX expecting to see DRGX but then see HUSH because the HUSH node is still running. At the same time, if you last changed to HUSH in SDX, you might not want to see DRGX when re-opening.
@fekt you bring up some good points. There are a lot of edge cases to deal with if this feature existed, and we could come up with some solution to them, but they likely would not be intuitive for many users. I don't think this feature is worth implementing. We have plenty of other stuff that is much more important to work on.