- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Thanks to all of you who asked

by Sergi Reyner

2014-04-02 16:17 GMT+01:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > As you may know, an earthquake occurred yesterday evening in the north of > Chile. It was a strong one. > First news I have. Probably because I donÂ´t actually watch or read the news :D > Many of us have asked how well we are. We are all good. > Glad everyone is allright :) Cheers, Sergi

April 2, 2014

Nautilus sidebar buttons as plugin (Pharo4)

by Stephan Eggermont

Ben wrote: >Remind me a lot of lectures I had: >âToday we will see how to go on the Moon. >â¦ >This was how to fill up the tank, >the rest is left as an exerciseâ As I forgot to take the VMMaker sources with me, I was unable to work on the VM bug this afternoon and bring the Pharo3 release a bit nearer. Instead I played with Nautilus and made the SBIC buttons into a plugin https://pharo.fogbugz.com/default.asp?13167 Improvements expected: - make plugins auto-layout vertically/horizontally; - and/or limit their possible positions; - show plugins by default; - make the functionality of the SBIC buttons available somewhere in a menu. I noticed the model/model ui is not available during construction of the plugin UI. A better solution than testing for availability of the ui would be welcome. Stephan

April 2, 2014

Re: [Pharo-dev] Font problem identified

by Ben Coman

April 2, 2014

[pharo-project/pharo-core]

by GitHub

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

April 2, 2014

[pharo-project/pharo-core] af5386: 30809

