Re: Namecoin-Qt BETA with Namespace Registration 3.67
Posted: Sat Aug 31, 2013 4:11 pm
should be fixed, any chance can see if it compiles on linux now? <3
The first secure, decentralized, human-meaningful naming system.
https://forum.namecoin.org/
1. can probably do thatomyno wrote:Thank you so much for creating namecoin-qt, this looks great already!
There are some usability issues I'd like to point to:
There are some other small issues with the current interface but those mentioned should definitely be addressed in my opinion.
- For me, the default width of the window leads to a hidden "Manage Names" button. Do you think the default width could be increased or can this be solved in some other way?
- Would "Register" instead of "Submit" be a better choice for the button?
- The UI should not use terms like "name_new", "name_firstupdate" at all.
- The column "Expires in" should contain an estimated date/time.
- What do you think about a drop-down menu for the prefix? In this drop-down menu a user can choose between "Domain", "Identity", "Custom" etc. This way the long explanation below the input field is not necessary anymore.
- Can we really expect the user to enter JSON strings manually? Are plain JSON strings necessary in any way? Again, drop-down menus or something similar would make it easier to enter values.
Fixed.snailbrain wrote:should be fixed, any chance can see if it compiles on linux now? <3
Do you use a non default font size possibly? This is not the case for most other people...omyno wrote:Thank you so much for creating namecoin-qt, this looks great already!
There are some usability issues I'd like to point to:
- For me, the default width of the window leads to a hidden "Manage Names" button. Do you think the default width could be increased or can this be solved in some other way?
It submits a request for registration to the network so IMHO it's ok.[*]Would "Register" instead of "Submit" be a better choice for the button?
Without that you will never be able to understand what is happening. With the automatic postponed name_firstupdate the GUI is going pretty far already.[*]The UI should not use terms like "name_new", "name_firstupdate" at all.
That would be nice but might give a wrong feeling of safety in case of drastic hash rate increases... maybe a very conservative date would be ok, like: "some time after ..."[*]The column "Expires in" should contain an estimated date/time.
Interesting idea. It should at least contain an "other / raw" option, though.[*]What do you think about a drop-down menu for the prefix? In this drop-down menu a user can choose between "Domain", "Identity", "Custom" etc. This way the long explanation below the input field is not necessary anymore.
Well, for domains there is already GUI supported entering...[*]Can we really expect the user to enter JSON strings manually? Are plain JSON strings necessary in any way? Again, drop-down
menus or something similar would make it easier to enter values.[/list]
IMHO we should make an official release first. There is plenty of room for improvement but as it is now it is already a huge step, especially for the less technically obsessed.There are some other small issues with the current interface but those mentioned should definitely be addressed in my opinion.
Turns out this is a slightly bigger problem than I previously thought. It does not seem to display name_firstupdate / name_update names so it is more difficult to find failed transactions.domob wrote:I think to remember that the official namecoind did display the names ... that's why I "miss" that, although I agree that that's not actually an "address" and it would maybe be better to just add a new field for name operations to the returned JSON object. What do you think about that? This could be done also for name_new, to be consistent.snailbrain wrote:We think listtransactions shouldn't show names, since it's not a name operation (i.e. it must be compatible with Bitcoin). also maybe cause problem with people switching between official and namecoind (from qt)?domob wrote:Works for me as advertised! Thanks also for adding the name_update operations in listtransactions. However, I think it would be great if more details were shown. Currently a name_firstupdate just looks like sending 0 NMC to some address ... what about adding some information as name_new shows? For instance, add the text "name_update: d/my-name" in the address field or so?
but can discuss if everyone thinks otherwise.. and add on todo for future update.
This change breaks my windows build... I think this line was not in the public namecoin-qt releases. Also I don't see why it would be necessary as all includes seem to have the proper directory prefixed (maybe there is one path missing for Linux?).moa wrote:Latest from github doesn't build on linux ... the dir re-restructure causes include errors. You need to re-instate the line
into namecoin-qt.pro ... it was in there previously ...as it is for the bitcoin-qt.proCode: Select all
INCLUDEPATH += src src/json src/qt
Code: Select all
TARGET = namecoin-qt macx:TARGET = "Namecoin-Qt" VERSION = 0.3.68 [b]INCLUDEPATH += src src/json src/qt[/b] QT += network DEFINES += GUI QT_GUI BOOST_THREAD_USE_LIB BOOST_SPIRIT_THREADSAFE CONFIG += no_include_pwd ...
Code: Select all
!win32 {
INCLUDEPATH += src src/json src/qt
}
Code: Select all
INCLUDEPATH += src/json src/qt