[PD] Pd 0.37.4 app test release for MacOS X

[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 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
>

________________________________________________________________________ 
____

                     There is no way to peace, peace is the way.
										-A.J. Muste