elective-stereophonic
elective-stereophonic
GUI changes proposal for NXT messaging system
Please login or register.

Login with username, password and session length
Advanced search  

News:

Latest Stable Nxt Client: Nxt 1.12.2

Pages: [1] 2 3 4  All

Author Topic: GUI changes proposal for NXT messaging system  (Read 7662 times)

bahamapascal

  • Sr. Member
  • ****
  • Karma: +25/-3
  • Offline Offline
  • Posts: 318
    • View Profile
GUI changes proposal for NXT messaging system
« on: October 24, 2014, 01:45:46 pm »

Problem: A recipient of a NXT-message might not even notice that he/she received a message, as there is no notification.

The only way to notice that one has received a message is, a) See that there was a recent transaction to your account with 0 Nxt payload and then checking the massage "inbox" or b) Regularly looking into the "inbox" to see if something is there.

Though normally when one just opens the client to start forging, you don't look at the recent transaction and most likely won't look into the inbox (at lest I don't).


Possible Solution: Changing the GUI in such a way that on the Dashboard in the "Recent Transactions" tab, transactions containing a message are in a different (Aye catching) color. Maybe even labeled as "message". It should be fast to implement that change in the GUI and would already make a significant change so that messages won't be that easily missed by the recipient.


A more complex solution would be to make a pop-up window with "You received x new messages". This solution would require a bit more changes.
Here is how I imagine the technical concept for that:
When loging in to an account the Client checks the transactions of that account on the blockchain, counting the total amount of messages.
If amount of messages >0, then it will create a file(Y) noting down the message(s) and the block hight of the message(s). At the same time the user gets a "pop-up window "You received x new messages".
Next time user logs in, the client looks at file(y), takes the  blockhight(Z)  from last note and searches for messages above that blockhight. If there are messages for that account above blockhight(Z), client notes them down with corresponding blockhight in file(Y), and opens a "pop-up" window for the user.

Question: What are your thoughts about this(community)? Is this a good Idea?

To every one with technical knowledge, is my Idea possible(I don't have great technical knowledge) ? If so how long would it take to implement that?
I might be willing to set aside a bounty for this, so feedback is welcome :)


Logged

MrV777

  • Hero Member
  • *****
  • Karma: +115/-4
  • Offline Offline
  • Posts: 991
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #1 on: October 24, 2014, 01:49:39 pm »

It has been brought up that messages can be easily missed.  I wonder if Recent Transactions could have the icons so you know quickly what each transaction was.
Also, I'm thinking Recent Blocks shouldn't be on the Dashboard.  Maybe that should be replaced with recent Messages?  I do think that something else should go there.  The only reason I really pay attention to recent blocks is to make sure everything is working and see when the last block was.  I typically don't look any further than the most recent block though.
Logged
NXT: NXT-BK2J-ZMY4-93UY-8EM9V
NXT nodes: 209.222.98.250, 216.155.128.10

wesley

  • Hero Member
  • *****
  • Karma: +204/-3
  • Offline Offline
  • Posts: 1159
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #2 on: October 24, 2014, 01:55:02 pm »

Perhaps it would be good if there was an API call that returns all things that require user attention after a specified timestamp. So this would return that there are 2 new messages, 1 feedback on an item sale, 1 refund, and so on, ... Otherwise you may have to do too many requests to check all these things at startup.
Logged

cc001

  • Hero Member
  • *****
  • Karma: +68/-4
  • Offline Offline
  • Posts: 829
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #3 on: October 24, 2014, 02:02:14 pm »

Perhaps it would be good if there was an API call that returns all things that require user attention after a specified timestamp. So this would return that there are 2 new messages, 1 feedback on an item sale, 1 refund, and so on, ... Otherwise you may have to do too many requests to check all these things at startup.
good idea!
Logged
cc001 Personal - NXT-8RXS-2SSK-RNF2-HSNL8
NxtReporting.com - The Nxt Asset Exchange Portfolio Manager with Profitability Tracking - Donations are greatly appreciated on NXT-5W4G-GAR6-JHJP-H8ZTW

bahamapascal

  • Sr. Member
  • ****
  • Karma: +25/-3
  • Offline Offline
  • Posts: 318
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #4 on: October 24, 2014, 04:53:46 pm »

It has been brought up that messages can be easily missed.  I wonder if Recent Transactions could have the icons so you know quickly what each transaction was.
Also, I'm thinking Recent Blocks shouldn't be on the Dashboard.  Maybe that should be replaced with recent Messages?  I do think that something else should go there.  The only reason I really pay attention to recent blocks is to make sure everything is working and see when the last block was.  I typically don't look any further than the most recent block though.

Yes thats a good thoght, recent blocks could be sustituted with just the last block. That would free up space.

Thogh on the otherhand, would we need more space? If the "Recent Transactions" would have Icons/colors, maybe thats already sufficiant.

Perhaps it would be good if there was an API call that returns all things that require user attention after a specified timestamp. So this would return that there are 2 new messages, 1 feedback on an item sale, 1 refund, and so on, ... Otherwise you may have to do too many requests to check all these things at startup.

I am not sure what an API call actually is...but would the API work to determine which messages are actually new and which are old?
Whesley, what do you think about the pop-up notification window for new messages? How long or how hard would it be to implement that ?
Logged

galeki

  • Full Member
  • ***
  • Karma: +16/-2
  • Offline Offline
  • Posts: 228
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #5 on: October 24, 2014, 05:46:54 pm »

Agreed, it's also easily missed when somebody purchase your goods.

and correct me if i'm wrong, the only way to see the attach message of a Payment is clicking the timestamp?
Logged

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #6 on: October 24, 2014, 09:15:49 pm »

Perhaps it would be good if there was an API call that returns all things that require user attention after a specified timestamp. So this would return that there are 2 new messages, 1 feedback on an item sale, 1 refund, and so on, ... Otherwise you may have to do too many requests to check all these things at startup.

Notification Center?
Logged

jones

  • Hero Member
  • *****
  • Karma: +310/-8
  • Offline Offline
  • Posts: 1043
  • write code not war
    • View Profile
    • jNxt
Re: GUI changes proposal for NXT messaging system
« Reply #7 on: October 24, 2014, 09:37:28 pm »

This has been brought up previously, but the issue has been that there is no way of knowing if the user has viewed the message or not.
the current project of user db could solve this because we now have a local database to store things like these. We can then store whether or not the user has checked off messages as 'seen' in this. I can add another column in the user db to account for this, the rest is just front end and ui
Logged
-- Jones NXT-RJU8-JSNR-H9J4-2KWKY

TwinWinNerD

  • Hero Member
  • *****
  • Karma: +222/-116
  • Offline Offline
  • Posts: 2012
  • CEO BitPanda.com
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #8 on: October 24, 2014, 09:45:49 pm »

Can't we solve this with use of clientside cookies/entries?

jones

  • Hero Member
  • *****
  • Karma: +310/-8
  • Offline Offline
  • Posts: 1043
  • write code not war
    • View Profile
    • jNxt
Re: GUI changes proposal for NXT messaging system
« Reply #9 on: October 24, 2014, 09:46:59 pm »

Can't we solve this with use of clientside cookies/entries?

What if someone logs on to their account from a different node/computer?
Logged
-- Jones NXT-RJU8-JSNR-H9J4-2KWKY

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #10 on: October 24, 2014, 09:49:31 pm »

Can't we solve this with use of clientside cookies/entries?

What if someone logs on to their account from a different node/computer?

It seems this is not solvable, not by nxt_user_db nor by cookies. :)
Logged

