Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0016499 | Openbravo ERP | A. Platform | public | 2011-03-26 18:09 | 2011-04-06 00:00 |
|
| Reporter | psarobe | |
| Assigned To | mtaal | |
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | |
| Platform | | OS | 5 | OS Version | |
| Product Version | pi | |
| Target Version | 3.0RC6 | Fixed in Version | 3.0RC6 | |
| Merge Request Status | |
| Review Assigned To | |
| OBNetwork customer | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0016499: After selecting a value in a selector, the focus must move to the next field |
| Description | In 2.50 whenever you selected a product, the focus moved to Quantity field since that is the normal flow (next action):
1. You select a product
2. You change the quantity
In 3.0 this doesn't happen anymore so after talking with Rob and several people from GPS this is what we want to have in form and grid view:
1. Whenever you select a business partner, product (in short, selector fields) the focus moves to the next field (without taking into account not editable fields)
2. Whenever you select a something from a combo box, the focus moves to next field
3. Whenever you select a date the focus moves to the next field. Here two scenarios:
3.1 Usual scenario: The end user type the date. The system according with the mask must know when the date is entering and moves to the next field
3.2 Other scenario: You click the calendar and pick a date. The focus moves to the next field
Martin, what it would be great is as a general rule, as it happens in most of the forms for example entering the bank account, that when you type something and you reach the length for that field the system automatically drives you to the next field
Regards |
| Steps To Reproduce | |
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2011-03-26 18:09 | psarobe | New Issue | |
| 2011-03-26 18:09 | psarobe | Assigned To | => mtaal |
| 2011-03-26 18:09 | psarobe | Modules | => Core |
| 2011-03-26 18:15 | psarobe | Status | new => scheduled |
| 2011-03-26 18:15 | psarobe | fix_in_branch | => pi |
| 2011-03-28 09:28 | rgoris | Note Added: 0035259 | |
| 2011-03-28 10:34 | rgoris | Note Edited: 0035259 | bug_revision_view_page.php?bugnote_id=0035259#r1719 |
| 2011-03-28 10:38 | rgoris | Note Added: 0035263 | |
| 2011-03-28 23:34 | psarobe | Note Added: 0035291 | |
| 2011-04-04 19:20 | hgbot | Checkin | |
| 2011-04-04 19:20 | hgbot | Note Added: 0035573 | |
| 2011-04-04 19:20 | hgbot | Status | scheduled => resolved |
| 2011-04-04 19:20 | hgbot | Resolution | open => fixed |
| 2011-04-04 19:20 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/705e3208ec211979e1447dad701e79222355db5c [^] |
| 2011-04-05 12:19 | psarobe | Note Added: 0035594 | |
| 2011-04-05 12:19 | psarobe | Status | resolved => closed |
| 2011-04-05 12:19 | psarobe | Fixed in Version | => 3.0RC6 |
| 2011-04-05 12:20 | psarobe | fix_in_branch | pi => |
| 2011-04-05 12:20 | psarobe | Summary | Dramatically improve the usability. Some issues => After selecting a value in a selector, the focus must move to the next field |
| 2011-04-06 00:00 | anonymous | sf_bug_id | 0 => 3276669 |
|
Notes |
|
|
(0035259)
|
|
rgoris
|
2011-03-28 09:28
(edited on: 2011-03-28 10:34) |
|
The idea in general is good and commonly used in other applications where high speed data entry is required.
However, there are some scenarios where it can work against the user. For example order line entry in grid where only the product needs to be chosen. E.g. in Paolo´s demo video at 33m30s (see our Teambox discussion).
It would be best to make this configurable.
Proposed approach: first implement the feature. Then wait for feedfback and see if it is necessary to make it configurable.
|
|
|
|
(0035263)
|
|
rgoris
|
|
2011-03-28 10:38
|
|
re: "what it would be great is as a general rule, as it happens in most of the forms for example entering the bank account, that when you type something and you reach the length for that field the system automatically drives you to the next field"
-- Let´s do it for dates only first. |
|
|
|
|
Martin,
finally after discussing with Ismael he agreed to go ahead with everything except when typing with the dates, only when selecting the date. So you have to:
1. For selector moves to next field
2. For combo boxes moves to next field
3. When selecting a date from the calendar moves to next field |
|
|
|
(0035573)
|
|
hgbot
|
|
2011-04-04 19:20
|
|
Repository: erp/devel/pi
Changeset: 705e3208ec211979e1447dad701e79222355db5c
Author: Martin Taal <martin.taal <at> openbravo.com>
Date: Mon Apr 04 19:19:46 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/705e3208ec211979e1447dad701e79222355db5c [^]
Fixes issue 16499: Dramatically improve the usability. Some issues
---
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/ob-formitem-widgets.js
M modules/org.openbravo.client.application/web/org.openbravo.client.application/js/ob-view-form.js
M modules/org.openbravo.userinterface.selector/web/org.openbravo.userinterface.selector/js/ob-selector-item.js
---
|
|
|
|
|
|