Topic: [ANN] Syscoin- FINAL 2.0 LAUNCHED! *ENCRYPTION, MARKETPLACE, BTC INTEGRATION* - page 193. (Read 582967 times)

That is the plan going forward as per Dan's post.

Devs,

Not sure if my perspective is dead-on, but here goes:

I'm getting the impression that you all are coding and implementing - but purely from a programmer's perspective.

Please consider that the vast majority of people who will install and use this wallet are *NOT* coders. None of us should be expected to (and probably many can't) kludge their way around shortcomings in the interface or function of same.

General analogy - automobile drivers shouldn't have to know how to build their vehicles or conduct major repairs on their newly purchased vehicles. Automobiles are pretty much turn-key and come with fairly adequate documentation of their features and options (not so much lessons how to drive, but where to find the fuses and how to use the satnav).

In the same way, simple users of your software should not have to know linux, c+, python, or whatever. We shouldn't have to understand programming/coding related jargon or anything else. We shouldn't have to JFGI anything in order to work around things like locked wallets or determine what a feature (such as alias) actually is.

Sometime between now and 0.1.6 - please spend some time testing to make sure things aren't neglected (not able to unlock wallet when creating an alias via the menu), invest a bit of time creating some clear documentation written in complete sentences with a minimum of jargon, and be sure that documentation includes plenty of explanation of what each feature is and does before explaining the HOW.

I think a quick round of user acceptance testing would be a big help in this regard. Would just take a very small group a few hours to iron out any howlers (such as this passphrase palava..).

Moderated due to double posts.

Actually I hit this issue when I use other wallets, it's a legacy of Bitcoin design, if SYS wallet improve this thing, it's very positive.

The most thing in UI design is user friendly and beautiful, maybe you can hire some expertise in UI degisn, UI is simple to developer, but it's very important to users.

EVERYONE encrypts their wallet. I don't know anyone that doesn't. Why should I go to the console to unlock it? Why wasn't this tested? It's not RC at all. I questions your team's programming techniques even more now considering you have difficulty testing properly and not knowing the difference between Alpha,Beta and RC!

This is true, the wallet works fine, there's just a few improvements to be made and this RC can go live, imo. Nice one @dano - ignore that throwaway fudster.

What are you talking about? Honestly.
2 minor issues has been reported in relation to the release candidate.

For the new alias functionality
1. If wallet is encrypted you have to unlock it manually
2. Hit enter on search screen.

How is that an nonworking wallet?

I am angry because even I submit patches to fix some known issues in previous version,
they still let the issue be there untouched in this later version,
even though they have already accepted the patch.

I can't bear the attitude, as a big whale, I can't stop my anger.

Man, don't be so harsh to the developers, just report the issues ,they will fix them.

No need to to throw around insults. It is a good suggestion though, will add it to the list.

OK this is a bug then. Other wallet functions that require authorisation return a passphrase prompt. Thanks for clearing that up.

So, why we need the new UI for alias?
just go to the console and do all the tasks.

And, what the hell can I get the instruction when I want to do something on alias?

Just adding another input box for the password under the already exists two input boxes,
and invoking the command under the hood when I click the "OK" button is trivial, right?

Don't tell me that you have no the capability to implement them.

Wallet encrypted I take it.
Help / Debug window / Console
walletpassphrase "your wallet password" 5000
The 5000 is the total time it will be unlocked.

I somewhat support part of what Keji is saying.

The feedback link isn't loading at all, so I was unable to submit anything there.
I've followed several links that end up taking me to scattered places like github (which means nothing to me and somewhat confusing WTF it is).
I can find the list of SYSCoin commands well enough, but as a user they are a bit vague.
I want to know ABOUT aliases and such, before I need to know HOW to create or modify them. I haven't seen a link or any documentation saying WHAT an alias *IS*.
The same thing applies to other elements/features.

Perhaps it is time to consider locating a good technical writer to create some documentation that defines what things are, suggestions regarding why and when we want to use which, and THEN in plain language how to make it happen.

I was going to test some of the RC functions and report back, but at the moment I can only use the wallet to send and receive coins - due to lack of sensible reading material.

Trying to be constructive, not b*tchy, about this. I hope I didn't come across poorly.

You're more active in here this morning than on the Syscoin forum thread you're trying to redirect people to, what's that all about...? Come on guys...

Did you see the PM I sent to you and danosphere about the patch I gave(I don't want to mention it here)?

I am quite disappointed when I saw the wallet, in many aspects.

It made me recall what happend during the launch,
and my confidence on the team rebuilt slowly after that now collapsed again.

A RC version should not in such a quality.

You guys should at least test it in a virtual machine with pure clean environment first before release a version with new feature to avoid such stupid issues.

As a big whale, god bless me to see better professionality and proficiency of you from now on.

You need to follow what everyone else is doing and follow the links provided. You maybe bringing up issues already being addressed / investigated.

issue 2:  in the alias searching tab, after I input the to be searched term, I must click the search button,
because "ENTER" key does not work, that's counterintuitive