Merge lp:~jamalta/gwibber/298898 into lp:gwibber/1.2
Status: | Rejected | ||||
---|---|---|---|---|---|
Rejected by: | Ken VanDine on 2012-05-09 | ||||
Proposed branch: | lp:~jamalta/gwibber/298898 | ||||
Merge into: | lp:gwibber/1.2 | ||||
Diff against target: | None lines | ||||
To merge this branch: | bzr merge lp:~jamalta/gwibber/298898 | ||||
Related bugs: |
|
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Alexander Sack (community) | 2009-07-10 | Needs Fixing on 2009-07-12 | |
Review via email:
|
Jamal Fanaian (jamalta) wrote : | # |
> The implementation is not yet complete imho; at least we should do two things:
>
> 1. fix the case when the user starts typing while he is at some pos < len ? I
> think when that happens we should reset the pos to len so the changed text
> gets saved as the new "current" (topmost) text.
>
> 2. the history buffer shouldn't grow indefinitely; please constraint it to
> 20-50 messages; consider to make the history buffer size configurable.
I will work on a fix for the 2nd issue.
Regarding the 1st issue, are you talking about the user typing something when they move up the buffer (pos < len) and then move again, thus losing what they typed? I think if the buffer gets switched to "current" (pos = len), it might confuse the user as they are now at the end of the buffer without realising it. I can think of one alternative, which is to save changes to the position when the user moves from it. This would end up working as it works when scrolling up and down the bash history. Which way of doing it do you think is better? I have implemented the first method, but I don't think it is the best way of doing things.
Thanks for your input. I really appreciate it, as it is very helpful.
- 348. By Jamal Fanaian on 2009-07-13
-
Added a max limit to the messages history. When a message is sent the limit will be checked and the list will be sliced if necessary.
Jamal Fanaian (jamalta) wrote : | # |
> The implementation is not yet complete imho; at least we should do two things:
>
> 1. fix the case when the user starts typing while he is at some pos < len ? I
> think when that happens we should reset the pos to len so the changed text
> gets saved as the new "current" (topmost) text.
>
> 2. the history buffer shouldn't grow indefinitely; please constraint it to
> 20-50 messages; consider to make the history buffer size configurable.
The last commit added saving of the buffer whenever the position is moved, so if the message is changed it will not be lost. This, to me, seemed to be the best way to implement this. Please comment if you feel otherwise and I will resolve it.
Thanks again for your time.
- 349. By Jamal Fanaian on 2009-07-13
-
Changed messages in buffer will now be saved
- 350. By Jamal Fanaian on 2009-07-13
-
Removed feature to modify the message history
Unmerged revisions
- 350. By Jamal Fanaian on 2009-07-13
-
Removed feature to modify the message history
- 349. By Jamal Fanaian on 2009-07-13
-
Changed messages in buffer will now be saved
- 348. By Jamal Fanaian on 2009-07-13
-
Added a max limit to the messages history. When a message is sent the limit will be checked and the list will be sliced if necessary.
- 347. By Jamal Fanaian on 2009-07-09
-
Created a message history list that gets appended on message send. Added a key_press_event to the input editor to detect for Ctrl+Up and Ctrl+Down and move through the message history.
The implementation is not yet complete imho; at least we should do two things:
1. fix the case when the user starts typing while he is at some pos < len ? I think when that happens we should reset the pos to len so the changed text gets saved as the new "current" (topmost) text.
2. the history buffer shouldn't grow indefinitely; please constraint it to 20-50 messages; consider to make the history buffer size configurable.