- Pharo-dev - lists.pharo.org

Pharo 6 update catalog entries
by Torsten Bergmann Feb. 7, 2017

Feb. 7, 2017

Hi, in preparation of upcoming Pharo 6 release we already should do a pass on all our external loadable projects: - load them into Pharo 6 to see if they could be loaded cleanly (due to automatic transformation of deprecated messages your packages get dirty when converted) - check if they are already/still working in Pharo 6 by using them - check that the tests are running in Pharo 6 - check that we have a proper config with catalog methods and that the latest config is in the MetaRepoForPharo60 repository http://smalltalkhub.com/#!/~Pharo/MetaRepoForPharo60 I did a pass over most projects I implemented or contributed to and we now have much more Pharo 6 based projects in catalog: - Units, Artefact - EventRecorder, Bugzilla, PunQlite, HubCap, VistaCursors, INIFile - Pomodoro, DesktopManager, QuickAccess, WebBrowser, MessageFlowBrowser - ScriptManager (now with icons) - Tealight, Teapot, Nginx, NPMJS, GitHubAPI, FogBugz - OSWindows, OSOSX, OSUnix, OSLinuxCentOS, OSLinuxUbuntu, OSRaspbian - ... You should do the same with your projects! Also if you have a project on SqueakSource, STHub or GitHub that is not yet in the catalog it would be good to provide a ConfigurationOf... with a catalog description. Using Versionner it is easy to create one or generate the required catalog methods. This would give more visibility to your projects! Thanks T.

8 16

Printing numbers in different bases
by Benoit St-Jean Feb. 7, 2017

Feb. 7, 2017

Is there a reason why we allow printing numbers in bases greater than 36?Â It makes no sense to me. For instance: 1406 printStringBase: 57.Â "O]"Â ----------------- BenoÃ®t St-Jean "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein)

1 0

Pharo 60 need help on Red-in-Dark-Theme-is-plain-bad
by Stephane Ducasse Feb. 6, 2017

Feb. 6, 2017

https://pharo.fogbugz.com/f/cases/19658/Red-in-Dark-Theme-is-plain-bad The black theme is not usable on certain screen because the red color cannot be distinguished. So when the white theme does not work for other reasons people cannot do much. They cannot read the errors. In addition since the hilighter is broken!!! bingo you cannot see anything. Super cool system.

2 1

Pharo 60 needs help on ooltips-of-the-class-button-does-not-changed
by Stephane Ducasse Feb. 6, 2017

Feb. 6, 2017

If you want to help pharo: https://pharo.fogbugz.com/f/cases/19659/Tooltips-of-the-class-button-does-n…

1 0

Pharo 60 needs help on Broken-syntax-highlithing
by Stephane Ducasse Feb. 6, 2017

Feb. 6, 2017

I'm giving some lectures to siemens engineers and .... we found glitches. (bad impression). https://pharo.fogbugz.com/f/cases/19656/Broken-syntax-highlithing

1 0

Seamless Error in GT-Inspector
by Sean P. DeNigris Feb. 6, 2017

Feb. 6, 2017

DoIt and Go: `remoteSmalltalk at: #Transcript.` In right pane: `self open` -> "MessageNotUnderstood: SeamlessRemoteClassCompilationContext>>requestorScopeClass" ----- Cheers, Sean -- View this message in context: http://forum.world.st/Seamless-Error-in-GT-Inspector-tp4933050.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

2 5

[QA] quality assurance
by Hilaire Feb. 6, 2017

Feb. 6, 2017

Hi, I discussed briefly with Steph about QA team and dedicated mailing list. He proposed to just use the @devel list with an appropriate [QA] tag, so every one can participate or just discard the topic without too much noise. I will post here about glitches I see in the UI, then depending on the feedback here and when appropriate I will open a bug ticket too on 'First impression count' tag, then propose a fix or ask for further assistance. I hope to dedicate a few hours per week on that topic. People interested on that topic could easily join too. It is a not so difficult way to learn a bit more about Pharo internal. Hilaire -- Dr. Geo http://drgeo.eu

4 3

[pharo-project/pharo-core]
by GitHub Feb. 6, 2017

Feb. 6, 2017

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

1 0

[pharo-project/pharo-core] 394af1: 60375
by GitHub Feb. 6, 2017

Feb. 6, 2017

Branch: refs/heads/6.0 Home: https://github.com/pharo-project/pharo-core Commit: 394af1e72e16fd07e051c527b87418e41e00b848 https://github.com/pharo-project/pharo-core/commit/394af1e72e16fd07e051c527… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2017-02-06 (Mon, 06 Feb 2017) Changed paths: A AST-Core.package/RBParseErrorNode.class/instance/accessing/body_.st A AST-Core.package/RBParseErrorNode.class/instance/accessing/source_.st M AST-Core.package/RBParser.class/instance/private-parsing/parseMethod.st A AST-Tests-Core.package/RBParserTest.class/instance/tests parsing/testParseFaultyMethodMessagePattern.st R BaselineOfFileTree.package/BaselineOfFileTree.class/README.md R BaselineOfFileTree.package/BaselineOfFileTree.class/definition.st R BaselineOfFileTree.package/BaselineOfFileTree.class/instance/baseline/baseline_.st M Morphic-Base.package/SystemProgressItemMorph.class/instance/private/refresh.st M Morphic-Base.package/SystemProgressMorph.class/instance/updating/refresh.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60374.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - scripts/script60375.st R ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60374.st A ScriptLoader60.package/ScriptLoader.class/instance/pharo - updates/update60375.st M ScriptLoader60.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 60375 18271 BaselineOfFileTree is in the old version https://pharo.fogbugz.com/f/cases/18271 18837 RBParser should not crash when parsing a faulty method node https://pharo.fogbugz.com/f/cases/18837 19655 Handle events during progressBar usage https://pharo.fogbugz.com/f/cases/19655 http://files.pharo.org/image/60/60375.zip

1 0

[pharo-project/pharo-core]
by GitHub Feb. 6, 2017

Feb. 6, 2017

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

1 0