Smalltalk › Cincom › VisualWorks

[vwnc] remove dependencies on pst sources

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

10 messages Options

Steve Whitson

[vwnc] remove dependencies on pst sources

Hi All,

Does anyone have any ideas how to go about removing the dependencies on
the .pst source pointers. I would like the .pst sources to be somehow
condensed onto the .sou file.

We have been able to publish all the dependent parcels into store, and
reload them during out image builds. But now I would like to go a step
further and remove the source dependencies. The goal here is to end up
with a image (image.im, image.sou, image.cha) file set which needs only
the object engine. All code contained in the image should be present
for browsing.

We already do the condenseChangesOntoSources which creates a .sou file
that matches our resulting image name. This is convenient, but we want
the .sou file to also contain all the other remaining (.pst) sources too
(such as StoreBase.pst).

The method SourceFileManager>>newBaseSourceFileWithoutParcels: looks
like it might do the trick... although it doesn't get the whole job
done. The classes get pushed into the .sou file, but not the methods
(that's all I've reviewed thus far).

Any help is greatly appreciated. Thanks much,
-Steve
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Reinout Heeck

Re: [vwnc] remove dependencies on pst sources

On Oct 16, 2008, at 7:00 PM, Steve Whitson wrote:

> Hi All,
>
> Does anyone have any ideas how to go about removing the dependencies
> on
> the .pst source pointers. I would like the .pst sources to be somehow
> condensed onto the .sou file.
>

Have tried doing it the silly way yet?

As in after loading the parcels do a file-in of their pst files once
more....

R
-

> We have been able to publish all the dependent parcels into store, and
> reload them during out image builds. But now I would like to go a
> step
> further and remove the source dependencies. The goal here is to end
> up
> with a image (image.im, image.sou, image.cha) file set which needs
> only
> the object engine. All code contained in the image should be present
> for browsing.
>
> We already do the condenseChangesOntoSources which creates a .sou file
> that matches our resulting image name. This is convenient, but we
> want
> the .sou file to also contain all the other remaining (.pst) sources
> too
> (such as StoreBase.pst).
>
> The method SourceFileManager>>newBaseSourceFileWithoutParcels: looks
> like it might do the trick... although it doesn't get the whole job
> done. The classes get pushed into the .sou file, but not the methods
> (that's all I've reviewed thus far).
>
> Any help is greatly appreciated. Thanks much,
> -Steve
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Charles Adams

Re: [vwnc] remove dependencies on pst sources

If Steve will allow me, I'd like to add some explanation.

Reinout, this would be the opposite of what we want to accomplish.

We publish most of the parcels we get with the VW release. We want our
images to reference the published code, not the parcel. This would allow us
to reduce the parcels list in Settings->System->Source->Source Files.

So far, we've been unable to rid ourselves of this dependency. I have found
though that if I reconcile the package with Store, then reload it, the
source winds up in my changes file. From there I can push it into a .sou.
And, through some as yet undiscovered magical incantation, I can then trim
my Sources Files of the unnecessary parcel link.

That's why Steve latched onto
SourceFileManager>>newBaseSourceFileWithoutParcels: as a promising
mechanism. But we don't understand it.

Our idea of a perfect image is one in which all of the source is in a .sou
file. Thus, we can deliver to our customers a .im, a .sou, and an empty
.cha. Then the only thing the customer needs at that point is an executable
and a Store library.

It is important that every line of code be under CM control.

Charlie

----- Original Message -----
From: "Reinout Heeck" <[hidden email]>
To: "vwnc-list list" <[hidden email]>
Sent: Thursday, October 16, 2008 3:41 PM
Subject: Re: [vwnc] remove dependencies on pst sources

> On Oct 16, 2008, at 7:00 PM, Steve Whitson wrote:
>
>> Hi All,
>>
>> Does anyone have any ideas how to go about removing the dependencies
>> on
>> the .pst source pointers. I would like the .pst sources to be somehow
>> condensed onto the .sou file.
>>
>
>
>
> Have tried doing it the silly way yet?
>
> As in after loading the parcels do a file-in of their pst files once
> more....
>
> R
> -
>
>
>> We have been able to publish all the dependent parcels into store, and
>> reload them during out image builds. But now I would like to go a
>> step
>> further and remove the source dependencies. The goal here is to end
>> up
>> with a image (image.im, image.sou, image.cha) file set which needs
>> only
>> the object engine. All code contained in the image should be present
>> for browsing.
>>
>> We already do the condenseChangesOntoSources which creates a .sou file
>> that matches our resulting image name. This is convenient, but we
>> want
>> the .sou file to also contain all the other remaining (.pst) sources
>> too
>> (such as StoreBase.pst).
>>
>> The method SourceFileManager>>newBaseSourceFileWithoutParcels: looks
>> like it might do the trick... although it doesn't get the whole job
>> done. The classes get pushed into the .sou file, but not the methods
>> (that's all I've reviewed thus far).
>>
>> Any help is greatly appreciated. Thanks much,
>> -Steve
>> _______________________________________________
>> vwnc mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>>
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Terry Raymond

