Hi all,
there is a way to put a .pdrc inside a standalone PD<n_version>.app ?
I whould send some command line option to pd (-nogui and -open) in a no_user_dependent way.
thank you
-- Lazzaro
Nope, not really, unless you recompile. I think the easiest thing to
do is to create a org.puredata.pd.plist, which is the file that the
preferences system saves to. Then you instruct users to copy that file
to ~/Library/Preferences.
I've started doing this with my OSX package, and the .pdrc is
deprecated anyway.
.hc
On Sep 8, 2005, at 6:23 PM, Lazzaro Ciccolella wrote:
Hi all,
there is a way to put a .pdrc inside a standalone PD<n_version>.app ?
I whould send some command line option to pd (-nogui and -open) in a no_user_dependent way.
thank you
-- Lazzaro
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
If you are not part of the solution, you are part of the problem.
- Eldridge Cleaver
On 15 Sep 2005, at 15:52, Hans-Christoph Steiner wrote:
Nope, not really, unless you recompile. I think the easiest thing to do is to create a org.puredata.pd.plist, which is the file that the preferences system saves to. Then you instruct users to copy that file to ~/Library/Preferences.
I've started doing this with my OSX package, and the .pdrc is deprecated anyway.
Deprecated how? Sorry, but I seemed to have missed this...
d
-- # David Plans Casal
problem.each { |day| assert_nil(spoon) }
Deprecated as is no longer supported and may eventually be removed.
Check the archives, Miller's been talking about it for a while in
relation to the new preferences system.
.hc
On Sep 15, 2005, at 5:06 PM, David Plans Casal wrote:
On 15 Sep 2005, at 15:52, Hans-Christoph Steiner wrote:
Nope, not really, unless you recompile. I think the easiest thing to
do is to create a org.puredata.pd.plist, which is the file that the
preferences system saves to. Then you instruct users to copy that
file to ~/Library/Preferences.I've started doing this with my OSX package, and the .pdrc is
deprecated anyway.Deprecated how? Sorry, but I seemed to have missed this...
d
-- # David Plans Casal
problem.each { |day| assert_nil(spoon) }
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
Using ReBirth is like trying to play an 808 with a long stick.
-David Zicarelli
On Sun, 2 Oct 2005, Hans-Christoph Steiner wrote:
Deprecated as is no longer supported and may eventually be removed. Check the archives, Miller's been talking about it for a while in relation to the new preferences system.
Well, if the replacement isn't a complete replacement, then no matter how often Miller (and others) shouts "deprecated" at it, in the facts it really isn't.
Miller promises the replacement will be ready before 2010.
Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju Freelance Digital Arts Engineer, Montréal QC Canada
Am 15.09.2005 um 16:52 schrieb Hans-Christoph Steiner:
I think the easiest thing to do is to create a
org.puredata.pd.plist, which is the file that the preferences
system saves to. Then you instruct users to copy that file to ~/ Library/Preferences.
there is a command line utility for writing preference values:
defaults. (see man defaults). for quickly inspect what is contained
in the pd prefs just type the following command into terminal:
defaults read org.puredata.pd
package distributors could then distribute a script which set the
appropriate defaults instead of providing a plist which will
overwrite the preferences of the user
On Oct 3, 2005, at 6:53 AM, Lorenz Schori wrote:
Am 15.09.2005 um 16:52 schrieb Hans-Christoph Steiner:
I think the easiest thing to do is to create a org.puredata.pd.plist,
which is the file that the preferences system saves to. Then you
instruct users to copy that file to ~/Library/Preferences.there is a command line utility for writing preference values:
defaults. (see man defaults). for quickly inspect what is contained in
the pd prefs just type the following command into terminal:defaults read org.puredata.pd
package distributors could then distribute a script which set the
appropriate defaults instead of providing a plist which will overwrite
the preferences of the user
Thanks, that's a good idea. I'll have to try that. Its on the TODO
list.
.hc
"Terrorism is not an enemy. It cannot be defeated. It's a tactic.
It's about as sensible to say we declare war on night attacks and
expect we're going to win that war. We're not going to win the war on
terrorism."
-
retired U.S. Army general, William Odom
hi list,
how to handle it if one may want to keep different properties for
different instances of pd?
e.g. one pd instance for sound, and one for gem to avoid audio
glitches; one instance has to have libaries to load, the other one
should run in -nogui....
how do you solve this with just one org.puredata.pd.plist all of the
instances of pd are refering to?
m
Am 07.10.2005 um 19:43 schrieb Hans-Christoph Steiner:
On Oct 3, 2005, at 6:53 AM, Lorenz Schori wrote:
Am 15.09.2005 um 16:52 schrieb Hans-Christoph Steiner:
I think the easiest thing to do is to create a
org.puredata.pd.plist, which is the file that the preferences
system saves to. Then you instruct users to copy that file to ~/ Library/Preferences.there is a command line utility for writing preference values:
defaults. (see man defaults). for quickly inspect what is
contained in the pd prefs just type the following command into
terminal:defaults read org.puredata.pd
package distributors could then distribute a script which set the
appropriate defaults instead of providing a plist which will
overwrite the preferences of the userThanks, that's a good idea. I'll have to try that. Its on the
TODO list..hc
"Terrorism is not an enemy. It cannot be defeated. It's a
tactic. It's about as sensible to say we declare war on night
attacks and expect we're going to win that war. We're not going to
win the war on terrorism." -
retired U.S. Army general, William Odom
I use a script which saves and restores different config files. Its in
CVS:
http://cvs.sourceforge.net/viewcvs.py/pure-data/scripts/config- switcher.sh?rev=1.2&view=log
.hc
On Oct 8, 2005, at 9:37 AM, Max Neupert wrote:
hi list,
how to handle it if one may want to keep different properties for
different instances of pd?e.g. one pd instance for sound, and one for gem to avoid audio
glitches; one instance has to have libaries to load, the other one
should run in -nogui....how do you solve this with just one org.puredata.pd.plist all of the
instances of pd are refering to?m
Am 07.10.2005 um 19:43 schrieb Hans-Christoph Steiner:
On Oct 3, 2005, at 6:53 AM, Lorenz Schori wrote:
Am 15.09.2005 um 16:52 schrieb Hans-Christoph Steiner:
I think the easiest thing to do is to create a
org.puredata.pd.plist, which is the file that the preferences
system saves to. Then you instruct users to copy that file to
~/Library/Preferences.there is a command line utility for writing preference values:
defaults. (see man defaults). for quickly inspect what is contained
in the pd prefs just type the following command into terminal:defaults read org.puredata.pd
package distributors could then distribute a script which set the
appropriate defaults instead of providing a plist which will
overwrite the preferences of the userThanks, that's a good idea. I'll have to try that. Its on the TODO
list..hc
"Terrorism is not an enemy. It cannot be defeated. It's a tactic.
It's about as sensible to say we declare war on night attacks and
expect we're going to win that war. We're not going to win the war
on terrorism." -
retired U.S. Army general, William Odom
News is what people want to keep hidden and everything else is
publicity.
- Bill Moyers
does that work even if one has to run two instances simultanuously?
max.
Am 11.10.2005 um 06:14 schrieb Hans-Christoph Steiner:
I use a script which saves and restores different config files.
Its in CVS:http://cvs.sourceforge.net/viewcvs.py/pure-data/scripts/config- switcher.sh?rev=1.2&view=log
.hc
On Oct 8, 2005, at 9:37 AM, Max Neupert wrote:
hi list,
how to handle it if one may want to keep different properties for
different instances of pd?e.g. one pd instance for sound, and one for gem to avoid audio
glitches; one instance has to have libaries to load, the other one
should run in -nogui....how do you solve this with just one org.puredata.pd.plist all of
the instances of pd are refering to?m
Am 07.10.2005 um 19:43 schrieb Hans-Christoph Steiner:
On Oct 3, 2005, at 6:53 AM, Lorenz Schori wrote:
Am 15.09.2005 um 16:52 schrieb Hans-Christoph Steiner:
I think the easiest thing to do is to create a
org.puredata.pd.plist, which is the file that the preferences
system saves to. Then you instruct users to copy that file to
~/Library/Preferences.there is a command line utility for writing preference values:
defaults. (see man defaults). for quickly inspect what is
contained in the pd prefs just type the following command into
terminal:defaults read org.puredata.pd
package distributors could then distribute a script which set
the appropriate defaults instead of providing a plist which will
overwrite the preferences of the userThanks, that's a good idea. I'll have to try that. Its on the
TODO list..hc
"Terrorism is not an enemy. It cannot be defeated. It's a
tactic. It's about as sensible to say we declare war on night
attacks and expect we're going to win that war. We're not going
to win the war on terrorism."
- retired U.S. Army general, William Odom
News is what people want to keep hidden and everything else is
publicity.- Bill Moyers
Max Neupert wrote:
does that work even if one has to run two instances simultanuously?
in theory it shouldn't make any problems with several instances: pd reads the configuration-information only at startup, so as soon as an instance is running, you can throw away your files/registry and/or reboot your computer.
mfg.asd.r IOhannes