Project

General

Profile

feature request #8045

Improve handling of default values and override in local preferences

Added by Katja Luther 5 months ago. Updated 4 months ago.

Status:
New
Priority:
Highest
Assignee:
Category:
taxeditor
Start date:
01/31/2019
Due date:
% Done:

0%

Severity:
normal

Description

For selection of default, dbPreference or explicit local value the local preference pages should have combo boxes.

Depending on his selection the local preference should be handled:

  • default: save the default value
  • db preference: delete the value in local preferences if exist
  • exlicit value: save to preference file

Related issues

Related to Edit - bug #7856: Allow local override for distribution vocabularies Closed 10/23/2018
Related to Edit - bug #7849: Improve DB Preferences handling and saving in TaxEditor Feedback 10/23/2018

Associated revisions

Revision 9fe7e119 (diff)
Added by Katja Luther about 2 months ago

ref #8045: show possible entries for preferences in combo boxes and show default value

Revision 755105d4 (diff)
Added by Katja Luther about 2 months ago

ref #8045: show possible entries for preferences in combo boxes and show default value - continue

Revision 1000779d (diff)
Added by Katja Luther about 2 months ago

ref #8045: add Interface for Preference Enums

Revision cc1302bd (diff)
Added by Katja Luther about 1 month ago

ref #8045: check whether all db preferences are deleted from DB if value is default value

Revision 63732a7c (diff)
Added by Katja Luther 29 days ago

ref #8045: further implementation for default/explicit value selection preference pages

Revision 4d025474 (diff)
Added by Katja Luther 29 days ago

ref #8045: add remove to preference service and dao

Revision bfaa6a16 (diff)
Added by Katja Luther 27 days ago

ref #8045: add toString() to the preference enums

History

#1 Updated by Andreas Müller 5 months ago

I don't know if we really need "db preference" as explicit value. It makes it more difficult to understand and there is almost no added value (compared to "default". So we only need "default" and the list of explicit values. If "default" is chosen then the preference is deleted from the local preferences.

#2 Updated by Katja Luther 5 months ago

I would show the value of the db preference in the drop down, but with ("global") or ("db") behind

#3 Updated by Andreas Müller 5 months ago

Katja Luther wrote:

I would show the value of the db preference in the drop down, but with ("global") or ("db") behind

OK, if this is not an explicit entry but if it is only added to the anyway existing entry for this value. Maybe "recommended" is another possible label. A bit long but standard for many such cases.

#4 Updated by Katja Luther 5 months ago

  • Related to bug #7856: Allow local override for distribution vocabularies added

#5 Updated by Andreas Müller 5 months ago

  • Related to bug #7849: Improve DB Preferences handling and saving in TaxEditor added

#6 Updated by Andreas Müller 5 months ago

  • Subject changed from local preferences pages with drop down to Improve handling of default values and override in local preferences

#7 Updated by Andreas Müller 4 months ago

  • Target version changed from Release 5.6 to Reviewed Next Major Release

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)