Re: [vwnc] remove dependencies on pst sources

In reply to this post by Steve Whitson

This is what we do,

Refactory.Browser.BrowserNavigator

moveSourceToChangesFile

<menuItem: #(#MoveSourceToChangesFile 'Move source to changes')
nameKey: #MoveSourceToChangesFile
enablement: #isParcelSelected
indication: nil
menu: #(#parcelMenu )
position: 20.3>
^self parcel unloadSource

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI 02878
(401) 624-4517 [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Steve Whitson
> Sent: Thursday, October 16, 2008 1:00 PM
> To: [hidden email]
> Subject: [vwnc] remove dependencies on pst sources
>
> Hi All,
>
> Does anyone have any ideas how to go about removing the dependencies on
> the .pst source pointers. I would like the .pst sources to be somehow
> condensed onto the .sou file.
>
> We have been able to publish all the dependent parcels into store, and
> reload them during out image builds. But now I would like to go a step
> further and remove the source dependencies. The goal here is to end up
> with a image (image.im, image.sou, image.cha) file set which needs only
> the object engine. All code contained in the image should be present
> for browsing.
>
> We already do the condenseChangesOntoSources which creates a .sou file
> that matches our resulting image name. This is convenient, but we want
> the .sou file to also contain all the other remaining (.pst) sources too
> (such as StoreBase.pst).
>
> The method SourceFileManager>>newBaseSourceFileWithoutParcels: looks
> like it might do the trick... although it doesn't get the whole job
> done. The classes get pushed into the .sou file, but not the methods
> (that's all I've reviewed thus far).
>
> Any help is greatly appreciated. Thanks much,
> -Steve
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Charles Adams

Re: [vwnc] remove dependencies on pst sources

(I'm using a 7.4 image, but the method is there and I suspect works the same
as in 7.6.)

After testing #moveSourceToChangesFile, I'm not convinced this is what we
want to do.

We have a package loaded cleanly and have no need of the parcel. Ultimately,
we want the package's source, not the parcel's source, in the .sou file.

Take SecurityBase for example. We have published it and loaded it into our
base image. Yet we have $(VISUALWORKS)\security\SecurityBase.pst referenced
in the Source Files settings. The package is clean, but so is the parcel. We
want to eliminate the parcel reference only. The source for SecurityBase in
our .sou file is as we want it. We do not want the parcel source in our
changes file or anywhere else for that matter.

Charlie

----- Original Message -----
From: "Terry Raymond" <[hidden email]>
To: "'Steve Whitson'" <[hidden email]>; <[hidden email]>
Sent: Thursday, October 16, 2008 7:00 PM
Subject: Re: [vwnc] remove dependencies on pst sources

> This is what we do,
>
> Refactory.Browser.BrowserNavigator
>
> moveSourceToChangesFile
>
> <menuItem: #(#MoveSourceToChangesFile 'Move source to changes')
> nameKey: #MoveSourceToChangesFile
> enablement: #isParcelSelected
> indication: nil
> menu: #(#parcelMenu )
> position: 20.3>
> ^self parcel unloadSource
>
>
> Terry
>
> ===========================================================
> Terry Raymond
> Crafted Smalltalk
> 80 Lazywood Ln.
> Tiverton, RI 02878
> (401) 624-4517 [hidden email]
> <http://www.craftedsmalltalk.com>
> ===========================================================
>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]] On
>> Behalf Of Steve Whitson
>> Sent: Thursday, October 16, 2008 1:00 PM
>> To: [hidden email]
>> Subject: [vwnc] remove dependencies on pst sources
>>
>> Hi All,
>>
>> Does anyone have any ideas how to go about removing the dependencies on
>> the .pst source pointers. I would like the .pst sources to be somehow
>> condensed onto the .sou file.
>>
>> We have been able to publish all the dependent parcels into store, and
>> reload them during out image builds. But now I would like to go a step
>> further and remove the source dependencies. The goal here is to end up
>> with a image (image.im, image.sou, image.cha) file set which needs only
>> the object engine. All code contained in the image should be present
>> for browsing.
>>
>> We already do the condenseChangesOntoSources which creates a .sou file
>> that matches our resulting image name. This is convenient, but we want
>> the .sou file to also contain all the other remaining (.pst) sources too
>> (such as StoreBase.pst).
>>
>> The method SourceFileManager>>newBaseSourceFileWithoutParcels: looks
>> like it might do the trick... although it doesn't get the whole job
>> done. The classes get pushed into the .sou file, but not the methods
>> (that's all I've reviewed thus far).
>>
>> Any help is greatly appreciated. Thanks much,
>> -Steve
>> _______________________________________________
>> vwnc mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Steve Whitson

