[haiku-development] Re: Design question.

  • From: fredrik@xxxxxxxxx
  • To: haiku-development@xxxxxxxxxxxxx
  • Date: Wed, 31 Mar 2021 23:04:55 +0200

2021-03-31 22:13 skrev Alexander G. M. Smith:

Certainly it has the advantage of doing "live" changes better.  The
server knows about the change (via a BMessage sent using the messaging
system) and can both update its operation and save it to a file.
Some part do that today I think, don't remember if its to the server, but it should be.

The alternative system is for the server to monitor the settings file
via the node monitoring facility (sends notification messages for
files you are interested in), and reread it whenever the file is
changed.
Yes thought of that to.

Which is the BeOS / Haiku way?
Sending Message? I asked first ;)

Would the server restrict what went into the settings file, throwing
out data it doesn't recognise?  Is that good?
Good question. The pref app will build the message to send, so it need to be of something that the server knows about. Can be that I but those BMessage stuff in the kitlib and both server and pref can use the same code?

How would it handle previewing changes in the user interface. Consider
the example of changing desktop colours, with an undo to go back to
the original colours.  Would all those changes during editing be
permanent ones, or only permanent when the user hits a Save button?
Really good question. Also what would happend when the server don't run.

How will undo/default work. Will it use a save or change on the fly (think on they fly are BeOS/Haiku way)

Think that settings store old and new value would make it possible to go back.


What should happend when Server are not running, perhaps it should always run?


//Fredrik

Other related posts:

  1. Home
  2. haiku-development
  3. Archive
  4. 03-2021