What do you think of deleting old packages which are completely useless, even for historical purposes. Some are actually from early attempt to port Moose but we have moved on since.
A few examples:
Moose-Installer Smart-Collections Monticello SLICE-* Merlin (has its own project now) TestWizard (now part of Merlin?) MooseGlamourBrowser (early attempt) Moose-UI (early attempt) Moose-Test-PackageBlueprint (old, duplication) PackageBlueprintOld Moose-PackageBlueprint (deprecated) Moose-NewBlueprint (deprecated) Moose-PB* (deprecated) Moose-NP* (deprecated) Moose-LANTests (old stuff) Moose-Importer-Tests (old stuff)
I dont want to delete some deprecated packages which still have a lot of versions, might be interesting for historical purposes.
Browsing the Moose repository from MC often feels sluggish : I suspect this is because of the high number of files. Maybe one day we should split between a Moose project and a Famix project.
-- Simon
Hi Simon,
I very much agree with this.
I think you can add: MooseCook, Moose-CookFamix3 (was moved in Famix-Extensions) Moose-UI (old UI) MooseLoader (replaced by ConfigurationOfMoose) Moose-OBBrowser (old UI) Moose-All
I would suggest to actually move this code into a dedicated repository. I created a MooseDeprecated repository:
MCHttpRepository location: 'http://www.squeaksource.com/MooseDeprecated' user: '' password: ''
Anyone up for this task? :)
Cheers, Doru
On 15 Jan 2010, at 23:54, Simon Denier wrote:
What do you think of deleting old packages which are completely useless, even for historical purposes. Some are actually from early attempt to port Moose but we have moved on since.
A few examples:
Moose-Installer Smart-Collections Monticello SLICE-* Merlin (has its own project now) TestWizard (now part of Merlin?) MooseGlamourBrowser (early attempt) Moose-UI (early attempt) Moose-Test-PackageBlueprint (old, duplication) PackageBlueprintOld Moose-PackageBlueprint (deprecated) Moose-NewBlueprint (deprecated) Moose-PB* (deprecated) Moose-NP* (deprecated) Moose-LANTests (old stuff) Moose-Importer-Tests (old stuff)
I dont want to delete some deprecated packages which still have a lot of versions, might be interesting for historical purposes.
Browsing the Moose repository from MC often feels sluggish : I suspect this is because of the high number of files. Maybe one day we should split between a Moose project and a Famix project.
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Beauty is where we see it."
On Jan 15, 2010, at 11:54 PM, Simon Denier wrote:
What do you think of deleting old packages which are completely useless, even for historical purposes. Some are actually from early attempt to port Moose but we have moved on since.
A few examples:
Moose-Installer Smart-Collections Monticello SLICE-* Merlin (has its own project now) TestWizard (now part of Merlin?) MooseGlamourBrowser (early attempt) Moose-UI (early attempt) Moose-Test-PackageBlueprint (old, duplication) PackageBlueprintOld Moose-PackageBlueprint (deprecated) Moose-NewBlueprint (deprecated) Moose-PB* (deprecated) Moose-NP* (deprecated)
simon I think that this really important to clean now are you sure that is deprecated? Moose-NewBlueprint (deprecated)
Moose-LANTests (old stuff) Moose-Importer-Tests (old stuff)
I dont want to delete some deprecated packages which still have a lot of versions, might be interesting for historical purposes.
create a MooseDeprecated and move them there. I do not that all the time with pharo inbox (so exicting)
Browsing the Moose repository from MC often feels sluggish : I suspect this is because of the high number of files. Maybe one day we should split between a Moose project and a Famix project.
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
On 16 janv. 2010, at 12:25, Stéphane Ducasse wrote:
On Jan 15, 2010, at 11:54 PM, Simon Denier wrote:
What do you think of deleting old packages which are completely useless, even for historical purposes. Some are actually from early attempt to port Moose but we have moved on since.
A few examples:
Moose-Installer Smart-Collections Monticello SLICE-* Merlin (has its own project now) TestWizard (now part of Merlin?) MooseGlamourBrowser (early attempt) Moose-UI (early attempt) Moose-Test-PackageBlueprint (old, duplication) PackageBlueprintOld Moose-PackageBlueprint (deprecated) Moose-NewBlueprint (deprecated) Moose-PB* (deprecated) Moose-NP* (deprecated)
simon I think that this really important to clean now are you sure that is deprecated? Moose-NewBlueprint (deprecated)
Yep, we continued to clean up the code yesterday and as a result, we moved it back to MondrianPaintings as OutgoingPackageBlueprint Also added a launch script on FamixPackage>>viewOutgoingPackageBlueprint in the Finder
Moose-LANTests (old stuff) Moose-Importer-Tests (old stuff)
I dont want to delete some deprecated packages which still have a lot of versions, might be interesting for historical purposes.
create a MooseDeprecated and move them there. I do not that all the time with pharo inbox (so exicting)
ok, starting now
-- Simon
Thanks a lot, Simon.
I added you as an admin to MooseDeprecated.
Doru
On 16 Jan 2010, at 12:39, Simon Denier wrote:
On 16 janv. 2010, at 12:25, Stéphane Ducasse wrote:
On Jan 15, 2010, at 11:54 PM, Simon Denier wrote:
What do you think of deleting old packages which are completely useless, even for historical purposes. Some are actually from early attempt to port Moose but we have moved on since.
A few examples:
Moose-Installer Smart-Collections Monticello SLICE-* Merlin (has its own project now) TestWizard (now part of Merlin?) MooseGlamourBrowser (early attempt) Moose-UI (early attempt) Moose-Test-PackageBlueprint (old, duplication) PackageBlueprintOld Moose-PackageBlueprint (deprecated) Moose-NewBlueprint (deprecated) Moose-PB* (deprecated) Moose-NP* (deprecated)
simon I think that this really important to clean now are you sure that is deprecated? Moose-NewBlueprint (deprecated)
Yep, we continued to clean up the code yesterday and as a result, we moved it back to MondrianPaintings as OutgoingPackageBlueprint Also added a launch script on FamixPackage>>viewOutgoingPackageBlueprint in the Finder
Moose-LANTests (old stuff) Moose-Importer-Tests (old stuff)
I dont want to delete some deprecated packages which still have a lot of versions, might be interesting for historical purposes.
create a MooseDeprecated and move them there. I do not that all the time with pharo inbox (so exicting)
ok, starting now
-- Simon
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Being happy is a matter of choice."
-
Simon Denier -
Stéphane Ducasse -
Tudor Girba