July 2013 - Pharo-dev - lists.pharo.org

[update 3.0] #30296

by Marcus Denker

July 24, 2013

Re: [Pharo-dev] Loading scripts vs. configs with #stable and config browser (was: [ann] snapshotcello)

by StÃ©phane Ducasse

+ 1 :) This is why I'm working on the PackageCatalog :) here is an example Stef On Jul 24, 2013, at 10:04 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Tudor wrote: >> You can get the code at: >> Gofer new >> smalltalkhubUser: 'girba' project: 'Snapshotcello'; >> package: 'ConfigurationOfSnapshotcello'; >> load. >> (Smalltalk globals at: #ConfigurationOfSnapshotcello) loadDevelopment > > Sorry about the rant in advance (which is more general and not only specific to snapshotcello), but: > > Next time someone wants this (or another) nice little Pharo tool: > > - one has to remember this load script or have to find the announcement mail again > - one has to a lot of typing the expression or copying to a workspace to load it. > > Just with the posted load script he does dont know if Pharo 1.4, 2.0 or 3.0 was used to develop it, > so how does he know the Pharo version to use it without failures? A pharo version where it is not broken. > Maybe the user is still using Pharo 2.0 but maybe the tool requires at least Pharo 3.0 ... > > What about a new user who starts tomorrow with Pharo and never read this announcement. > Since he entered the mailinglist very late he missed the mail with the script. > How can he now about this super cool package? Why cant it be more accessible? > > I propose: PLEASE define a #stable for the working versions and place an additional copy in: > > - "ss3.gemtalksystems.com/ss/MetaRepoForPharo20" (Pharo 2.0) or > - "http://smalltalkhub.com/mc/Pharo/MetaRepoForPharo30/main" (Pharo 3.0) > > when you know it runs in the according pharo version. It will then appear in the config browser. > > If it is not in the config browser of the current pharo version for easy loading > then it does not really exist. ;) > It only exists for the people who read about it in the mailinglist. Think of a first > time user who downloads Pharo 2.0. He may never stumble over the load script or > the tool in Smalltalkhub. > > I know: it may not yet be the best mechanism to provide packages to users (we need more infos > on the configs, hence catalog and automatic verification in the future) - but still it > is better than the "load scripts" and possible confusion. > > So please CARE ABOUT YOUR USERS and make your packages available like this so it can > be easily accessible and loadable right from the according image! > > Same for Roassal, Moose, ... and all the nice packages that now appear in the > Pharo universe... > > Thanks > T. >

July 24, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30295 Home: https://github.com/pharo-project/pharo-core

July 24, 2013

