- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [Bloc] MDLColor and new gradient

by Glenn CavarlÃ©

Hi, In my memories, a first implementation of material colors was also made by Alex in Brick packages. This can be a inspiration source, too. ----- Glenn CavarlÃ© -- View this message in context: http://forum.world.st/Bloc-MDLColor-and-new-gradient-tp4879795p4880198.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 24, 2016

Re: [Pharo-dev] [Moose-dev] Call for action for Roassal

by Alexandre Bergel

> - the possibility to place hangout of the edges on nodes (as box) more flexible. Indeed, I am reverse engineering a database containing around 80 tables and lot of foreign keys and the result is not readable since the edge are orthogonal starting from the top or the bottom of the box corresponding to the column name. I would like a real entity-relation diagram. Do you have a screenshot showing the issue? > If you want, I can show you the current stage of the visu (once again done in Telescope on top of Roassal) in order that you see on real data how uggly it is. Yes please, some screenshots would help Alexandre > > Cheers, > Anne > >> Le 24 fÃ©vr. 2016 Ã 09:51, Alexandre Bergel <alexandre.bergel(a)me.com> a Ã©crit : >> >> Dear community, >> >> As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: >> >> What are the 3 aspects you would like to see improved in Roassal? >> >> You can answer publicly or by sending private messages. >> >> Kind regards, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)list.inf.unibe.ch >> https://www.list.inf.unibe.ch/listinfo/moose-dev > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 24, 2016

Re: [Pharo-dev] [Moose-dev] Call for action for Roassal

by Anne Etien

Hi Alexandre, In a wonderful world, I would like: - a real graph layout (like in graphviz) that can take into account around hundred nodes and several hundred of edges and place the nodes in order to see something. Currently, I have to use the circle layout and it looks strange. - the possibility to place hangout of the edges on nodes (as box) more flexible. Indeed, I am reverse engineering a database containing around 80 tables and lot of foreign keys and the result is not readable since the edge are orthogonal starting from the top or the bottom of the box corresponding to the column name. I would like a real entity-relation diagram. For the remainder, I use only Telescope since I have just to specify my data and not to script the visualization taking into account the order of the instructionsâ¦ So donât change the interface of the existing API in order we can continue to use Telescope on top on Roassal. If you want, I can show you the current stage of the visu (once again done in Telescope on top of Roassal) in order that you see on real data how uggly it is. Cheers, Anne > Le 24 fÃ©vr. 2016 Ã 09:51, Alexandre Bergel <alexandre.bergel(a)me.com> a Ã©crit : > > Dear community, > > As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: > > What are the 3 aspects you would like to see improved in Roassal? > > You can answer publicly or by sending private messages. > > Kind regards, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev

Feb. 24, 2016

Re: [Pharo-dev] [pharo-project/pharo-core] 91c994: 50605

by Marcus Denker

> > Log Message: > ----------- > 50605 > Moose > > http://files.pharo.org/image/50/50605.zip > > this is 17659 GTPlayground does not highlight defined implicit variables https://pharo.fogbugz.com/f/cases/17659/ 17656 Spotter should sort search results https://pharo.fogbugz.com/f/cases/17656/ 17668 Spotter should allow filtering categories that have space https://pharo.fogbugz.com/f/cases/17668/ Marcus

Feb. 24, 2016

Re: [Pharo-dev] Starting to add class comment and test on BlElements

by Glenn CavarlÃ©

Hi Stef, Yes, BlElement is the starting point, i think so. All examples in BlElement run for me, do you have some errors ? On my side, i'm starting to write examples using layouts. We can talk about the performances issue later (if asserts really have an impact on) , when the first stable version will be released. But for now, i think using asserts is a good choice to make things clear and to help the understanding and the documentation (same for the <return> pragma). Glenn. ----- Glenn CavarlÃ© -- View this message in context: http://forum.world.st/Starting-to-add-class-comment-and-test-on-BlElements-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Feb. 24, 2016

[pharo-project/pharo-core]

by GitHub

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

Feb. 24, 2016

