On 01.05.2009, at 00:32, Jerome Peace wrote:
>
> Hi all,
>
> Problem: You develop an application in a project under one set of
> circumstances.
> Save the project out to disk.
> Them want to load it back in another entirely different set of
> circumstances.
>
> Some Browser or morph or something saved with the project doesn't
> want to load back in.*
>
>
> The story I would like to see implemented is:
>
> In addition to the option of loading the project
> 1) can I opt instead to load just the code associated with the
> project into a code browser. And/Or
> 2) save the code associated with the project as a fileout to the
> disk w/o loading the project at all.
>
> (Then filelist would allow the many things it knows to do with filed
> out code.)
>
> This story is strictly for .pr files. I know to generally save out a
> projects change set first before saving a project. I am looking for
> a way to ease things, particularly when I forget the extra steps.
>
>
> Yours in curiosity and service, --Jerome Peace
You can unzip the .pr file. There is another .pr file inside. If it
starts with 'SPRJ', chop of the signature (first 44 bytes). Then
gunzip the rest. You get an uncompressed .pr file. In the beginning of
that, you have the project changeset.
- Bert -