i didnt say why to test my dev skills. i said why to an installer. the QT is 1 file and creates / reads from the directories that is needs already built in. which is normally the point of an installer. let me tell you what can be done almost immidiately (besides the changes i said i already made). all OS will be supported. (really simple and pretty much done). of course i can update the version 1 level. that will take maybe 30 seconds. as far as logo change goes. if someone can make a logo that the community like then it can be added immediately. im not good with Photoshop / graphics. sorry. there is usually whole separate divisions for that in a company from the other coders. how to beta test? umm... just run it? there isnt really any significant changes to be made to the actual networking portion of the code, so theres no real reason to test those immediate upgrades.
Ah, ok.
Yes, they are easy and basic steps. That is why I proposed it, nice and simple with a small scope of work to start things off. Sounds like you have it covered.
The logo can be provided or recreated, in whatever format/size you need. That's not a problem.
I see you don't have an installer on the MWC project either, let me explain my request.
The current 'released' wallet build does not include a working supercoin.conf file, and does not do jack-shit without it. This has completely stopped adoption by anyone that is not hanging out here, or enjoys screwing around with projects-in-development.
Installers are important for regular people... Regular people install something, and expect it to work with no manual steps, if it does not work they delete it, and then tell everyone it is a piece of shit. Right?
Regular people are the customer base any project needs to succeed in the real world. You want doctors, lawyers, investors, school teachers, farmers, your relatives, to use the product right? You know, regular people with more money than computer skills? That is the target market. It needs to be fast and simple for them to install and use.
The answers in bold are exactly why I asked that question.
3 wallet builds, 3 os's, installed in at least 2 os versions each, with no testing, just release it after making changes. [facepalm]
There are multiple people here that would be happy to test it in many operating systems\versions, if you choose to work with them.
Will you allow input before changes and feedback before releasing builds?
I am also worried about securely releasing a software product that handles money. That is why I asked if release builds will be built by you and include a hash of the build to ensure the download isn't compromised. It is simply a trust issue, if you put your name on it and provide a hash, it provides some basic accountability, which would be appreciated.
Will you release it securely?
Besides the last 2 important questions above, your experience and current wallet project looks really awesome, and I am looking forward to seeing your work.