[Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523
Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 4021f31ef110a3f16862ef02329c66f4e04ffa40 https://github.com/pharo-project/pharo-core/commit/4021f31ef110a3f16862ef02329c66f4e04ffa40 Author: Jenkins Build Server Date: 2013-10-25 (Fri, 25 Oct 2013) Changed paths: R BaselineOfFileTree.package/BaselineOfFileTree.class/README.md R BaselineOfFileTree.package/BaselineOfFileTree.class/definition.st R BaselineOfFileTree.package/BaselineOfFileTree.class/instance/baseline/baseline_.st R BaselineOfMetacello.package/BaselineOfMetacello.class/README.md R BaselineOfMetacello.package/BaselineOfMetacello.class/definition.st R BaselineOfMetacello.package/BaselineOfMetacello.class/instance/baseline/baseline_.st R BaselineOfMetacello.package/BaselineOfMetacello.class/instance/doits/gemstone10beta311PostLoadDoIt.st R BaselineOfMetacello.package/BaselineOfMetacello.class/instance/doits/reprimeRegistryIssue197.st R BaselineOfMetacello.package/BaselineOfMetacello.class/instance/doits/testResourcePostLoadDoIt.st M Collections-Strings.package/String.class/instance/converting/subStrings_.st M Kernel.package/DeepCopier.class/definition.st M Kernel.package/DeepCopier.class/instance/like fullCopy/checkClass_.st M Kernel.package/DeepCopier.class/instance/like fullCopy/checkVariables.st R Kernel.package/DeepCopier.class/instance/like fullCopy/intervalForChecks.st R Kernel.package/DeepCopier.class/instance/like fullCopy/isItTimeToCheckVariables.st A Kernel.package/DeepCopier.class/instance/like fullCopy/warnInstanceVariableNotCopiedIn_selector_.st R Kernel.package/DeepCopier.class/instance/like fullCopy/warnIverNotCopiedIn_sel_.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script178.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30523.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M System-Support.package/SystemNavigation.class/instance/query/obsoleteMethodReferences.st M Tools.package/extension/SystemNavigation/instance/browseObsoleteReferences.st Log Message: --- 30523 12001 moved some isKindOf: to isXXX https://pharo.fogbugz.com/f/cases/12001 12004 delete empty packages https://pharo.fogbugz.com/f/cases/12004 12002 DeepCopier>>isItTimeToCheckVariables is candidate to be removed https://pharo.fogbugz.com/f/cases/12002 12005 unload BaselineOfFileTree, BaselineOfMetacello https://pharo.fogbugz.com/f/cases/12005 http://files.pharo.org/image/30/30523.zip
Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523
Why do we need to remove configurations of projects loaded into the image? I would say the opposite: all projects in the image should have their configuration loaded. It is part of the project. Le 25 oct. 2013 à 14:00, GitHub a écrit : > 12005 unload BaselineOfFileTree, BaselineOfMetacello > https://pharo.fogbugz.com/f/cases/12005 smime.p7s Description: S/MIME cryptographic signature
Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523
I did it because they are the only ones. Yes, we need to have them at some point. But having two baselines but nothing else makes no sense. And we need to be able to organise package better, even with the package tags there is too much in the left pane. On 25 Oct 2013 at 15:19:02, Christophe Demarey (christophe.dema...@inria.fr) wrote: > >Why do we need to remove configurations of projects loaded into the image? >I would say the opposite: all projects in the image should have their >configuration loaded. It is part of the project. > >Le 25 oct. 2013 à 14:00, GitHub a écrit : >> 12005 unload BaselineOfFileTree, BaselineOfMetacello >> https://pharo.fogbugz.com/f/cases/12005 > > >- smime.p7s, 6 KB
Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523
I agree with this. In particular, the configuration classes offer extra information that can be used by smart browsers. We need them. Cheers, Doru On Fri, Oct 25, 2013 at 3:18 PM, Christophe Demarey < christophe.dema...@inria.fr> wrote: > Why do we need to remove configurations of projects loaded into the image? > I would say the opposite: all projects in the image should have their > configuration loaded. It is part of the project. > > Le 25 oct. 2013 à 14:00, GitHub a écrit : > > 12005 unload BaselineOfFileTree, BaselineOfMetacello > > https://pharo.fogbugz.com/f/cases/12005 > > > -- www.tudorgirba.com "Every thing has its own flow"
Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523
Le 25/10/2013 15:27, Marcus Denker a écrit : ... even with the package tags there is too much in the left pane. Yes, I've seen that as well. Either go into the six pane browser of S. Travis Pope, or use the tree to build proper categories of packages like I do in the AltBrowser. I.e. it's a GUI issue, not a package issue. Thierry On 25 Oct 2013 at 15:19:02, Christophe Demarey (christophe.dema...@inria.fr) wrote: Why do we need to remove configurations of projects loaded into the image? I would say the opposite: all projects in the image should have their configuration loaded. It is part of the project. Le 25 oct. 2013 à 14:00, GitHub a écrit : 12005 unload BaselineOfFileTree, BaselineOfMetacello https://pharo.fogbugz.com/f/cases/12005 - smime.p7s, 6 KB -- Thierry Goubier CEA list Laboratoire des Fondations des Systèmes Temps Réel Embarqués 91191 Gif sur Yvette Cedex France Phone/Fax: +33 (0) 1 69 08 32 92 / 83 95
Re: [Pharo-dev] [pharo-project/pharo-core] 4021f3: 30523
Indeed I'm all in favor to have ConfigurationOf in the image because they are metaData of the packages and projects!!! I do not understand why UI concerns show up into structure of the system. I do not see why having a long list is a problem: there is a search behavior there is a smart group So it would be good not to mix systematically this issue. I'm quite sure that we can open Nautilus on an empty RBBrowserEnvironment and it will work so? Let us move on. I spent time rebuilding from scratch some configurations and I will continue because I want to create a Pharo image from a set of projects and I must have configuration for doing so. Stef > I agree with this. In particular, the configuration classes offer extra > information that can be used by smart browsers. We need them. > > Cheers, > Doru > > > On Fri, Oct 25, 2013 at 3:18 PM, Christophe Demarey > wrote: > Why do we need to remove configurations of projects loaded into the image? > I would say the opposite: all projects in the image should have their > configuration loaded. It is part of the project. > > Le 25 oct. 2013 à 14:00, GitHub a écrit : > > 12005 unload BaselineOfFileTree, BaselineOfMetacello > > https://pharo.fogbugz.com/f/cases/12005 > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow"
