Opened 18 years ago

Last modified 7 years ago

#344 assigned enhancement

Unify file/folder names in ~/config/settings — at Version 15

Reported by: diver Owned by: axeld
Priority: low Milestone: Unscheduled
Component: - General Version: R1/Development
Keywords: R2 Cc:
Blocked By: Blocking:
Platform: All

Description (last modified by humdinger)

Could we prettify ~/config/settings? Currently there is no standard settings names for apps/prefs some of them capitalized/underlined or have settings postfix. Maybe would be better to have a standart naming, such as for ex: "$app_name$_settings" or just "$app_name$" in the lower case or 1st letter in upper case like "$App_name$". screenshot of current name hell will follow.

Some folders could also do with a unified name, e.g. in Tracker there's DefaultFolderTemplates and DefaultQueryTemplates, but "Tracker New Templates".

Some folders are lower case, which should be upper case, e.g. deskbar, expander, pe.
What about boot, global, kernel, mime_db, printers, system?

Change History (16)

comment:1 by diver, 18 years ago

attachments.description: setings hellsettings hell

by diver, 18 years ago

Attachment: settings.PNG added

settings hell

comment:2 by diver, 18 years ago

Owner: changed from sikosis to axeld

comment:3 by axeld, 18 years ago

I would like that, too, but we'd need to "break" compatibility for that, ie. when upgrading to Haiku, you'd lose all your settings. Of course, we could make all apps be able to read old settings, but write their settings to a different place afterwards - but that's not very nice, and probably also just not worth the effort.

comment:4 by korli, 18 years ago

bug_group: developers

comment:5 by axeld, 17 years ago

Description: modified (diff)
Platform: All
Priority: normallow

comment:6 by wkornewald, 17 years ago

Do we want to do this, at all? This looks more like something for R2 when we define a real settings API which does this job, automatically.

comment:7 by diver, 16 years ago

Type: bugenhancement

comment:8 by nielx, 16 years ago

Milestone: R1Unscheduled

Change the milestone according to the type change of the ticket.

comment:9 by diver, 15 years ago

Component: Applications- General

I would agree with you 3 years ago, but since it already took 7 years for Haiku, I don't think this would "break" compatibility for that many people, but from consistent POV it would make more point to rename those settings.

comment:10 by diver, 15 years ago

Version: R1 development

Ping. Thoughts?

comment:11 by jonas.kirilla, 15 years ago

A settings class/API could create settings files of a specific type. This filetype could have attributes for the application name, version and the file's purpose, which the app would supply through the class.

To lessen the risk of name conflict the files' names would be based on the application signature, minus the "application/". Hide the filename column if you like and show only the attribute columns.

A single settings file might not be ideal for every application, so one could allow multiple files (adding a filename suffix) or opt for a folder with contents instead, using the same API.

If the class is made to look up the app name, signature and version on its own, then programmer "lazyness" (not supplying values, not having to invent a filename) might actually help create order.

comment:12 by diver, 14 years ago

Version: R1/pre-alpha1R1/Development

comment:13 by waddlesplash, 10 years ago

What's the status of this with the PM merge and all?

comment:14 by humdinger, 10 years ago

I don't think PM has changed anything about this "settings hell". The issue is still the same only 5 years have gone by... :)

FWIW, while we're repackaging apps for haikuports, I'm all for cleaning up where we can and go with "$app_name$_settings".

comment:15 by humdinger, 10 years ago

Description: modified (diff)
Keywords: R2 added
Summary: ~/config/settingsUnify file/folder names in ~/config/settings
Note: See TracTickets for help on using tickets.