Jump to content


Photo

Language assistance requested...


  • Please log in to reply
786 replies to this topic

Re: Language assistance requested... #781 Huevos

  • Senior Member
  • 1,951 posts

+104
Excellent

Posted 21 September 2018 - 15:32

Can you point me to that part...

 

Actually you navigate with left/right/up/down and you have equal keys in each row... so I do not see how the navigation can be done quickly for larger buttons...

That is what happens when people confuse something that looks good in a jpeg image with something that is a practical, user friendly interface.

 

If you have a wide button with 2 narrow buttons above it how does the UI ever decide which narrow button to select when moving from the wide button to the narrow button. For this reason, IMO, all buttons should form a grid where it is 100% clear which cell becomes active to when pressing LEFT/RIGHT/UP/DOWN.

 

Aesthetics should come second to a user friendly interface. And whether Ian's keyboard has any aesthetic problem is a matter of opinion anyway.


Edited by Huevos, 21 September 2018 - 15:36.


Re: Language assistance requested... #782 Pr2

  • PLi® Contributor
  • 2,842 posts

+119
Excellent

Posted 21 September 2018 - 16:30

You can keep the grid approach even with wider buttons, a wider button is just a button that include several adjacent cells, you just need to remember the former button position.

So when you reach the wider button you can always easily return to this last position depending on the direction decided by the end-user.


NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.

If you think that my answer helps you, you can press the up arrow in bottom right the answer.

 

Octagon SF-4008: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W (+DVB-C)
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C)
Zgemma H5: 1*DVB-S2 + 1*DVB-C

Zgemma H7C: 1*DVB-S2 + 2*DVB-C


Re: Language assistance requested... #783 littlesat

  • PLi® Core member
  • 45,233 posts

+463
Excellent

Posted 21 September 2018 - 16:58

Indeed... only when you do left/right you need to ‘skip’
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W Thanks to Henksat

Re: Language assistance requested... #784 Rob van der Does

  • Senior Member
  • 7,637 posts

+177
Excellent

Posted 21 September 2018 - 16:58

Actually you navigate with left/right/up/down and you have equal keys in each row... so I do not see how the navigation can be done quickly for larger buttons...

Exactly!



Re: Language assistance requested... #785 Taapat

  • PLi® Core member
  • 1,439 posts

+69
Good

Posted 21 September 2018 - 17:55

I can make mistakes, but at this moment I understand this:
The code already assumes that the size of the buttons in the skin may vary.
Therefore, you can use larger buttons in HD skins.
The same thing works if the button size is only wider and not bigger.
Therefore, in markSelectedKey is the check for select button location and size: https://github.com/O...eyBoard.py#L404
 
If we are talking about button sizes then I agree that the left/right/up/down navigation buttons of different sizes may be a problem.
It seems to me that a button with 2-button size, if it is just on the edges of the keyboard, is a very small problem. There is no big problem going one position to the right or left if we leave it.
A bigger problem might be space if it has a large size. In the current code this button looks like one button with a wider size, so it does not remember the previous position.
 
But if we consider that the left/right/up/down navigation as a priority, then the existing layout 4x14+1x7 is not good enough.
Then you should use for example 5x13.
 
If anyone says that the view is less important than navigation that was used until now, then you should have told this Steve Jobs 10 years ago, when he released the iphone without buttons ;) .

Edited by Taapat, 21 September 2018 - 17:59.


Re: Language assistance requested... #786 Huevos

  • Senior Member
  • 1,951 posts

+104
Excellent

Posted 21 September 2018 - 18:23

 

If anyone says that the view is less important than navigation that was used until now, then you should have told this Steve Jobs 10 years ago, when he released the iphone without buttons ;) .

 

I don't know what you mean. The iPhone uses a tactile screen there the user touches the required button, i.e. an image map, not left/right/up/down buttons on a remote control.



Re: Language assistance requested... #787 Taapat

  • PLi® Core member
  • 1,439 posts

+69
Good

Posted 21 September 2018 - 18:36

I think that before first iphone many thought that navigation was possible only with buttons. And if something changes this, then it will not be usable.
 
But I also like simple and understandable things.
Therefore, I do not like the current keybord, which is not symmetrical and contains non-usable buttons.
I do not know what would be the right way. Seeing the sss keyboard I think it might be a wide buttons.
But maybe I'm wrong.
It seems to me that I will create it, and try how it works.

Edited by Taapat, 21 September 2018 - 18:37.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users