by GitHub

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: af5386de4ec1a6fe9cefda688eda5c09ef7aeb89 https://github.com/pharo-project/pharo-core/commit/af5386de4ec1a6fe9cefda68… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-04-02 (Wed, 02 Apr 2014) Changed paths: A ScriptLoader30.package/ScriptLoader.class/instance/pharo - scripts/script462.st A ScriptLoader30.package/ScriptLoader.class/instance/pharo - updates/update30809.st M ScriptLoader30.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st R Versionner-Core-Commands.package/VSDevCycleCommand.class/instance/accessing/standardizeDevVersionString_.st M Versionner-Core-Commands.package/VSDevCycleCommand.class/instance/private/createDevelopmentVersion.st M Versionner-Core-Commands.package/VSReleaseDevelopmentVersionCommand.class/instance/actions/release_andSolveSymbolic_.st M Versionner-Core-Commands.package/VSRemoveCommand.class/instance/execute/execute.st M Versionner-Core-Commands.package/VSUpdateDevelopmentVersionCommand.class/instance/execute/execute.st M Versionner-Core-DependenciesModel.package/MTDevelopmentWorkfow.class/instance/private/nextDevelopmentVersionString_.st A Versionner-Core-DependenciesModel.package/MTDevelopmentWorkfow.class/instance/private/standardizeDevVersionString_.st A Versionner-Core-DependenciesModel.package/MTDevelopmentWorkfow.class/instance/private/version_.st M Versionner-Core-DependenciesModel.package/MTDevelopmentWorkfow.class/instance/protocol/nextDevelopmentVersionString.st A Versionner-Core-DependenciesModel.package/MTProject.class/class/instance creation/newFromVersion_inConfiguration_.st R Versionner-Core-DependenciesModel.package/MTProject.class/class/instance creation/newFromVersion_inRepository_.st M Versionner-Core-DependenciesModel.package/MTProject.class/class/instance creation/newNamed_withInitialVersion_inRepository_.st R Versionner-Core-DependenciesModel.package/MTVersion.class/class/as yet unclassified/fromVersionName_.st R Versionner-Core-DependenciesModel.package/MTVersion.class/class/as yet unclassified/fromVersionString_.st A Versionner-Core-DependenciesModel.package/MTVersion.class/class/instance creation/fromVersionName_.st A Versionner-Core-DependenciesModel.package/MTVersion.class/class/instance creation/fromVersionString_.st R Versionner-Core-DependenciesModel.package/MTVersion.class/instance/as yet unclassified/=.st A Versionner-Core-DependenciesModel.package/MTVersion.class/instance/comparing/=.st A Versionner-Core-Model.package/MBConfigurationInfo.class/instance/updating/recalculateSilently.st A Versionner-Spec-Browser.package/VSGroupLeafNode.class/instance/testing/hasChildren.st M Versionner-Spec-Browser.package/VSGroupNode.class/instance/accessing/childNodeClassFor_.st A Versionner-Spec-Browser.package/VSGroupNode.class/instance/testing/hasChildren.st A Versionner-Spec-Browser.package/VSPackageLeafNode.class/instance/testing/hasChildren.st A Versionner-Spec-Browser.package/VSPackageNode.class/instance/testing/hasChildren.st A Versionner-Spec-Browser.package/VSProjectLeafNode.class/instance/testing/hasChildren.st A Versionner-Spec-Browser.package/VSProjectNode.class/instance/testing/hasChildren.st M Versionner-Spec-Browser.package/VSVersionMorph.class/instance/private/build.st R Versionner-Spec-Browser.package/VersionListModel.class/instance/as yet unclassified/updateSelection.st R Versionner-Spec-Browser.package/VersionListModel.class/instance/as yet unclassified/updateSelectionVersionString.st A Versionner-Spec-Browser.package/VersionListModel.class/instance/private/developmentVersionString.st A Versionner-Spec-Browser.package/VersionListModel.class/instance/protocol/selectDevelopment.st A Versionner-Spec-Browser.package/VersionListModel.class/instance/updating/updateSelection.st A Versionner-Spec-Browser.package/VersionListModel.class/instance/updating/updateSelectionVersionString.st M Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/initialization/initializePresenter.st M Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/menu/loadMenuFor_in_.st M Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/protocol/configuration_.st A Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/refreshing/selectDevelopmentVersion.st M Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/refreshing/update.st M Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/testing/hasChanges.st A Versionner-Spec-Browser.package/VersionnerProjectBrowser.class/instance/testing/ignoreUnsavedChangesOnDevelopmentIfAny.st M Versionner-Spec-Browser.package/VersionnerProjectPackagesPanel.class/instance/actions/addPackageRequirement.st M Versionner-Spec-Browser.package/VersionnerProjectPanel.class/instance/accessing-ui/requiredProjectMenu_.st M Versionner-Spec-Browser.package/VersionnerProjectToolBar.class/instance/actions/executeWithDevWorkflow_.st M Versionner-Spec-Browser.package/VersionnerProjectToolBar.class/instance/initialization/initializePresenter.st M Versionner-Spec-Browser.package/VersionnerProjectToolBar.class/instance/initialization/initializeWidgets.st A Versionner-Spec-Browser.package/VersionnerProjectToolBar.class/instance/protocol/releaseEnabled_.st M Versionner-Spec-Browser.package/VersionnerReleasePanel.class/instance/initialization/initializeWidgets.st M Versionner-Spec-Browser.package/VersionnerReleasePanel.class/instance/private/latestVersionString.st A Versionner-Spec-Browser.package/VersionnerReleasePanel.class/instance/private/nextVersionString.st R Versionner-Tests-Core-Commands.package/VSDevCycleCommandTest.class/README.md R Versionner-Tests-Core-Commands.package/VSDevCycleCommandTest.class/definition.st R Versionner-Tests-Core-Commands.package/VSDevCycleCommandTest.class/instance/tests/testStandardizeDevVersionString.st A Versionner-Tests-Core-DependenciesModel.package/MTDevelopmentWorkfowTest.class/instance/tests/testNextDevelopmentVersionString.st A Versionner-Tests-Core-DependenciesModel.package/MTDevelopmentWorkfowTest.class/instance/tests/testStandardizeDevVersionString.st R Versionner-Tests-Core-DependenciesModel.package/MTDevelopmentWorkfowTestWithXMLParser.class/instance/tests/testNextDevelopmentVersionString.st Log Message: ----------- 30809 13143 Integrate Versionner 2.7 https://pharo.fogbugz.com/f/cases/13143 Which include these: 13056 Versioneer: MNU - receiver of treeNodeClass is nil https://pharo.fogbugz.com/f/cases/13056 13148 check if the version does not exist before creating a new development version https://pharo.fogbugz.com/f/cases/13148 13140 No tree in Versionner panes https://pharo.fogbugz.com/f/cases/13140 13144 wrong name for generated development version https://pharo.fogbugz.com/f/cases/13144 13141 List of package dependencies contains absurd values https://pharo.fogbugz.com/f/cases/13141 http://files.pharo.org/image/30/30809.zip

April 2, 2014

Thanks to all of you who asked

by Alexandre Bergel

As you may know, an earthquake occurred yesterday evening in the north of Chile. It was a strong one. Many of us have asked how well we are. We are all good. Luckily, Chile is very well prepared. Whereas a shake of 8.3 is strong enough to swipe away most of countries, Chile almost did not suffer. It happens in the north of Chile, quite far from Santiago, where most of us are based. We actually did not feel anything. Over the last few months, the Chilean ground has been shaking a lot, around Santiago. Thanks for thinking about us. You guys are great! Alexandre (in the name of all the people living in Chile part of this mailing list) -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

April 2, 2014

Re: [Pharo-dev] Don't do this X(

by Goubier Thierry