[pharo-project/pharo-core] c3f24c: 30295

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: c3f24c045e28a6ff5ad751885b984664a76597c2 https://github.com/pharo-project/pharo-core/commit/c3f24c045e28a6ff5ad75188… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-07-24 (Wed, 24 Jul 2013) Changed paths: R KernelTests-Classes/BasicBehaviorClassMetaclassTest.cls/instance/testing/testClassDescriptionAllSubInstances.st M Refactoring-Tests-Changes/RBRefactoringChangeTests.cls/instance/tests-pattern/testAddMetaclassPattern.st M ScriptLoader30/ScriptLoader.cls/instance/pharo - scripts/script129.st A ScriptLoader30/ScriptLoader.cls/instance/pharo - scripts/script130.st M ScriptLoader30/ScriptLoader.cls/instance/pharo - updates/update30294.st A ScriptLoader30/ScriptLoader.cls/instance/pharo - updates/update30295.st M ScriptLoader30/ScriptLoader.cls/instance/public/commentForCurrentUpdate.st A Spec-Debugger/SpecDebugger.cls/class/accessing/defaultStackSize.st A Spec-Debugger/SpecDebugger.cls/class/accessing/expandedStackSize.st M Spec-Debugger/SpecDebugger.cls/class/instance creation/informExistingDebugger_label_.st M Spec-Debugger/SpecDebugger.cls/class/menu/menuStackAction_.st M Spec-Debugger/SpecDebugger.cls/class/menu/menuStack_.st M Spec-Debugger/SpecDebugger.cls/class/opening/openInterrupt_onProcess_.st A Spec-Debugger/SpecDebugger.cls/class/printing/buildClassNameFor_.st A Spec-Debugger/SpecDebugger.cls/class/printing/columnsFor_.st A Spec-Debugger/SpecDebugger.cls/class/tools registry/register.st A Spec-Debugger/SpecDebugger.cls/class/tools registry/registerToolsOn_.st A Spec-Debugger/SpecDebugger.cls/instance/actions/expandStack.st R Spec-Debugger/SpecDebugger.cls/instance/initialization/errorWasInUIProcess_.st M Spec-Debugger/SpecDebugger.cls/instance/initialization/initializePresenter.st M Spec-Debugger/SpecDebugger.cls/instance/initialization/initializeWidgets.st A Spec-Debugger/SpecDebugger.cls/instance/initialization/setStackShortcuts.st A Spec-Debugger/SpecDebugger.cls/instance/initialization/shortCuts.st M Spec-Debugger/SpecDebugger.cls/instance/intialization menu/contextStackMenu_.st R Spec-Debugger/SpecDebugger.cls/instance/intialization menu/implementStackMenu_.st A Spec-Debugger/SpecDebugger.cls/instance/old - public/errorWasInUIProcess_.st R Spec-Debugger/SpecDebugger.cls/instance/private/buildClassNameFor_.st M Spec-Debugger/SpecDebugger.cls/instance/private/columnsFor_.st M Spec-Debugger/SpecDebugger.cls/instance/updating/updateCodeFromContext_.st A Spec-Debugger/SpecDebugger.cls/instance/updating/updateStackFromSelectedContext.st M Spec-Debugger/SpecDebugger.cls/instance/updating/updateStackFromSession_.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions browsing/browseClassVarRefs.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions browsing/browseClassVariables.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions browsing/browseInstVarRefs.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions browsing/browseMessages.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions browsing/browseSendersOfMessages.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions browsing/browseVersions.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions browsing/currentClass.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions browsing/currentMessageCategoryName.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions browsing/methodHierarchy.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions/copyToClipboard.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions/expandStackBy_.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions/fullStackAction.st M Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions/peelToFirst.st M Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions/returnValue.st M Spec-Debugger/SpecDebuggerToolbar.cls/instance/actions/toggleBreakOnEntry.st M Spec-Debugger/SpecDebuggerToolbar.cls/instance/building widgets/validButtonIds.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/initialization widgets/initializeFullStackButton.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/testing/hasFullStackAction.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/testing/shouldEnableFullStackButton.st A Spec-Debugger/SpecDebuggerToolbar.cls/instance/updating/updateFullStackButton.st R Spec-Debugger/SpecPreDebugWindow.cls/instance/as yet unclassified/buildClassNameFor_.st R Spec-Debugger/SpecPreDebugWindow.cls/instance/as yet unclassified/columnsFor_.st M Spec-Debugger/SpecPreDebugWindow.cls/instance/initialize-widgets/initializeStackPane.st A Spec-Debugger/SpecPreDebugWindow.cls/instance/printing/columnsFor_.st M Spec-Debugger/SpecProxyDebugger.cls/class/class initialization/initialize.st A System-Changes/ChangeRecord.cls/instance/access/prior.st M System-Changes/ChangeSet.cls/definition.st A System-Changes/ChangeSet.cls/instance/accessing/structures.st M System-Changes/ChangeSet.cls/instance/change logging/changeClass_from_.st M System-Changes/ChangeSet.cls/instance/change logging/renameClass_from_to_.st A System-Changes/ChangeSet.cls/instance/class changes/noteClassForgotten_.st A System-Changes/ChangeSet.cls/instance/class changes/noteClassStructure_.st A System-Changes/ChangeSet.cls/instance/method changes/messageListForChangesWhich_ifNone_.st M System-Changes/ChangeSet.cls/instance/moving changes/absorbClass_from_.st A System-Changes/ChangeSet.cls/instance/moving changes/absorbStructureOfClass_from_.st M System-Changes/ChangeSet.cls/instance/moving changes/forgetChangesForClass_in_.st A System-Changes/ChangeSet.cls/instance/moving changes/methodsWithAnyInitialsOtherThan_.st M System-Changes/ChangeSet.cls/instance/moving changes/removeClassChanges_.st M Tools-Debugger/SyntaxError.cls/instance/other/notify_at_in_.st R UIManager/NonInteractiveUIManager.cls/instance/ui requests/openDebuggerOn_context_label_contents_fullView_.st Log Message: ----------- 30295 11219 Speed up test run: #testAddMetaclassPattern in RBRefactoringChangeTests https://pharo.fogbugz.com/f/cases/11219 11224 Enable the new debugger https://pharo.fogbugz.com/f/cases/11224 10780 Inspecting self in SpecDebugger inspects nil https://pharo.fogbugz.com/f/cases/10780