jones

  • Hero Member
  • *****
  • Karma: +310/-8
  • Offline Offline
  • Posts: 1043
  • write code not war
    • View Profile
    • jNxt
Re: GUI changes proposal for NXT messaging system
« Reply #11 on: October 24, 2014, 09:53:22 pm »

Can't we solve this with use of clientside cookies/entries?

What if someone logs on to their account from a different node/computer?

It seems this is not solvable, not by nxt_user_db nor by cookies. :)

My thought is that someone needs their nxt_user_db to log into their account. It holds the ciphertext that is decrypted to make the passphrase for the account. This way, at any other node, they will need to import their nxt_user_db, and the data will be updated to it next time after they export that data.
Logged
-- Jones NXT-RJU8-JSNR-H9J4-2KWKY

galeki

  • Full Member
  • ***
  • Karma: +16/-2
  • Offline Offline
  • Posts: 228
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #12 on: October 24, 2014, 09:53:37 pm »

Can't we solve this with use of clientside cookies/entries?

What if someone logs on to their account from a different node/computer?

It seems this is not solvable, not by nxt_user_db nor by cookies. :)

we can package that info into wallet.dat if we have one   ;)
Logged

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #13 on: October 24, 2014, 09:55:59 pm »

Can't we solve this with use of clientside cookies/entries?

What if someone logs on to their account from a different node/computer?

It seems this is not solvable, not by nxt_user_db nor by cookies. :)

we can package that info into wallet.dat if we have one   ;)

What is the difference to a cookies or a nxt_user_db?
Logged

TwinWinNerD

  • Hero Member
  • *****
  • Karma: +222/-116
  • Offline Offline
  • Posts: 2012
  • CEO BitPanda.com
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #14 on: October 24, 2014, 09:56:26 pm »

Why is it a problem if someone logs into the account from another computer? Then he will be shown the "old" messages again. So what?

