So I have gotten the rough version of the new MacOS X package working.
Keep in mind that this is a test version, but it should be usable. The
aim is to have everything needed to run Pd in a Pd.app, so that you can
just drag-n-drop to install. Plus, the long term goal is to make Pd
behave like a normal MacOS X app, but there needs to be some biggish
changes for that to happen.
http://at.or.at/hans/pd/installers/
Lots of stuff has been added, including: iemlib pmpd toxy
There is some stuff I would like to add, but need some help from the respective developers:
flext (compile straight from CVS on MacOS X) Gem (compile from the command line) pdp (statically link for all deps) gridflow (help compiling)
So this Pd.app is all set for the AppMain.tcl way of building a Tcl/Tk MacOS X app. In order for that to work, Wish Shell has to launch Pd rather than Pd launching Wish Shell. I started playing around with trying to get that working but didn't get that far. Anyone else working on this or have some pointers?
.hc
http://at.or.at/hans/
Cool,
Unless you object I'll attempt to roll the "pd.app" organization into my 0.38 Pd pre-release (was already intending to try to do this).
cheers Miller
On Sat, Aug 14, 2004 at 12:55:39PM -0400, Hans-Christoph Steiner wrote:
So I have gotten the rough version of the new MacOS X package working.
Keep in mind that this is a test version, but it should be usable. The aim is to have everything needed to run Pd in a Pd.app, so that you can just drag-n-drop to install. Plus, the long term goal is to make Pd behave like a normal MacOS X app, but there needs to be some biggish changes for that to happen.http://at.or.at/hans/pd/installers/
Lots of stuff has been added, including: iemlib pmpd toxy
There is some stuff I would like to add, but need some help from the respective developers:
flext (compile straight from CVS on MacOS X) Gem (compile from the command line) pdp (statically link for all deps) gridflow (help compiling)
So this Pd.app is all set for the AppMain.tcl way of building a Tcl/Tk MacOS X app. In order for that to work, Wish Shell has to launch Pd rather than Pd launching Wish Shell. I started playing around with trying to get that working but didn't get that far. Anyone else working on this or have some pointers?
.hc
http://at.or.at/hans/
No, that would be great. Check out packages/darwin_app from the CVS to
get the files that build this. It still needs work, which I will do
over the next week or two.
It would be really awesome if we could get Pd to use the AppMain.tcl
setup working. The only that AFAIK that needs to happen for this to
work is for Pd to be launched by Wish Shell. Then we could use the
Tcl/Tk standalone Wish Shell package and Pd would truly be entirely
self-contained and would work where ever its located.
I don't know how much would this change would be since I only just
started looking into it. But I would happily continue or even pick up
the pace on my work with the packaging if you would do the Wish
Shell/AppMain.tcl launching Pd.
.hc
On Aug 14, 2004, at 1:06 PM, Miller Puckette wrote:
Cool,
Unless you object I'll attempt to roll the "pd.app" organization into my 0.38 Pd pre-release (was already intending to try to do this).
cheers Miller
On Sat, Aug 14, 2004 at 12:55:39PM -0400, Hans-Christoph Steiner wrote:
So I have gotten the rough version of the new MacOS X package working. Keep in mind that this is a test version, but it should be usable. The aim is to have everything needed to run Pd in a Pd.app, so that you
can just drag-n-drop to install. Plus, the long term goal is to make Pd behave like a normal MacOS X app, but there needs to be some biggish changes for that to happen.http://at.or.at/hans/pd/installers/
Lots of stuff has been added, including: iemlib pmpd toxy
There is some stuff I would like to add, but need some help from the respective developers:
flext (compile straight from CVS on MacOS X) Gem (compile from the command line) pdp (statically link for all deps) gridflow (help compiling)
So this Pd.app is all set for the AppMain.tcl way of building a Tcl/Tk MacOS X app. In order for that to work, Wish Shell has to launch Pd rather than Pd launching Wish Shell. I started playing around with trying to get that working but didn't get that far. Anyone else working on this or have some pointers?
.hc
http://at.or.at/hans/
Using ReBirth is like trying to play an 808 with a long stick. -David Zicarelli
Good, have already made some attempts, will continue...
M
On Sat, Aug 14, 2004 at 07:05:37PM -0400, Hans-Christoph Steiner wrote:
No, that would be great. Check out packages/darwin_app from the CVS to get the files that build this. It still needs work, which I will do over the next week or two.
It would be really awesome if we could get Pd to use the AppMain.tcl setup working. The only that AFAIK that needs to happen for this to work is for Pd to be launched by Wish Shell. Then we could use the Tcl/Tk standalone Wish Shell package and Pd would truly be entirely self-contained and would work where ever its located.
I don't know how much would this change would be since I only just started looking into it. But I would happily continue or even pick up the pace on my work with the packaging if you would do the Wish Shell/AppMain.tcl launching Pd.
.hc
On Aug 14, 2004, at 1:06 PM, Miller Puckette wrote:
Hello,
It would be really awesome if we could get Pd to use the AppMain.tcl setup working. The only that AFAIK that needs to happen for this to work is for Pd to be launched by Wish Shell. Then we could use the Tcl/Tk standalone Wish Shell package and Pd would truly be entirely self-contained and would work where ever its located.
Just downloaded your 0.37.4 .dmg for testing...cool work! thank you.
Just one question: is it normal (I mean do you know of this behaviour as a bug) that on launching pd.app, the tcl/tk window traces mouse movement wrong? As in, the mouse pointer is approximately 100px away from its actual effect; so, if you try to select an object, you find yourself selecting something about 100px below and to the right of where the pointer is.
d
On Aug 17, 2004, at 5:17 AM, David Casal wrote:
Hello,
It would be really awesome if we could get Pd to use the AppMain.tcl
setup working. The only that AFAIK that needs to happen for this to
work is for Pd to be launched by Wish Shell. Then we could use the
Tcl/Tk standalone Wish Shell package and Pd would truly be entirely
self-contained and would work where ever its located.Just downloaded your 0.37.4 .dmg for testing...cool work! thank you.
Just one question: is it normal (I mean do you know of this behaviour
as a bug) that on launching pd.app, the tcl/tk window traces mouse
movement wrong? As in, the mouse pointer is approximately 100px away
from its actual effect; so, if you try to select an object, you find
yourself selecting something about 100px below and to the right of
where the pointer is.
That is a bug I have run into a lot, I am not sure of the source. But
for me, I can get rid of it by restarting Pd. Some patches seem more
prone to having that problem than others. Its an intermittent problem
so its hard to track down, so any info you can gather on what triggers
it or fixes it would be most helpful.
.hc ________________________________________________________________________ ____
Using ReBirth is like trying to play an 808 with a long stick. -David Zicarelli
Hi
Just one question: is it normal (I mean do you know of this behaviour as a bug) that on launching pd.app, the tcl/tk window traces mouse movement wrong? As in, the mouse pointer is approximately 100px away from its actual effect; so, if you try to select an object, you find yourself selecting something about 100px below and to the right of where the pointer is.
That is a bug I have run into a lot, I am not sure of the source. But for me, I can get rid of it by restarting Pd. Some patches seem more prone to having that problem than others. Its an intermittent problem so its hard to track down, so any info you can gather on what triggers it or fixes it would be most helpful.
Yes, I did find restarting helps, but I can't trace where the problem might be.
However, it does look like it happens mostly if one starts PD, the opens a new blank patch. If you open an existing patch right after starting PD, it seems to drop the buggy mouse behaviour.
Hm.
thanks,
d
On Aug 17, 2004, at 11:13 AM, David Casal wrote:
Hi
Just one question: is it normal (I mean do you know of this
behaviour as a bug) that on launching pd.app, the tcl/tk window
traces mouse movement wrong? As in, the mouse pointer is
approximately 100px away from its actual effect; so, if you try to
select an object, you find yourself selecting something about 100px
below and to the right of where the pointer is.That is a bug I have run into a lot, I am not sure of the source.
But for me, I can get rid of it by restarting Pd. Some patches seem
more prone to having that problem than others. Its an intermittent
problem so its hard to track down, so any info you can gather on what
triggers it or fixes it would be most helpful.Yes, I did find restarting helps, but I can't trace where the problem
might be.However, it does look like it happens mostly if one starts PD, the
opens a new blank patch. If you open an existing patch right after
starting PD, it seems to drop the buggy mouse behaviour.
The real coup would be to make a patch that triggers this bug
everytime. Its one of my all time greatest annoyances when using Pd.
I'd love to see it fixed, but I haven't been able to figure out what
triggers it.
.hc
"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away
to benefit those who profit from scarcity."
-John Gilmore
I get this on patches that have objects with negative coordinates... somehow Wish then slides everything down or to the right without telling Pd. I hope to fix this in 0.38 somehow.
cheers Miller
On Tue, Aug 17, 2004 at 10:17:37AM +0100, David Casal wrote:
Hello,
It would be really awesome if we could get Pd to use the AppMain.tcl setup working. The only that AFAIK that needs to happen for this to work is for Pd to be launched by Wish Shell. Then we could use the Tcl/Tk standalone Wish Shell package and Pd would truly be entirely self-contained and would work where ever its located.
Just downloaded your 0.37.4 .dmg for testing...cool work! thank you.
Just one question: is it normal (I mean do you know of this behaviour as a bug) that on launching pd.app, the tcl/tk window traces mouse movement wrong? As in, the mouse pointer is approximately 100px away from its actual effect; so, if you try to select an object, you find yourself selecting something about 100px below and to the right of where the pointer is.
d
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
It would be really awesome if we could get Pd to use the AppMain.tcl setup working. The only that AFAIK that needs to happen for this to work is for Pd to be launched by Wish Shell. Then we could use the Tcl/Tk standalone Wish Shell package and Pd would truly be entirely self-contained and would work where ever its located.
is this fixed already? I think I have it working. the only problem is that there's no console, not sure how to deal with this ...
. g
On Aug 17, 2004, at 1:14 PM, 0001 wrote:
It would be really awesome if we could get Pd to use the AppMain.tcl
setup working. The only that AFAIK that needs to happen for this to
work is for Pd to be launched by Wish Shell. Then we could use the
Tcl/Tk standalone Wish Shell package and Pd would truly be entirely
self-contained and would work where ever its located.is this fixed already? I think I have it working. the only problem is that there's no console, not sure how to deal
with this ...
I haven't seen this fixed, but I'd love to see your copy if you got it
working. Can you post it somewhere? The other issue that you might
have come across is the Help->Documentation menu item not working since
MacOS X hides anything within the .app wrapper.
.hc
"[W]e have invented the technology to eliminate scarcity, but we are
deliberately throwing it away
to benefit those who profit from scarcity."
-John Gilmore
I haven't seen this fixed, but I'd love to see your copy if you got it working. Can you post it somewhere? The other issue that you might have come across is the Help->Documentation menu item not working since MacOS X hides anything within the .app wrapper.
I'm trying to finish the job and throw it into a Wish .app with the tcl / tk frameworks included, but I'm stuck at trying to link pdtcl so that it can be loaded without having the frameworks in /Library
by now it only loads if I link against /Library and keep the frameworks there ...
any hints ?
. g
On Sat, 21 Aug 2004, 0001 wrote:
I haven't seen this fixed, but I'd love to see your copy if you got it working. Can you post it somewhere? The other issue that you might have come across is the Help->Documentation menu item not working since MacOS X hides anything within the .app wrapper.
I'm trying to finish the job and throw it into a Wish .app with the tcl / tk frameworks included, but I'm stuck at trying to link pdtcl so that it can be loaded without having the frameworks in /Library by now it only loads if I link against /Library and keep the frameworks there ... any hints ?
Check whether any *.tcl files from a framework folder get loaded at startup. It's also important to print the error messages, so that Tcl can tell you that the error is actually "bleh.tcl not found" instead of "an error occurred..." or just "Segmentation Fault"....
Mathieu Bouchard http://artengine.ca/matju
It's also important to print the error messages, so that Tcl can tell you that the error is actually "bleh.tcl not found" instead of "an error occurred..." or just "Segmentation Fault"....
well, actually the only way Tcl has to tell me there is any error is happily crashing the wish shell. I'd love to be enlightened about how to avoid this. in fact I think it used to pop up messages before
. g
On Sun, 22 Aug 2004, 0001 wrote:
It's also important to print the error messages, so that Tcl can tell you that the error is actually "bleh.tcl not found" instead of "an error occurred..." or just "Segmentation Fault"....
well, actually the only way Tcl has to tell me there is any error is happily crashing the wish shell. I'd love to be enlightened about how to avoid this. in fact I think it used to pop up messages before
Impd (CVS) has code for printing verbose error messages. I don't recall whether that's in the A2 release. Here's the code:
void tcl_mess(char *s) { int result; result = Tcl_Eval(tk_myinterp, s); if (result != TCL_OK) { if (*tk_myinterp->result) { Tcl_Eval(tk_myinterp, "global errorInfo; " "puts stderr "Tcl Error: $errorInfo""); } } }
And something similar for pdgui_doevalfile...
(Note that t_tkcmd.c is bound to disappear from IMPD at some point...)
Mathieu Bouchard http://artengine.ca/matju
ok, I'll take a look, thanks a lot
. g
El 23/08/2004, a las 9:33, Mathieu Bouchard escribió:
On Sun, 22 Aug 2004, 0001 wrote:
It's also important to print the error messages, so that Tcl can tell you that the error is actually "bleh.tcl not found" instead of "an error occurred..." or just "Segmentation Fault"....
well, actually the only way Tcl has to tell me there is any error is happily crashing the wish shell. I'd love to be enlightened about how to avoid this. in fact I think it used to pop up messages before
Impd (CVS) has code for printing verbose error messages. I don't recall whether that's in the A2 release. Here's the code:
void tcl_mess(char *s) { int result; result = Tcl_Eval(tk_myinterp, s); if (result != TCL_OK) { if (*tk_myinterp->result) { Tcl_Eval(tk_myinterp, "global errorInfo; " "puts stderr "Tcl Error: $errorInfo""); } } }
And something similar for pdgui_doevalfile...
(Note that t_tkcmd.c is bound to disappear from IMPD at some point...)
Mathieu Bouchard http://artengine.ca/matju
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://iem.at/cgi-bin/mailman/listinfo/pd-list
On Aug 21, 2004, at 9:26 AM, 0001 wrote:
I haven't seen this fixed, but I'd love to see your copy if you got
it working. Can you post it somewhere? The other issue that you
might have come across is the Help->Documentation menu item not
working since MacOS X hides anything within the .app wrapper.I'm trying to finish the job and throw it into a Wish .app with the
tcl / tk frameworks included, but I'm stuck at trying to link pdtcl so
that it can be loaded without having the frameworks in /Library
Are you using the standalone Wish Shell version from the Tcl.tk site or
are you rolling your own? Maybe the standalone Wish Shell in combo
with the AppMain.tcl launching Pd would make this job easier.
.hc
Man has survived hitherto because he was too ignorant to know how to
realize his wishes.
Now that he can realize them, he must either change them, or perish.
-William Carlos Williams
hi, I've put a modified version of the test MacOSX application package here:
http://pure-data.info/Members/gerard/pd-0.37.4.dmg
changes:
- moved to the WishKit app package (distributed with tcl / tk BI)
- added -nowish flag to pd
- modified AppMain.tcl and pd.tk to launch pd -nowish and load pdtcl in
the new structure, also completed drag+drop support ;)
- recompiled pdtcl to link with embeded frameworks. For some reason
@executable_path/../Frameworks seems to resolve to inside the Resuorces folder of the package, so I've copied the Frameworks folder there as well as a hackaround.
- added some experimental documentation menu patches.
the biggest problem is that it lacks the console. some feedback is
available at Console.ap, but not the [print] messages. solutions that
come to mind are the impd console or whatever tigital did with pd++
for going to Console.app (stderr). or maybe the Wish Shell's own
console could be used.
one effect of decoupling is that if you run into problems, you may need to manually kill the pd process. maybe the tcl code could do this at startup. In general, the startup process may need some improvements.
...
gerard
Very nice! Real progress! I would be great if you would work out of
the CVS and add some instructions to the README. All of the files for
creating the Pd.app are in packages/darwin_app.
On Aug 22, 2004, at 8:20 AM, 0001 wrote:
hi, I've put a modified version of the test MacOSX application package
here:http://pure-data.info/Members/gerard/pd-0.37.4.dmg
changes:
- moved to the WishKit app package (distributed with tcl / tk BI)
- added -nowish flag to pd
- modified AppMain.tcl and pd.tk to launch pd -nowish and load pdtcl
in the new structure, also completed drag+drop support ;)
Not only does dragging and dropping a .pd file onto Pd.app work, but
also double-clicking files in the Finder. It will either open the file
in the existing Pd.app, or launch Pd.app if it isn't running.
Aaahhhh... finally!
- recompiled pdtcl to link with embeded frameworks. For some reason
@executable_path/../Frameworks seems to resolve to inside the
Resuorces folder of the package, so I've copied the Frameworks folder
there as well as a hackaround.
It would be good to have this all done from
packages/darwin_app/Makefile, since that's the Makefile that assembles
the Pd.app that I created.
- added some experimental documentation menu patches.
Help->Pure Documentation needs to be figured out. The patches that are
included in the Pd.app are a good workaround, but I think in the long
run, we should figure out something that would be easier to maintain.
But perhaps having all of the docs put into a navigatible system of
patches would be a good idea, kind of like Pd hypertext. But it would
add to the amount of maintenance that would need to be done.
the biggest problem is that it lacks the console. some feedback is
available at Console.ap, but not the [print] messages. solutions
that come to mind are the impd console or whatever tigital did with
pd++ for going to Console.app (stderr). or maybe the Wish Shell's own
console could be used.one effect of decoupling is that if you run into problems, you may
need to manually kill the pd process. maybe the tcl code could do this at startup. In general, the startup
process may need some improvements.
This shouldn't be too hard to do. Each instance of Pd.app (Wish
Shell.app wrapper for the pd process) could keep track of the pd
-nowish PID, then make sure to kill it when it exits. The Tcl
exceptions could be used to catch crashes, etc. (if they are anything
like Java exceptions, I haven't really looked into them).
.hc
"If nature has made any one thing less susceptible than all others of
exclusive property, it is the action of the thinking power called an
idea, which an individual may exclusively possess as long as he keeps
it to himself; but the moment it is divulged, it forces itself into the
possession of everyone, and the receiver cannot dispossess himself of
it."
- Thomas Jefferson
would be great if you would work out of the CVS and add some instructions to the README. All of the files for creating the Pd.app are in packages/darwin_app.
not sure I understand that right. I can post a patch for -nowish, all the rest of the code is inside the package.
It would be good to have this all done from packages/darwin_app/Makefile, since that's the Makefile that assembles the Pd.app that I created.
it shouldn't be too difficult, you just need to choose a reference Tcl / Tk installation that includes a package with the embedded frameworks.
Help->Pure Documentation needs to be figured out. The patches that are included in the Pd.app are a good workaround, but I think in the long run, we should figure out something that would be easier to maintain. But perhaps having all of the docs put into a navigatible system of patches would be a good idea, kind of like Pd hypertext.
But it would add to the amount of maintenance that would need to be done.
actually those ones are in part automated with a shell script. but I admit it's more of a workaround for now. I think I've seen something similar in jMax
This shouldn't be too hard to do. Each instance of Pd.app (Wish Shell.app wrapper for the pd process) could keep track of the pd -nowish PID, then make sure to kill it when it exits.
well currently it quits the (sub)process, the problem is when it crashes.
The Tcl exceptions could be used to catch crashes, etc. (if they are anything like Java exceptions, I haven't really looked into them).
is it included as standard? that'd be great
. g
On Aug 22, 2004, at 6:27 PM, 0001 wrote:
would be great if you would work out of the CVS and add some
instructions to the README. All of the files for creating the Pd.app
are in packages/darwin_app.not sure I understand that right. I can post a patch for -nowish, all
the rest of the code is inside the package.
For example, your AppMain.tcl and the shell script that you use to
create the help nav: these should be checked into packages/darwin_app
in the Pd CVS. Any files that are needed to generate this package
should be checked into packages/darwin_app. Then others will be able
to build the package themselves and even develop it further, fix bugs,
etc.
Then, if all of the files are in CVS, a Makefile can assemble the whole
package automatically. This will make future releases much, much
easier.
.hc
It would be good to have this all done from
packages/darwin_app/Makefile, since that's the Makefile that
assembles the Pd.app that I created.it shouldn't be too difficult, you just need to choose a reference Tcl
/ Tk installation that includes a package with the embedded
frameworks.Help->Pure Documentation needs to be figured out. The patches that
are included in the Pd.app are a good workaround, but I think in the
long run, we should figure out something that would be easier to
maintain. But perhaps having all of the docs put into a navigatible
system of patches would be a good idea, kind of like Pd hypertext.
But it would add to the amount of maintenance that would need to be
done.actually those ones are in part automated with a shell script. but I
admit it's more of a workaround for now. I think I've seen something
similar in jMaxThis shouldn't be too hard to do. Each instance of Pd.app (Wish
Shell.app wrapper for the pd process) could keep track of the pd
-nowish PID, then make sure to kill it when it exits.well currently it quits the (sub)process, the problem is when it
crashes.The Tcl exceptions could be used to catch crashes, etc. (if they are
anything like Java exceptions, I haven't really looked into them).is it included as standard? that'd be great
. g
There is no way to peace, peace is the way.
-A.J. Muste
hi Hans,
is there any guidelines for compiling pdp2gem/ gem2pdp in macosx?
Thanks
slimboyfatboyslim http://www.slimboyfatboyslim.org
於 23 Aug 04 11:59 AM 時，Hans-Christoph Steiner 提到：
On Aug 22, 2004, at 6:27 PM, 0001 wrote:
would be great if you would work out of the CVS and add some
instructions to the README. All of the files for creating the
Pd.app are in packages/darwin_app.not sure I understand that right. I can post a patch for -nowish, all
the rest of the code is inside the package.For example, your AppMain.tcl and the shell script that you use to
create the help nav: these should be checked into packages/darwin_app
in the Pd CVS. Any files that are needed to generate this package
should be checked into packages/darwin_app. Then others will be able
to build the package themselves and even develop it further, fix bugs,
etc.Then, if all of the files are in CVS, a Makefile can assemble the
whole package automatically. This will make future releases much,
much easier..hc
It would be good to have this all done from
packages/darwin_app/Makefile, since that's the Makefile that
assembles the Pd.app that I created.it shouldn't be too difficult, you just need to choose a reference
Tcl / Tk installation that includes a package with the embedded
frameworks.Help->Pure Documentation needs to be figured out. The patches that
are included in the Pd.app are a good workaround, but I think in the
long run, we should figure out something that would be easier to
maintain. But perhaps having all of the docs put into a navigatible
system of patches would be a good idea, kind of like Pd hypertext.
But it would add to the amount of maintenance that would need to be
done.actually those ones are in part automated with a shell script. but I
admit it's more of a workaround for now. I think I've seen something
similar in jMaxThis shouldn't be too hard to do. Each instance of Pd.app (Wish
Shell.app wrapper for the pd process) could keep track of the pd
-nowish PID, then make sure to kill it when it exits.well currently it quits the (sub)process, the problem is when it
crashes.The Tcl exceptions could be used to catch crashes, etc. (if they
are anything like Java exceptions, I haven't really looked into
them).is it included as standard? that'd be great
. g
There is no way to peace, peace is the way. -A.J. Muste
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://iem.at/cgi-bin/mailman/listinfo/pd-list
On Aug 22, 2004, at 6:40 PM, 0001 wrote:
Help->Pure Documentation needs to be figured out.
I've also considered making a script to change all of the help patches
to a 10 font size. this one looks good on osx , but I don't know what
fits on other platforms.
10 point fonts work well on Windows and X11 (GNU/Linux). Windows needs
the 12 point fonts. Anyone know how hard it would be to bump up the
font size Pd uses in Windows so that the font size is closer to the
same on all the platforms? This would make writing help patches much,
much easier.
.hc
There is no way to peace, peace is the way.
-A.J. Muste
On Sun, 22 Aug 2004, Hans-Christoph Steiner wrote:
On Aug 22, 2004, at 6:40 PM, 0001 wrote:
Help->Pure Documentation needs to be figured out.
I've also considered making a script to change all of the help patches
to a 10 font size. this one looks good on osx , but I don't know what
fits on other platforms.10 point fonts work well on Windows and X11 (GNU/Linux). Windows needs
the 12 point fonts. Anyone know how hard it would be to bump up the
font size Pd uses in Windows so that the font size is closer to the
same on all the platforms? This would make writing help patches much,
much easier.
As said previously: use pixel sizes. In Tk you indicate that by using negative values.
Mathieu Bouchard http://artengine.ca/matju
Mathieu Bouchard wrote:
On Sun, 22 Aug 2004, Hans-Christoph Steiner wrote:
On Aug 22, 2004, at 6:40 PM, 0001 wrote:
Help->Pure Documentation needs to be figured out.
I've also considered making a script to change all of the help patches
to a 10 font size. this one looks good on osx , but I don't know what
fits on other platforms.10 point fonts work well on Windows and X11 (GNU/Linux). Windows needs
the 12 point fonts. Anyone know how hard it would be to bump up the
font size Pd uses in Windows so that the font size is closer to the
same on all the platforms? This would make writing help patches much,
much easier.As said previously: use pixel sizes. In Tk you indicate that by using negative values.
dear god yes. having my GOP patches be truely portable would be so great.
Yep. I'm going to try this for 0.38.
cheers Miller
On Mon, Aug 23, 2004 at 12:24:28AM -0400, Mathieu Bouchard wrote:
On Sun, 22 Aug 2004, Hans-Christoph Steiner wrote:
On Aug 22, 2004, at 6:40 PM, 0001 wrote:
Help->Pure Documentation needs to be figured out.
I've also considered making a script to change all of the help patches
to a 10 font size. this one looks good on osx , but I don't know what
fits on other platforms.10 point fonts work well on Windows and X11 (GNU/Linux). Windows needs
the 12 point fonts. Anyone know how hard it would be to bump up the
font size Pd uses in Windows so that the font size is closer to the
same on all the platforms? This would make writing help patches much,
much easier.As said previously: use pixel sizes. In Tk you indicate that by using negative values.
Mathieu Bouchard http://artengine.ca/matju
yet one more upload. better startup and jackosx support.
. g
On Aug 31, 2004, at 6:27 PM, 0001 wrote:
yet one more upload. better startup and jackosx support.
...I like the new icon, but get the following error on startup:
dyld: ./pd can't open library: /Library/Frameworks/Tk.framework/Versions/8.4/Tk (No such file or directory, errno = 2)
...this is of course due to the fact that I'm using tcl/tk8.5a in that place...but I assumed that since this pd.app package includes the frameworks (or two copies), that it'd look there first?
...sorry I haven't been able to help out much more than bug reports so far :=)
james
For some reason, I was able to get pdtcl to find frameworks within the actual App all right. Probably because I moved all the sources into the app and compiled Pd there. I'm stuck getting Wish to fork Pd correctly though, hope to figure that out 'real soon'.
cheers Miller
On Sat, Aug 21, 2004 at 03:26:41PM +0200, 0001 wrote:
I haven't seen this fixed, but I'd love to see your copy if you got it working. Can you post it somewhere? The other issue that you might have come across is the Help->Documentation menu item not working since MacOS X hides anything within the .app wrapper.
I'm trying to finish the job and throw it into a Wish .app with the tcl / tk frameworks included, but I'm stuck at trying to link pdtcl so that it can be loaded without having the frameworks in /Library
by now it only loads if I link against /Library and keep the frameworks there ...
any hints ?
. g
On Aug 14, 2004, at 12:55 PM, Hans-Christoph Steiner wrote:
So I have gotten the rough version of the new MacOS X package working. Keep in mind that this is a test version, but it should be usable. The aim is to have everything needed to run Pd in a Pd.app, so that you can just drag-n-drop to install. Plus, the long term goal is to make Pd behave like a normal MacOS X app, but there needs to be some biggish changes for that to happen.
...drat...just tried it, and I get the following at console:
/ Applications automount Applications (Mac OS 9) bin Desktop DB cores Desktop DF dev Desktop Folder etc Developer mach Library mach.sym Network mach_kernel System private System Folder sbin TheVolumeSettingsFolder sw User Guides And Information tmp Users usr Volumes var 2004-08-17 23:15:31.503 open[760] No such file: /Applications/Pd.app/Contents/Resources/Pd.term
...sure enough, I check the app package and it has a file Pd.term in the correct place...back to command line!
jamie
On Aug 17, 2004, at 11:18 PM, James Tittle II wrote:
On Aug 14, 2004, at 12:55 PM, Hans-Christoph Steiner wrote:
So I have gotten the rough version of the new MacOS X package working. Keep in mind that this is a test version, but it should be usable. The aim is to have everything needed to run Pd in a Pd.app, so that you can just drag-n-drop to install. Plus, the long term goal is to make Pd behave like a normal MacOS X app, but there needs to be some biggish changes for that to happen.
...drat...just tried it, and I get the following at console:
/ Applications automount Applications (Mac OS 9) bin Desktop DB cores Desktop DF dev Desktop Folder etc Developer mach Library mach.sym Network mach_kernel System private System Folder sbin TheVolumeSettingsFolder sw User Guides And Information tmp Users usr Volumes var 2004-08-17 23:15:31.503 open[760] No such file: /Applications/Pd.app/Contents/Resources/Pd.term
...sure enough, I check the app package and it has a file Pd.term in the correct place...back to command line!
Yeah, this is a kludge until we get the AppMain.tcl thing working. Did move the Pd.app to your /Applications folder? What does this show you:
ls -l /Applications/Pd.app/Contents/Resources/Pd.term
.hc
hey hans!
On Aug 20, 2004, at 1:45 AM, Hans-Christoph Steiner wrote:
Yeah, this is a kludge until we get the AppMain.tcl thing working.
Did move the Pd.app to your /Applications folder? What does this show you:ls -l /Applications/Pd.app/Contents/Resources/Pd.term
tiggity:~ tigital$ ls -l /Applications/Pd.app/Contents/Resources/Pd.term ls: /Applications/Pd.app/Contents/Resources/Pd.term: No such file or directory
...wonder where it went, because I can see it there via finder? Also check ls -la on my /Applications directory, and it doesn't even show Pd.app! Weird...
jamie
-
0001 -
David Casal -
Hans-Christoph Steiner -
James Tittle II -
Josh Steiner -
Mathieu Bouchard -
Miller Puckette -
slimboyfatboyslim