July 24, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=win/… 2 regressions found. AST.Interpreter.Test.ASTInterpreterTest.testAssert ToolsTest.Debugger.DebuggerTest.testBasic

July 24, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=mac/… 2 regressions found. AST.Interpreter.Test.ASTInterpreterTest.testAssert ToolsTest.Debugger.DebuggerTest.testBasic

July 24, 2013

[regression reporter]regression occurred

by no-reply＠ci.inria.fr

https://ci.inria.fr/pharo/job/Pharo-3.0-Update-Step-2-Validation/label=linu… 2 regressions found. AST.Interpreter.Test.ASTInterpreterTest.testAssert ToolsTest.Debugger.DebuggerTest.testBasic

July 24, 2013

Re: [Pharo-dev] [update 3.0] #30295

by Tudor Girba

Hi, On Wed, Jul 24, 2013 at 1:05 PM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > 30295 > ----- > > 11219 Speed up test run: #testAddMetaclassPattern in > RBRefactoringChangeTests > https://pharo.fogbugz.com/f/cases/11219 > > 11224 Enable the new debugger > https://pharo.fogbugz.com/f/cases/11224 This is so cool! :) Doru > > 10780 Inspecting self in SpecDebugger inspects nil > https://pharo.fogbugz.com/f/cases/10780 > > > > Diff information: > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.99… > > http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Tests-Changes-Mar… > > > -- www.tudorgirba.com "Every thing has its own flow"

July 24, 2013

[update 3.0] #30295

by Marcus Denker

30295 ----- 11219 Speed up test run: #testAddMetaclassPattern in RBRefactoringChangeTests https://pharo.fogbugz.com/f/cases/11219 11224 Enable the new debugger https://pharo.fogbugz.com/f/cases/11224 10780 Inspecting self in SpecDebugger inspects nil https://pharo.fogbugz.com/f/cases/10780 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.99… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Refactoring-Tests-Changes-Mar…

July 24, 2013

Re: [Pharo-dev] [Pharo-users] [Moose-dev] Re: Re: [ann] snapshotcello

by Tudor Girba