[pharo-project/pharo-core] 91c994: 50605

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 91c994b57d1070c33831a3dc85cbeee58f77d06e https://github.com/pharo-project/pharo-core/commit/91c994b57d1070c33831a3dc… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-02-24 (Wed, 24 Feb 2016) Changed paths: M ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version32_.st M ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version32_.st M ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic versions/stable_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version22_.st M ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGToolkitCore.package/ConfigurationOfGToolkitCore.class/instance/versions/version313_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version43_.st M GT-Spotter.package/GTFilterSubstring.class/instance/private/applyFilterWithQuery.st A GT-Spotter.package/GTFilterSubstring.class/instance/private/indexForItemName_andQuery_.st R GT-Spotter.package/GTFilterSubstring.class/instance/private/indexForItem_.st M GT-Spotter.package/GTSpotterCandidatesListProcessor.class/definition.st A GT-Spotter.package/GTSpotterCandidatesListProcessor.class/instance/accessing/sort.st A GT-Spotter.package/GTSpotterCandidatesListProcessor.class/instance/scripting/sort_.st A GT-Spotter.package/GTSpotterCategoryBrick.class/instance/adding/addItem_.st A GT-Spotter.package/GTSpotterCategoryBrick.class/instance/adding/addItems_.st R GT-Spotter.package/GTSpotterCategoryBrick.class/instance/as yet unclassified/addItem_.st M GT-Spotter.package/GTSpotterHelp.class/class/accessing/pages.st A GT-Spotter.package/GTSpotterHelp.class/class/documentation/basicExamples.st A GT-Spotter.package/GTSpotterHelp.class/class/documentation/categoryFilterExamples.st A GT-Spotter.package/GTSpotterHelp.class/class/documentation/diveInCategoryExamples.st A GT-Spotter.package/GTSpotterHelp.class/class/documentation/diveInExamples.st A GT-Spotter.package/GTSpotterHelp.class/class/documentation/extensionExamples.st M GT-Spotter.package/GTSpotterHelp.class/class/documentation/extensions.st M GT-Spotter.package/GTSpotterHelp.class/class/documentation/extensionsString.st A GT-Spotter.package/GTSpotterResultsBrick.class/instance/adding/addItems_to_.st M GT-Spotter.package/GTSpotterResultsBrick.class/instance/event handling/onAllCandidatesAdded_.st M GT-Spotter.package/GTSpotterStep.class/instance/private/basicRelevantProcessorsProcess_do_.st A GT-Spotter.package/GTSpotterStep.class/instance/private/processor_isRelevantForQuery_.st M Glamour-Morphic-Renderer.package/GLMMorphicPharoScriptRenderer.class/instance/rendering/morph.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50604.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50605.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50604.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50605.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50605 Moose http://files.pharo.org/image/50/50605.zip

Feb. 24, 2016

Re: [Pharo-dev] How was BoxedFloat64 integrated into the image ?

by Nicolai Hess

2016-02-24 9:31 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > > > 2016-02-23 8:48 GMT+01:00 Nicolai Hess <nicolaihess(a)gmail.com>: > >> >> >> 2016-02-23 3:55 GMT+01:00 Eliot Miranda <eliot.miranda(a)gmail.com>: >> >>> Hi Nicolai, >>> >>> there is a hairy script that moves methods around the hierarchy. >>> IIRC Float is renamed to BoxedFloat64, then a new Float is introduced, then >>> BoxedFloat64 made to inherit from it. It's likely that the last step of >>> this script, which replaces the methodClassAssociations in the moved >>> methods (makes those BoxedFloat64 methods that used to be Float or maybe >>> vice verse) with the right association, didn't work. >>> >>> I don't know how the Pharo 5 image is built. If it is incremental then >>> just write a script to fix the associations. But if the image is produced >>> by a bootstrap you'll need to track down the script that creates the >>> revised Float hierarchy and fix it to work properly in Pharo. >>> >>> _,,,^..^,,,_ (phone) >>> >> >> Thanks Eliot, >> >> The methods for c lass Float and BoxedFloat are looking fine. Whats wrong >> is, that some other methods referring to class Float in there source, now >> having >> BoxedFloat in its compiled method literal array, >> #BoxedFloat64->BoxedFloat64 instead of #Float->Float. >> >> But it looks like recompiling the whole image fixes this. >> >> nicolai >> > > > Would it makes sense if > BoxedFloat64 species returns Float ? > This is because I am about to fix some failing tests in pharo. Tests like self assert: result class = Float can be replaced by self assert: result isFloat But for tests like self assert: resultClass = Float I don't want to write self assert: resultClass = BoxedFloat64 and looking for an easy way to check if the result class is "like" Float self assert: resultClass species = Float species ? self assert: resultClass isFloatClass ? self assert: resultClass new isFloat ? any ideas > > >> >> >>> >>> On Feb 18, 2016, at 2:47 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: >>> >>> Because we have compiled methods with BoxedFloat64 associations in the >>> methods literals, but the source code still shows only "Float". >>> >>> 17638 >>> <https://pharo.fogbugz.com/f/cases/17638/Browsing-calls-on-BoxedFloat64-show…> >>> Browsing calls on BoxedFloat64 shows methods with reference to BoxedFloat64 >>> in the code >>> >>> >>> >>> >> >

Feb. 24, 2016

Call for action for Roassal

by Alexandre Bergel

Dear community, As you may have seen, Roassal has entered a stabilization phase. The book AgileVisualization.com will soon be released. After its release, Roassal will go over a new development phase. In order to prepare it, I am asking this question: What are the 3 aspects you would like to see improved in Roassal? You can answer publicly or by sending private messages. Kind regards, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 24, 2016

Re: [Pharo-dev] [regression reporter]regression occurred

by Max Leske

OS X 10.11.3 ./pharo Pharo.image test --junit-xml-output '^(?!Metacello)(?!NativeBoost)[M-Z].*' 4146 run, 4122 passes, 17 failures, 7 errors. Output from the CI build: 4146 run, 4121 passes, 17 failures, 8 errors. > On 24 Feb 2016, at 09:07, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > The following test seems to be failing a lot lately on the CI infrastructure, yet it always succeeds for me on my machine. Is there anybody who sees this fail on their machines ? > >> On 24 Feb 2016, at 08:36, no-reply(a)ci.inria.fr wrote: >> >> https://ci.inria.fr/pharo/job/Pharo-5.0-Update-Step-2.1-Validation-M-Z/labe… >> >> 1 regressions found. >> Zinc.Zodiac.ZnHTTPSTests.testAmazonAWS > >

Feb. 24, 2016