Better twice then never. I have missed tons of messages and tons of messages attached to asset transfers. If I get them atleast once per computer, that is a major improvement.

Also as I understand it, we currently get the notification "XXXX Assets received" also for each computer seperate once you login.

jones

  • Hero Member
  • *****
  • Karma: +310/-8
  • Offline Offline
  • Posts: 1043
  • write code not war
    • View Profile
    • jNxt
Re: GUI changes proposal for NXT messaging system
« Reply #15 on: October 24, 2014, 10:02:39 pm »

Can't we solve this with use of clientside cookies/entries?

What if someone logs on to their account from a different node/computer?

It seems this is not solvable, not by nxt_user_db nor by cookies. :)

we can package that info into wallet.dat if we have one   ;)

What is the difference to a cookies or a nxt_user_db?

If they are taken from the prospective of a user that doesn't bother to import/export anything (most of them) then I guess the result would be the same. I agree that messages should be highlighted in the 'recent transactions' tab, that would improve the noticeability, as for the notification, if someone can find how to get persistence across multiple nodes, that would be great.
Logged
-- Jones NXT-RJU8-JSNR-H9J4-2KWKY

galeki

  • Full Member
  • ***
  • Karma: +16/-2
  • Offline Offline
  • Posts: 228
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #16 on: October 24, 2014, 10:11:58 pm »

Can't we solve this with use of clientside cookies/entries?

What if someone logs on to their account from a different node/computer?

It seems this is not solvable, not by nxt_user_db nor by cookies. :)

we can package that info into wallet.dat if we have one   ;)

What is the difference to a cookies or a nxt_user_db?

easily understand, import, backup... and bind the info to their accounts :)

put that dat file in USB stick and login with that everywhere  ;D


or we can make a marker transcation on logout when the fee is low enough.
Logged

bahamapascal

  • Sr. Member
  • ****
  • Karma: +25/-3
  • Offline Offline
  • Posts: 318
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #17 on: October 25, 2014, 12:39:51 pm »

Great, I see every one dose agree that the current messaging-visability has to be improved. Though just knowing "it has to be changed" won't help us at all :D

So basicaly my solution proposal is correct, as far as I can tell from the discussion here. Every thing we do would be on a local basis* and GUI (for now).  But as TwinWin already pointed out, thats nothing to worry about.
I guess 99% of the time people use there nxt acounts from the same PC, and if some one really uses the Nxt system from a different PC...I think it won't hurt them to get a "new messages" pop-up for old messages.


As it seems to be the easiest way and wont require any big changes, I propose we change the GUI of the "Recent Transactions" tab first. Making  Messages in a different color, giving each transaction type a different symbol and maybe labeling the type of each transaction.

Who is doing the GUI work for the client right now? I would like to contact him/her, to see how much work/time it would take to change that. Then see what a apropriate bounty would be for that task, if the bounty wont be to high, I hope we can get that in for next release :)



* later on I could even amagine that we could find ways to make it non-local.

Logged

nxtrules

  • Sr. Member
  • ****
  • Karma: +15/-1
  • Offline Offline
  • Posts: 254
    • View Profile
GUI changes proposal for NXT messaging system
« Reply #18 on: October 25, 2014, 01:56:53 pm »

Can't we solve this with use of clientside cookies/entries?

What if someone logs on to their account from a different node/computer?

It seems this is not solvable, not by nxt_user_db nor by cookies. :)

My thought is that someone needs their nxt_user_db to log into their account. It holds the ciphertext that is decrypted to make the passphrase for the account. This way, at any other node, they will need to import their nxt_user_db, and the data will be updated to it next time after they export that data.

Let's start using local storage instead of cookies. It's been working great and all the browsers support it. I don't think we should persist it in the db. Decentralization should make as think differently ;-). IMO

http://nxtrules.mooo.com
« Last Edit: October 25, 2014, 01:59:41 pm by nxtrules »
Logged
http://nxtrules.mooo.com {NXT investment tracking with multiple account support}

ChuckOne

  • Hero Member
  • *****
  • Karma: +293/-17
  • Offline Offline
  • Posts: 3450
  • ☕ NXT-4BTE-8Y4K-CDS2-6TB82
    • View Profile
Re: GUI changes proposal for NXT messaging system
« Reply #19 on: October 25, 2014, 03:33:10 pm »

Who is doing the GUI work for the client right now? I would like to contact him/her, to see how much work/time it would take to change that. Then see what a apropriate bounty would be for that task, if the bounty wont be to high, I hope we can get that in for next release :)

Start an issue here at BitBucket https://bitbucket.org/JeanLucPicard/nxt/issues?status=new&status=open

MrV will take care of it.
Logged
Pages: [1] 2 3 4  All
 

elective-stereophonic
elective-stereophonic
assembly
assembly