What are the practical problems with using the current
format for the Pd preferences file under Linux?
I don't know, I'm a windows user, and think that the linux .pdsettings will be a better substitute for the actual windows method of writing in the registry. And think that it should live on the pd/bin dir & not in a user dir. to disallow sharing prefs. on multiple installations. (Pd, Purr-Data, PsVST)
If is needed to hold different fonts-metrics there could be a separete file just for that, or it can be stored in the actual file format.
fm1: 5 11 fm2: 6 13 fm3: 7 16 fm4: 10 19 fm5: 14 29 fm6: 22 44
Mensaje telepatico asistido por maquinas.
From: Jonathan Wilkes jancsika@yahoo.com Sent: Monday, February 20, 2017 1:35 AM To: Lucas Cordiviola; pd-list@lists.iem.at Subject: Re: [PD] (wip) Preferences file.
Benefit: there would be a single preferences file format shared among all platforms.
Cost:
preferences is OSX, and Pd relies on its proprietary, non-portable tool in order to read and save this file. So it would be necessary to write an XML parser for reading and writing in Pd, or bring in an XML library as a dependency.
use them as a guide. For example, the Pd message parser splits tokens on spaces-- the XML preferences file below doesn't fit that pattern-- the pd parser would interpret that first line as a single symbol atom.
in Pd for reading/writing preference files. That would be thrown out to create a newer one that is more difficult to implement.
the power that XML would have provided. (For example, nested tags to make the values in "fontmetrics" self documenting.)
What are the practical problems with using the current format for the Pd preferences file under Linux?
-Jonathan
<rate>44100</rate>
<flags>-font-weight normal</flags>
<fontmetrics> 5 11 6 13 7 16 10 19 14 29 22 44 </fontmetrics>
Mensaje telepatico asistido por maquinas.