Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0019034 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
feature request | [Openbravo ERP] B. User interface | major | always | 2011-11-10 01:13 | 2013-01-10 15:01 | |||||||
Reporter | dbaz | View Status | public | |||||||||
Assigned To | dbaz | |||||||||||
Priority | urgent | Resolution | open | Fixed in Version | ||||||||
Status | feedback | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Review Assigned To | ||||||||||||
Web browser | Google Chrome | |||||||||||
Modules | Core | |||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0019034: The form layouter toolbar icon doesn't get the "asterisk" if the form layout has been edited | |||||||||||
Description | The form layouter toolbar icon doesn't get the "asterisk" if the form layout has been edited | |||||||||||
Steps To Reproduce | * Go to any window * Click the form layoutter toolbar icon * Do any change * Save * Close the form layoutter * Notice that the form layoutter icon doesn't have the "modified" asterisk | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | ||||||||
|
Notes | |
(0042713) rgoris (developer) 2011-11-10 09:03 |
The asterisk has been intentionally taken out. The rationale is that there is no added value for the user knowing that a form has been modified. In fact, in most cases (when using an *) the * will always be shown as on day 1 the form will be customized for the user. This kind of subverts the notion of giving the user a visual cue of something that happens. Also, how is changing a form layout different than changing a grid layout? Would that need an visual cue as well? |
(0042718) dbaz (developer) 2011-11-10 10:28 |
As a user I personally loved this feature. In the grid, you miss some information (section, order, status bar, filtered columns, hidden columns) and is plenty of visual cues: for hidden columns clicking in a drop down you see all the columns, for the filter you see the funnel, for status bar you can see the columns, etc etc. All of them you know without lose sight of the grid. For the order, you have to specify save the view to persist it (remember that there is a feature request to know if you are in a view or not), and even for sections there is a feature request (although this is for me the less important). So in the grid you don't have to open a different window to know if something has happened or not. As I said in the beginning, I would like to know if the form layout is the standard one or not without the need to open the form layoutter, and click "Restore defaults" to see if anything is changed or not. This feature was already built, so it is not expensive to have it, we are not talking about a big development to put it in place. |
(0042722) mtaal (manager) 2011-11-10 12:17 |
In all I think it is not that important to spend any time on this. If there is a great need to see that the current view (form or grid) has been changed but not saved then we should do it at view level (to also show that the grid has changed). So in the views button. But again, I don't at all see the importance of this issue... gr. Martin |
(0053143) mtaal (manager) 2012-10-09 09:26 |
He Guys, Going through older issues... For this one, I propose to either do something, maybe add a different background to the customize view button in the toolbar? Or to close it. I vote for the latter! gr. Martin |
(0053181) dbaz (developer) 2012-10-09 20:38 |
I am still for getting the * back, and my arguments are the same I give some comments above. |
(0053414) ioritzCia (developer) 2012-10-17 10:37 |
Changed from critical to major as it is a feature request. |
(0053683) mtaal (manager) 2012-10-25 11:16 |
Hi, Getting back to this. I agree with David that it should be more visible. For example when you add a new field in the form in the application dictionary then this is not shown if there is a window personalization. It would be better to show somehow to the user that something has been customized,. Instead of the form personalization icon change, can we change the icon of the saved view button, so that you know that the standard view is overridden? Also have a better hover text on the saved view button saying which view has been applied. And then leave the form button as it is. gr. Martin |
Issue History | |||
Date Modified | Username | Field | Change |
2011-11-10 01:13 | dbaz | New Issue | |
2011-11-10 01:13 | dbaz | Assigned To | => mtaal |
2011-11-10 01:13 | dbaz | Web browser | => Google Chrome |
2011-11-10 01:13 | dbaz | Modules | => Core |
2011-11-10 01:44 | dbaz | Tag Attached: Regression | |
2011-11-10 09:03 | rgoris | Note Added: 0042713 | |
2011-11-10 10:28 | dbaz | Note Added: 0042718 | |
2011-11-10 12:17 | mtaal | Note Added: 0042722 | |
2011-11-10 12:18 | mtaal | Web browser | Google Chrome => Google Chrome |
2011-11-10 12:18 | mtaal | Type | defect => feature request |
2012-05-03 07:48 | mtaal | Tag Detached: Regression | |
2012-10-09 09:26 | mtaal | Note Added: 0053143 | |
2012-10-09 09:26 | mtaal | Status | new => feedback |
2012-10-09 15:59 | mtaal | Assigned To | mtaal => rgoris |
2012-10-09 20:38 | dbaz | Note Added: 0053181 | |
2012-10-17 10:37 | ioritzCia | Web browser | Google Chrome => Google Chrome |
2012-10-17 10:37 | ioritzCia | Note Added: 0053414 | |
2012-10-17 10:37 | ioritzCia | Severity | critical => major |
2012-10-25 11:16 | mtaal | Note Added: 0053683 | |
2012-10-25 11:16 | mtaal | Relationship added | related to 0021925 |
2013-01-10 15:01 | rgoris | Assigned To | rgoris => dbaz |
Copyright © 2000 - 2009 MantisBT Group |