Perhaps I missed something in the toolbox, but as far as I know you cannot create a version of a configuration that is composed of multiple sub-projects nested multiple levels deep. Could you describe the way you are using the Metacello Toolbox? Doru On Wed, Jul 24, 2013 at 10:39 AM, Johan Brichau <johan(a)inceptive.be> wrote: > Hi Doru, Stef, > > May I ask what the difference is with the version generation and updating > methods found in MetacelloToolbox ? I want to understand, because I am > currently using these of MetacelloToolbox to do the things you describe. > > Cheers! > Johan > > On 24 Jul 2013, at 09:52, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > wrote: > > > > > On Jul 24, 2013, at 9:11 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > > >> Hi, > >> > >> On Jul 24, 2013, at 8:48 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> > >>> > >>> On Jul 23, 2013, at 11:51 PM, Dale K. Henrichs < > dale.henrichs(a)gemtalksystems.com> wrote: > >>> > >>>> Stef, > >>>> > >>>> I haven't completely wrapped my brain around what SnapshotCello does > so I don't have an informed opinion ... the fact that you found a need to > invent SnapshotCello does speak volumes to the fact that there is a need > that is going unmet:). > >>>> > >>>> However, I don't like the fact that you end up sending a non-spec > message to make this work (#populateSpec:with:). Tools like Versioner will > not be able to rewrite a method like this correctly so it is a less than > satisfactory workaround to the method literal limit. > >>> Indeed. May be in the future we could recreate a simple compliant spec > driven method by interpreting the > >>> existing configuration trees but this requires some work. > >> > >> I do not understand this point. What do you mean by "interpreting the > configuration trees"? > > > > I mean going over the configurations with dependencies to recreate the > tree structure but with versions. > > May be this is not needed because for versions we do not need > dependencies so just group them per configurations. > > > >> > >> Doru > >> > >>>> > >>>> With that said it _is_ performing a useful function ... > >>>> > >>>> I have recently come up with an approach to addressing the method > literal limit from a slightly different angle and I would assume that > SnapshotCello could be recast to use this "approved approach" when the new > techinique becomes available. At that time it would make sense to roll the > SnapshotCello funtionality into the MetacelloToolBox... > >>>> > >>>> Dale > >>>> > >>>> [1] > http://forum.world.st/Loading-problem-in-Seaside-tp4699965p4700161.html > >>>> ----- Original Message ----- > >>>> | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > >>>> | To: "Moose-related development" <moose-dev(a)iam.unibe.ch> > >>>> | Cc: "Any question about pharo is welcome" < > pharo-users(a)lists.pharo.org>, "Pharo Development List" > >>>> | <pharo-dev(a)lists.pharo.org> > >>>> | Sent: Tuesday, July 23, 2013 2:17:50 PM > >>>> | Subject: [Moose-dev] Re: [ann] snapshotcello > >>>> | > >>>> | Nice to see SnapshotCello coming to live. May be it should be > >>>> | integrated to Metacello. > >>>> | Because everybody may need this cool feature. > >>>> | > >>>> | Stef > >>>> | > >>>> | On Jul 23, 2013, at 10:43 PM, Tudor Girba <tudor(a)tudorgirba.com> > >>>> | wrote: > >>>> | > >>>> | > Hi, > >>>> | > > >>>> | > Stef and I developed Snapshotcello, a little utility that enables > >>>> | > you to freeze a snapshot of a given configuration based on what is > >>>> | > already loaded in your current image. > >>>> | > > >>>> | > The idea is simple. You develop against the latest versions of all > >>>> | > packages, and commit your changes for each package. When you are > >>>> | > ready for a release, you assemble your image, and generate a > >>>> | > snapshot version that can be reloaded later. > >>>> | > > >>>> | > Here is an example of how it can work to take a snapshot of a > >>>> | > development version: > >>>> | > Snapshotcello new > >>>> | > configurationClass: ConfigurationOfMoose; > >>>> | > configurationVersion: #development; > >>>> | > publishVersion: '4.8-snapshot' > >>>> | > > >>>> | > You can find more details here: > >>>> | > > http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… > >>>> | > > >>>> | > You can get the code at: > >>>> | > Gofer new > >>>> | > smalltalkhubUser: 'girba' project: 'Snapshotcello'; > >>>> | > package: 'ConfigurationOfSnapshotcello'; > >>>> | > load. > >>>> | > (Smalltalk globals at: #ConfigurationOfSnapshotcello) > >>>> | > loadDevelopment > >>>> | > > >>>> | > Cheers, > >>>> | > Doru > >>>> | > > >>>> | > -- > >>>> | > www.tudorgirba.com > >>>> | > > >>>> | > "Every successful trip needs a suitable vehicle." > >>>> | > > >>>> | > > >>>> | > > >>>> | > > >>>> | > > >>>> | > _______________________________________________ > >>>> | > Moose-dev mailing list > >>>> | > Moose-dev(a)iam.unibe.ch > >>>> | > https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >>>> | > >>>> | > >>>> | _______________________________________________ > >>>> | Moose-dev mailing list > >>>> | Moose-dev(a)iam.unibe.ch > >>>> | https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >>>> | > >>> > >>> > >>> _______________________________________________ > >>> Moose-dev mailing list > >>> Moose-dev(a)iam.unibe.ch > >>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >> > >> -- > >> www.tudorgirba.com > >> > >> "From an abstract enough point of view, any two things are similar." > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

July 24, 2013