Le 02/04/2014 16:33, phil(a)highoctane.be a Ã©crit : > On Wed, Apr 2, 2014 at 4:06 PM, Goubier Thierry <thierry.goubier(a)cea.fr > <mailto:thierry.goubier@cea.fr>> wrote: > > > > Le 02/04/2014 15:59, Sebastian Sastre a Ã©crit : > > Advice: > > Never save a âbig" package using monticello (lets say ~2000 classes) > > and then save the image > > Why? > > Because while you donât have feedback of saving progress* it will be > doing something on background (forked save?) and if for any > reason you > are tempted to do an image save or save and quit, it will save in a > state that will prevent the image from opening again > > You have no option but to go to your previous image version or > something > of the kind > > :( > > *saving a package actually provides /some/ feedback on progress > but when > the progress bar finishes, the saving doesnât actually finish and it > still have something going on, so you get "silenceâ > (no-feedback) until > you get the little monticello window with your new package version > > > Does this mean that once we get the little window, we are safe? > I am saving a package with containing a lot of Pack-XXX Pack-YYY > Pack-ZZZ in a 2.0 image as a single Pack-PhilippeBack-nn.mcz thing. > > What is the moves to make to be safe? > > I already got my image locked at some points in a way that resembles > what you describe. I'm looking at the code and I don't understand everything, but, yes, it seems there are a few ways to keep doing things while saving the package (and maybe locking up things). MCWorkingCopyBrowser>>basicSaveVersionIn: basicSaveVersionIn: aRepository | newVersion waitForVersion | waitForVersion := Semaphore new. UIManager default defer: [ newVersion := workingCopy newVersionIn: aRepository. waitForVersion signal ]. Processor activeProcess == UIManager default uiProcess ifFalse: [ waitForVersion wait ]. newVersion ifNil: [ ^ self ]. Cursor wait showWhile: [[ self storeVersion: newVersion in: aRepository; storeDependencies: newVersion in: aRepository.] ensure: [ (MCVersionInspector new version: newVersion) show ]] It seems asynchronous, but I'm unsure of what it is doing. Progress bar is only displayed when doing newVersionIn:, but this is sent to the UIManager. And this is done in a fork (see saveVersion), so it's probably allways possible to interrupt the thing half-way (or save). Anybody to explain what is the objective when writing code like that? Thierry > > Phil > > I'll profile that to see what's happening. > > Thierry > -- > 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 > <tel:%2B33%20%280%29%201%2069%2008%2032%2092> / 83 95 > > -- 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

April 2, 2014

Re: [Pharo-dev] Don't do this X(

by phil＠highoctane.be

On Wed, Apr 2, 2014 at 4:06 PM, Goubier Thierry <thierry.goubier(a)cea.fr>wrote: > > > Le 02/04/2014 15:59, Sebastian Sastre a Ã©crit : > >> Advice: >> >> Never save a "big" package using monticello (lets say ~2000 classes) >> >> and then save the image >> >> Why? >> >> Because while you don't have feedback of saving progress* it will be >> doing something on background (forked save?) and if for any reason you >> are tempted to do an image save or save and quit, it will save in a >> state that will prevent the image from opening again >> >> You have no option but to go to your previous image version or something >> of the kind >> >> :( >> >> *saving a package actually provides /some/ feedback on progress but when >> the progress bar finishes, the saving doesn't actually finish and it >> still have something going on, so you get "silence" (no-feedback) until >> you get the little monticello window with your new package version >> > > Does this mean that once we get the little window, we are safe? I am saving a package with containing a lot of Pack-XXX Pack-YYY Pack-ZZZ in a 2.0 image as a single Pack-PhilippeBack-nn.mcz thing. What is the moves to make to be safe? I already got my image locked at some points in a way that resembles what you describe. Phil > I'll profile that to see what's happening. > > Thierry > -- > 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 > >

April 2, 2014

Re: [Pharo-dev] Don't do this X(

by Goubier Thierry

Le 02/04/2014 15:59, Sebastian Sastre a Ã©crit : > Advice: > > Never save a âbig" package using monticello (lets say ~2000 classes) > > and then save the image > > Why? > > Because while you donât have feedback of saving progress* it will be > doing something on background (forked save?) and if for any reason you > are tempted to do an image save or save and quit, it will save in a > state that will prevent the image from opening again > > You have no option but to go to your previous image version or something > of the kind > > :( > > *saving a package actually provides /some/ feedback on progress but when > the progress bar finishes, the saving doesnât actually finish and it > still have something going on, so you get "silenceâ (no-feedback) until > you get the little monticello window with your new package version I'll profile that to see what's happening. Thierry -- 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

April 2, 2014

Don't do this X(

by Sebastian Sastre

Advice: Never save a âbig" package using monticello (lets say ~2000 classes) and then save the image Why? Because while you donât have feedback of saving progress* it will be doing something on background (forked save?) and if for any reason you are tempted to do an image save or save and quit, it will save in a state that will prevent the image from opening again You have no option but to go to your previous image version or something of the kind :( *saving a package actually provides some feedback on progress but when the progress bar finishes, the saving doesnât actually finish and it still have something going on, so you get "silenceâ (no-feedback) until you get the little monticello window with your new package version

April 2, 2014