Re: [vwnc] remove dependencies on pst sources

In reply to this post by Terry Raymond

Thanks Terry! I do believe that's the info we need. :)

-Steve

Terry Raymond wrote:

This is what we do,

Refactory.Browser.BrowserNavigator

moveSourceToChangesFile

	<menuItem: #(#MoveSourceToChangesFile 'Move source to changes')
			nameKey: #MoveSourceToChangesFile
			enablement: #isParcelSelected
			indication: nil
			menu: #(#parcelMenu )
			position: 20.3>
	^self parcel unloadSource


Terry
 
===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI  02878
(401) 624-4517      [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================

-----Original Message-----
From: [hidden email] [[hidden email]] On Behalf Of Steve Whitson
Sent: Thursday, October 16, 2008 1:00 PM
To: [hidden email]
Subject: [vwnc] remove dependencies on pst sources

Hi All,

Does anyone have any ideas how to go about removing the dependencies on
the .pst source pointers.  I would like the .pst sources to be somehow
condensed onto the .sou file.

We have been able to publish all the dependent parcels into store, and
reload them during out image builds.  But now I would like to go a step
further and remove the source dependencies.  The goal here is to end up
with a image (image.im, image.sou, image.cha) file set which needs only
the object engine.   All code contained in the image should be present
for browsing.

We already do the condenseChangesOntoSources which creates a .sou file
that matches our resulting image name.  This is convenient, but we want
the .sou file to also contain all the other remaining (.pst) sources too
(such as StoreBase.pst).

The method SourceFileManager>>newBaseSourceFileWithoutParcels:  looks
like it might do the trick... although it doesn't get the whole job
done.  The classes get pushed into the .sou file, but not the methods
(that's all I've reviewed thus far).

Any help is greatly appreciated.  Thanks much,
    -Steve
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Charles Adams

Re: [vwnc] remove dependencies on pst sources

In reply to this post by Charles Adams

OK, y'all are off the hook. Steve Whitson has convinced me #unloadSources
will give us good results.

Charlie

----- Original Message -----
From: "Charles Adams" <[hidden email]>
To: <[hidden email]>
Sent: Monday, October 20, 2008 11:45 AM
Subject: Re: [vwnc] remove dependencies on pst sources

> (I'm using a 7.4 image, but the method is there and I suspect works the
> same
> as in 7.6.)
>
> After testing #moveSourceToChangesFile, I'm not convinced this is what we
> want to do.
>
> We have a package loaded cleanly and have no need of the parcel.
> Ultimately,
> we want the package's source, not the parcel's source, in the .sou file.
>
> Take SecurityBase for example. We have published it and loaded it into our
> base image. Yet we have $(VISUALWORKS)\security\SecurityBase.pst
> referenced
> in the Source Files settings. The package is clean, but so is the parcel.
> We
> want to eliminate the parcel reference only. The source for SecurityBase
> in
> our .sou file is as we want it. We do not want the parcel source in our
> changes file or anywhere else for that matter.
>
>
> Charlie
>
>
> ----- Original Message -----
> From: "Terry Raymond" <[hidden email]>
> To: "'Steve Whitson'" <[hidden email]>; <[hidden email]>
> Sent: Thursday, October 16, 2008 7:00 PM
> Subject: Re: [vwnc] remove dependencies on pst sources
>
>
>> This is what we do,
>>
>> Refactory.Browser.BrowserNavigator
>>
>> moveSourceToChangesFile
>>
>> <menuItem: #(#MoveSourceToChangesFile 'Move source to changes')
>> nameKey: #MoveSourceToChangesFile
>> enablement: #isParcelSelected
>> indication: nil
>> menu: #(#parcelMenu )
>> position: 20.3>
>> ^self parcel unloadSource
>>
>>
>> Terry
>>
>> ===========================================================
>> Terry Raymond
>> Crafted Smalltalk
>> 80 Lazywood Ln.
>> Tiverton, RI 02878
>> (401) 624-4517 [hidden email]
>> <http://www.craftedsmalltalk.com>
>> ===========================================================
>>
>>> -----Original Message-----
>>> From: [hidden email] [mailto:[hidden email]] On
>>> Behalf Of Steve Whitson
>>> Sent: Thursday, October 16, 2008 1:00 PM
>>> To: [hidden email]
>>> Subject: [vwnc] remove dependencies on pst sources
>>>
>>> Hi All,
>>>
>>> Does anyone have any ideas how to go about removing the dependencies on
>>> the .pst source pointers. I would like the .pst sources to be somehow
>>> condensed onto the .sou file.
>>>
>>> We have been able to publish all the dependent parcels into store, and
>>> reload them during out image builds. But now I would like to go a step
>>> further and remove the source dependencies. The goal here is to end up
>>> with a image (image.im, image.sou, image.cha) file set which needs only
>>> the object engine. All code contained in the image should be present
>>> for browsing.
>>>
>>> We already do the condenseChangesOntoSources which creates a .sou file
>>> that matches our resulting image name. This is convenient, but we want
>>> the .sou file to also contain all the other remaining (.pst) sources too
>>> (such as StoreBase.pst).
>>>
>>> The method SourceFileManager>>newBaseSourceFileWithoutParcels: looks
>>> like it might do the trick... although it doesn't get the whole job
>>> done. The classes get pushed into the .sou file, but not the methods
>>> (that's all I've reviewed thus far).
>>>
>>> Any help is greatly appreciated. Thanks much,
>>> -Steve
>>> _______________________________________________
>>> vwnc mailing list
>>> [hidden email]
>>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>>
>> _______________________________________________
>> vwnc mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>>
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Terry Raymond

Re: [vwnc] remove dependencies on pst sources

In reply to this post by Charles Adams

If you loaded from the repository you should be referring
to the parcel pst file, unless possibly you attempted to
load over a loaded parcel.

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI 02878
(401) 624-4517 [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Charles Adams
> Sent: Monday, October 20, 2008 12:45 PM
> To: [hidden email]
> Subject: Re: [vwnc] remove dependencies on pst sources
>
> (I'm using a 7.4 image, but the method is there and I suspect works the same
> as in 7.6.)
>
> After testing #moveSourceToChangesFile, I'm not convinced this is what we
> want to do.
>
> We have a package loaded cleanly and have no need of the parcel. Ultimately,
> we want the package's source, not the parcel's source, in the .sou file.
>
> Take SecurityBase for example. We have published it and loaded it into our
> base image. Yet we have $(VISUALWORKS)\security\SecurityBase.pst referenced
> in the Source Files settings. The package is clean, but so is the parcel. We
> want to eliminate the parcel reference only. The source for SecurityBase in
> our .sou file is as we want it. We do not want the parcel source in our
> changes file or anywhere else for that matter.
>
>
> Charlie
>
>
> ----- Original Message -----
> From: "Terry Raymond" <[hidden email]>
> To: "'Steve Whitson'" <[hidden email]>; <[hidden email]>
> Sent: Thursday, October 16, 2008 7:00 PM
> Subject: Re: [vwnc] remove dependencies on pst sources
>
>
> > This is what we do,
> >
> > Refactory.Browser.BrowserNavigator
> >
> > moveSourceToChangesFile
> >
> > <menuItem: #(#MoveSourceToChangesFile 'Move source to changes')
> > nameKey: #MoveSourceToChangesFile
> > enablement: #isParcelSelected
> > indication: nil
> > menu: #(#parcelMenu )
> > position: 20.3>
> > ^self parcel unloadSource
> >
> >
> > Terry
> >
> > ===========================================================
> > Terry Raymond
> > Crafted Smalltalk
> > 80 Lazywood Ln.
> > Tiverton, RI 02878
> > (401) 624-4517 [hidden email]
> > <http://www.craftedsmalltalk.com>
> > ===========================================================
> >
> >> -----Original Message-----
> >> From: [hidden email] [mailto:[hidden email]] On
> >> Behalf Of Steve Whitson
> >> Sent: Thursday, October 16, 2008 1:00 PM
> >> To: [hidden email]
> >> Subject: [vwnc] remove dependencies on pst sources
> >>
> >> Hi All,
> >>
> >> Does anyone have any ideas how to go about removing the dependencies on
> >> the .pst source pointers. I would like the .pst sources to be somehow
> >> condensed onto the .sou file.
> >>
> >> We have been able to publish all the dependent parcels into store, and
> >> reload them during out image builds. But now I would like to go a step
> >> further and remove the source dependencies. The goal here is to end up
> >> with a image (image.im, image.sou, image.cha) file set which needs only
> >> the object engine. All code contained in the image should be present
> >> for browsing.
> >>
> >> We already do the condenseChangesOntoSources which creates a .sou file
> >> that matches our resulting image name. This is convenient, but we want
> >> the .sou file to also contain all the other remaining (.pst) sources too
> >> (such as StoreBase.pst).
> >>
> >> The method SourceFileManager>>newBaseSourceFileWithoutParcels: looks
> >> like it might do the trick... although it doesn't get the whole job
> >> done. The classes get pushed into the .sou file, but not the methods
> >> (that's all I've reviewed thus far).
> >>
> >> Any help is greatly appreciated. Thanks much,
> >> -Steve
> >> _______________________________________________
> >> vwnc mailing list
> >> [hidden email]
> >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
> >
> > _______________________________________________
> > vwnc mailing list
> > [hidden email]
> > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
> >
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Charles Adams

Re: [vwnc] remove dependencies on pst sources

I did indeed have a parcel loaded in the image when I went to the repository
and loaded its CM'ed version. Obviously, this doesn't accomplish what I'd
hoped.

There's something I'm missing here, but I'm not sure its worth the effort to
find out. Frankly, I don't want anything to do with parcels. They do not
represent a useful packaging concept to me or my product. The sooner we can
get to a published code base the better. The 5+ year hiatus we've taken from
the Envy paradigm has been nothing but a huge distraction.

Charlie

----- Original Message -----
From: "Terry Raymond" <[hidden email]>
To: "'Charles Adams'" <[hidden email]>; <[hidden email]>
Sent: Monday, October 20, 2008 5:49 PM
Subject: RE: [vwnc] remove dependencies on pst sources

> If you loaded from the repository you should be referring
> to the parcel pst file, unless possibly you attempted to
> load over a loaded parcel.
>
> Terry
>
> ===========================================================
> Terry Raymond
> Crafted Smalltalk
> 80 Lazywood Ln.
> Tiverton, RI 02878
> (401) 624-4517 [hidden email]
> <http://www.craftedsmalltalk.com>
> ===========================================================
>
>> -----Original Message-----
>> From: [hidden email] [mailto:[hidden email]] On
>> Behalf Of Charles Adams
>> Sent: Monday, October 20, 2008 12:45 PM
>> To: [hidden email]
>> Subject: Re: [vwnc] remove dependencies on pst sources
>>
>> (I'm using a 7.4 image, but the method is there and I suspect works the
>> same
>> as in 7.6.)
>>
>> After testing #moveSourceToChangesFile, I'm not convinced this is what we
>> want to do.
>>
>> We have a package loaded cleanly and have no need of the parcel.
>> Ultimately,
>> we want the package's source, not the parcel's source, in the .sou file.
>>
>> Take SecurityBase for example. We have published it and loaded it into
>> our
>> base image. Yet we have $(VISUALWORKS)\security\SecurityBase.pst
>> referenced
>> in the Source Files settings. The package is clean, but so is the parcel.
>> We
>> want to eliminate the parcel reference only. The source for SecurityBase
>> in
>> our .sou file is as we want it. We do not want the parcel source in our
>> changes file or anywhere else for that matter.
>>
>>
>> Charlie
>>
>>
>> ----- Original Message -----
>> From: "Terry Raymond" <[hidden email]>
>> To: "'Steve Whitson'" <[hidden email]>; <[hidden email]>
>> Sent: Thursday, October 16, 2008 7:00 PM
>> Subject: Re: [vwnc] remove dependencies on pst sources
>>
>>
>> > This is what we do,
>> >
>> > Refactory.Browser.BrowserNavigator
>> >
>> > moveSourceToChangesFile
>> >
>> > <menuItem: #(#MoveSourceToChangesFile 'Move source to changes')
>> > nameKey: #MoveSourceToChangesFile
>> > enablement: #isParcelSelected
>> > indication: nil
>> > menu: #(#parcelMenu )
>> > position: 20.3>
>> > ^self parcel unloadSource
>> >
>> >
>> > Terry
>> >
>> > ===========================================================
>> > Terry Raymond
>> > Crafted Smalltalk
>> > 80 Lazywood Ln.
>> > Tiverton, RI 02878
>> > (401) 624-4517 [hidden email]
>> > <http://www.craftedsmalltalk.com>
>> > ===========================================================
>> >
>> >> -----Original Message-----
>> >> From: [hidden email] [mailto:[hidden email]] On
>> >> Behalf Of Steve Whitson
>> >> Sent: Thursday, October 16, 2008 1:00 PM
>> >> To: [hidden email]
>> >> Subject: [vwnc] remove dependencies on pst sources
>> >>
>> >> Hi All,
>> >>
>> >> Does anyone have any ideas how to go about removing the dependencies
>> >> on
>> >> the .pst source pointers. I would like the .pst sources to be somehow
>> >> condensed onto the .sou file.
>> >>
>> >> We have been able to publish all the dependent parcels into store, and
>> >> reload them during out image builds. But now I would like to go a
>> >> step
>> >> further and remove the source dependencies. The goal here is to end
>> >> up
>> >> with a image (image.im, image.sou, image.cha) file set which needs
>> >> only
>> >> the object engine. All code contained in the image should be present
>> >> for browsing.
>> >>
>> >> We already do the condenseChangesOntoSources which creates a .sou file
>> >> that matches our resulting image name. This is convenient, but we
>> >> want
>> >> the .sou file to also contain all the other remaining (.pst) sources
>> >> too
>> >> (such as StoreBase.pst).
>> >>
>> >> The method SourceFileManager>>newBaseSourceFileWithoutParcels: looks
>> >> like it might do the trick... although it doesn't get the whole job
>> >> done. The classes get pushed into the .sou file, but not the methods
>> >> (that's all I've reviewed thus far).
>> >>
>> >> Any help is greatly appreciated. Thanks much,
>> >> -Steve
>> >> _______________________________________________
>> >> vwnc mailing list
>> >> [hidden email]
>> >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>> >
>> > _______________________________________________
>> > vwnc mailing list
>> > [hidden email]
>> > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>> >
>>
>> _______________________________________________
>> vwnc mailing list
>> [hidden email]
>> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>
>

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Terry Raymond

Re: [vwnc] remove dependencies on pst sources

Charles

There is a package in the public repository you might be
interested in, "Store-Source-Extention". It adds a local
.sou file to your development. It holds the source loaded
from the repository thus permitting the changes file to hold
only changes made locally by the developer.

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI 02878
(401) 624-4517 [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================

> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Charles Adams
> Sent: Tuesday, October 21, 2008 10:16 AM
> To: [hidden email]
> Subject: Re: [vwnc] remove dependencies on pst sources
>
> I did indeed have a parcel loaded in the image when I went to the repository
> and loaded its CM'ed version. Obviously, this doesn't accomplish what I'd
> hoped.
>
> There's something I'm missing here, but I'm not sure its worth the effort to
> find out. Frankly, I don't want anything to do with parcels. They do not
> represent a useful packaging concept to me or my product. The sooner we can
> get to a published code base the better. The 5+ year hiatus we've taken from
> the Envy paradigm has been nothing but a huge distraction.
>
> Charlie
>
> ----- Original Message -----
> From: "Terry Raymond" <[hidden email]>
> To: "'Charles Adams'" <[hidden email]>; <[hidden email]>
> Sent: Monday, October 20, 2008 5:49 PM
> Subject: RE: [vwnc] remove dependencies on pst sources
>
>
> > If you loaded from the repository you should be referring
> > to the parcel pst file, unless possibly you attempted to
> > load over a loaded parcel.
> >
> > Terry
> >
> > ===========================================================
> > Terry Raymond
> > Crafted Smalltalk
> > 80 Lazywood Ln.
> > Tiverton, RI 02878
> > (401) 624-4517 [hidden email]
> > <http://www.craftedsmalltalk.com>
> > ===========================================================
> >
> >> -----Original Message-----
> >> From: [hidden email] [mailto:[hidden email]] On
> >> Behalf Of Charles Adams
> >> Sent: Monday, October 20, 2008 12:45 PM
> >> To: [hidden email]
> >> Subject: Re: [vwnc] remove dependencies on pst sources
> >>
> >> (I'm using a 7.4 image, but the method is there and I suspect works the
> >> same
> >> as in 7.6.)
> >>
> >> After testing #moveSourceToChangesFile, I'm not convinced this is what we
> >> want to do.
> >>
> >> We have a package loaded cleanly and have no need of the parcel.
> >> Ultimately,
> >> we want the package's source, not the parcel's source, in the .sou file.
> >>
> >> Take SecurityBase for example. We have published it and loaded it into
> >> our
> >> base image. Yet we have $(VISUALWORKS)\security\SecurityBase.pst
> >> referenced
> >> in the Source Files settings. The package is clean, but so is the parcel.
> >> We
> >> want to eliminate the parcel reference only. The source for SecurityBase
> >> in
> >> our .sou file is as we want it. We do not want the parcel source in our
> >> changes file or anywhere else for that matter.
> >>
> >>
> >> Charlie
> >>
> >>
> >> ----- Original Message -----
> >> From: "Terry Raymond" <[hidden email]>
> >> To: "'Steve Whitson'" <[hidden email]>; <[hidden email]>
> >> Sent: Thursday, October 16, 2008 7:00 PM
> >> Subject: Re: [vwnc] remove dependencies on pst sources
> >>
> >>
> >> > This is what we do,
> >> >
> >> > Refactory.Browser.BrowserNavigator
> >> >
> >> > moveSourceToChangesFile
> >> >
> >> > <menuItem: #(#MoveSourceToChangesFile 'Move source to changes')
> >> > nameKey: #MoveSourceToChangesFile
> >> > enablement: #isParcelSelected
> >> > indication: nil
> >> > menu: #(#parcelMenu )
> >> > position: 20.3>
> >> > ^self parcel unloadSource
> >> >
> >> >
> >> > Terry
> >> >
> >> > ===========================================================
> >> > Terry Raymond
> >> > Crafted Smalltalk
> >> > 80 Lazywood Ln.
> >> > Tiverton, RI 02878
> >> > (401) 624-4517 [hidden email]
> >> > <http://www.craftedsmalltalk.com>
> >> > ===========================================================
> >> >
> >> >> -----Original Message-----
> >> >> From: [hidden email] [mailto:[hidden email]] On
> >> >> Behalf Of Steve Whitson
> >> >> Sent: Thursday, October 16, 2008 1:00 PM
> >> >> To: [hidden email]
> >> >> Subject: [vwnc] remove dependencies on pst sources
> >> >>
> >> >> Hi All,
> >> >>
> >> >> Does anyone have any ideas how to go about removing the dependencies
> >> >> on
> >> >> the .pst source pointers. I would like the .pst sources to be somehow
> >> >> condensed onto the .sou file.
> >> >>
> >> >> We have been able to publish all the dependent parcels into store, and
> >> >> reload them during out image builds. But now I would like to go a
> >> >> step
> >> >> further and remove the source dependencies. The goal here is to end
> >> >> up
> >> >> with a image (image.im, image.sou, image.cha) file set which needs
> >> >> only
> >> >> the object engine. All code contained in the image should be present
> >> >> for browsing.
> >> >>
> >> >> We already do the condenseChangesOntoSources which creates a .sou file
> >> >> that matches our resulting image name. This is convenient, but we
> >> >> want
> >> >> the .sou file to also contain all the other remaining (.pst) sources
> >> >> too
> >> >> (such as StoreBase.pst).
> >> >>
> >> >> The method SourceFileManager>>newBaseSourceFileWithoutParcels: looks
> >> >> like it might do the trick... although it doesn't get the whole job
> >> >> done. The classes get pushed into the .sou file, but not the methods
> >> >> (that's all I've reviewed thus far).
> >> >>
> >> >> Any help is greatly appreciated. Thanks much,
> >> >> -Steve
> >> >> _______________________________________________
> >> >> vwnc mailing list
> >> >> [hidden email]
> >> >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
> >> >
> >> > _______________________________________________
> >> > vwnc mailing list
> >> > [hidden email]
> >> > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
> >> >
> >>
> >> _______________________________________________
> >> vwnc mailing list
> >> [hidden email]
> >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
> >
> >
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc