Ask / Submit
4

Preferred way of implementing application settings?

asked 2014-01-15 15:35:04 +0200

fercen gravatar image

updated 2014-07-25 11:49:12 +0200

jiit gravatar image

I have seen no user-created application implement its settings by utilizing the Sailfish settings menu. I'm afraid people either aren't really aware of its existence (easy to forget (which ironically is good)) or deem it an unnecessary way of complicating things.

I reckon the very essence of the ideas behind Sailfish is that most frequently used applications and features are presented as simply and with as few obstacles as possible. One of the ways to implement and make use of this idea is to separate the (less frequently needed) configuration features from those that make the application into what it is. This keeps the pulley menus tidier etc. and when configuration is needed, the user will know where to look since it's all in the same place for every application.

It's a new approach as is dropping the buttons and thus needs some getting used to, but both are necessary for the simple usage of the OS.

So what I'm hoping is that the design guidelines for Sailfish applications would disclose the preferred approach to implementing application settings since it's a fairly fundamental feature of the platform. Perhaps it would help to emphasize this idea while the whole ecosystem is still new and developing fast.

Or do people generally find separated app settings an undesired feature? Discuss.

edit retag flag offensive close delete

Comments

1

"I have seen no user-created application implement its settings by utilizing the Sailfish settings menu.". That's because there is currently no way to do it.

koudi ( 2014-01-15 15:44:19 +0200 )edit

I think developers would love to be able to do that, but at least for now there is no way to do this and publish on the Harbour. But actually, the information on how to do this is available on the sailfishos-devel mailing list. Let's hope the permission problem holding this back gets sorted out soon.

mikelima ( 2014-01-15 15:48:08 +0200 )edit

2 Answers

Sort by » oldest newest most voted
1

answered 2014-01-15 15:56:36 +0200

rainisto gravatar image

updated 2014-01-15 15:57:30 +0200

Sailfish settings menu is currently reserved for Jolla applications only (because it has privileged group access that cant be granted to 3rd party applications).

So currently preferred way for settings is by using QSettings.

edit flag offensive delete publish link more

Comments

1

Actually, as a developer, I am using QSettings... Still I would love to have settings page for my application be a page in the settings application, instead of calling them from the PullDownMenu.

mikelima ( 2014-01-15 17:01:49 +0200 )edit
0

answered 2014-01-15 19:32:47 +0200

foss4ever gravatar image

updated 2014-01-17 00:27:21 +0200

This question seems to be a duplicate of this: https://together.jolla.com/question/13464/why-are-native-app-developers-not-using-settings-apps/

Should we close this, and continue discussion abt the topic there?

edit flag offensive delete publish link more

Comments

It seems to me like that question is more straightforward and technical and already dealt with to the extent possible for the time being. Here I was hoping to discuss opinions about the feature from user and Sailfish design principles point of view.

fercen ( 2014-01-15 20:34:52 +0200 )edit

The question there is not technical but the answer is (cause developers currently can't use System settings) irrespective of any best practises..

foss4ever ( 2014-01-15 20:47:07 +0200 )edit
Login/Signup to Answer

Question tools

Follow
3 followers

Stats

Asked: 2014-01-15 15:35:04 +0200

Seen: 417 times

Last updated: Jan 17 '14