Quote from: gnarl on November 26, 2014, 12:04:07 AM

Quote from: Griffith on November 25, 2014, 06:49:58 AM

still here. didnt really read the last ~10 posts. more skimmed them due to lack of time.

2 things that immediately came to mind.

why do you need an installer? the qt is a 1 click app. no need for an installation process imo. most coins dont have an installer. but if its reallyyyyy wanted i guess i could make one...

other thing was...

it is actually needed for the old dev to state he is leaving and name a successor, otherwise exchanges wont follow new code/github repos and wont update the wallets they run. in which case no matter what i edit the code to do that wont run it. so it would be useless. ive had this problem temporarily in the past (when mintpal was still a thing) and they told me they needed the old devs approval to change the repo they were following.

EDIT: btw, the reason the coin wont connect to the network if you havent run the wallet before is due to lack of coin conf file. and you need to create one manually. no need to do that anymore. i edited the code so that it automatically creates one in the right directory now for you. so that bug is eliminated.

dont know where to upload it as of right now though. i can create my own repo on my git. but before i do that i want to see if the dev is willing to hand off the coin to pass succession to my git. otherwise further developement is pointless if the exchanges wont follow me (described why earlier in the post)

but besides that, yeah we can take over for devving, if there is anything else that i need(that i can get), if someone could PM me or send me that would be great

So the answer to a Test Run of your development skills, is: Why?
"Why does it need an installer" is not really what I would expect from someone that is serious about delivering a marketable product.
We are all trying to determine if giving you control of the code is a good idea, this test build seems like a pretty simple way to do that.

I proposed the Fix the Wallet test run to determine:
If you can.
If you can support all the OS's required.
If you can resist 'on the fly' or unannounced changes.
If you will beta test thoroughly.
If you will release it securely.
How you work with the community and/or people involved.

This would also finally produce something that regular people can install, making it worth recommending and advertising...

You mentioned that you "already fixed it". Ok great, then the hard part is done!
Open source - Stated it would be posted in github.
Installs without manual user steps. - Fix ready
Includes updated supercoin.conf. - Fix ready

Steps To go:
Update logo (Red one, to match what websites were told to use)
Update version and changelog.
Nothing fancy, and no other changes to code.
Tested and reviewed before full release. (allows for community beta test and marketing prep)
Compiled builds released by you with sha256 hash.

What do you think of the steps listed? Are they all necessary? Are any missing?
How long do you think it would take to complete this test build for win\linux\mac?
How would you beta test this build? and for how long?
(Knowing these answers would allow the community to schedule marketing and media stuff.)

These would all be great things to know before the keys to everything get handed over. Thanks for any clarification you can provide.
Hope we can give you some super for your time and effort.

We can update all these minor things in 1 day. As I see it by now, there has never been a Mac wallet, nor a linux wallet from the SuperDev....
But we have it ready ( I am using the mac wallet ).

For updating the logo...where is the Logo, who has the original files?...All the changes you propose and the steps to go can be done in 1 day.

Now...we will keep the source from Supercoin open source, however if we are going to add in wallet trading, multiple coin support and other exclusive developments to Supercoin, then those developments WILL stay closed source.

No coin has benefits if ALL the source code is open source. Closed source will give value to a coin as it will be unique. So I think we will do the following, we will make 2 wallets for every operating system. 1 with special futures and 1 without them.

The open source wallets (without special futures) will be for the persons that have doubts in us (Griffith and Me), the source code from these wallets will be available on the Github for copy cats and scam developers, because a normal user (that needs an installer) can not read that code AND is not interested in that code.

The Supercoin wallets with exclusive developments (in wallet trading, multi-coin support, etc...) will only be available pre-compiled. The Source code from these wallets will be on a closed section from the Github.

If you want to know how the development of in wallet trading is going then you should have a look on the MWC forum https://bitcointalk.org/index.php?topic=752808.msg9544646#msg9544646 there you can see that the development is in the final stages and that the forum members are given the opertunity to choose which exchanges they want to be added.