January 2014 - Pharo-dev - lists.pharo.org

Concerts of Iron Maiden Analyzed

by Alexandre Bergel

Load Roassal to enjoy Dowser, a relational tower visualization. The following expression relates the year and locations of Iron Maidenâs concerts: RODowserExample new example10 More Screenshots available on: https://www.facebook.com/media/set/?set=a.567893596630575.1073741840.340543… Thanks Ricardo for this excellent piece of work! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 4, 2014

Re: [Pharo-dev] Unifying Testing Ideas

by Sean P. DeNigris

Denis Kudriashov wrote > Problem with TestCase approach is mixing two separate concerns. First is > how we want to define system specifications. Another is how we can persist > such specifications. > ... > So it is my vision. I really want to build such system but I have no time > for this yet. > Maybe Sean doing something similar? Yes, yes, yes!!! This is something I've been working on and thinking about since I came to Smalltalk. Right now we have something like: 1. Use standard Smalltalk artifacts and tools to write serialized descriptions of tests 2. Have SUnit automagically create live test objects, which we never really see or reason about 3. Use some Test-specific tools, like TestRunner and Nautilus icons This is writing in "testing assembly language". We work with the serialized implementation details, which then bubble up all the way to the UI i.e. TestRunner lists Packages in the left pane, and TestCase subclasses in the next, neither of which have anything to do with the domain of testing. It's similar to the way we encode files (e.g. images) as strings returned by methods because we can't version them easily with Monticello. Every time I try to create "what TDD/BDD would look like in a live, dynamic environment", I start with a custom test creation UI and work backward. The UI creates a testing domain model, which may be serialized as packages, classes, and methods, but neither the test writer, runner, or reader should ever have to deal with them directly. I have had quite a few false starts, but have learned a lot. I think a real testing domain model could create huge leverage for our community. In fact I came to Smalltalk from Ruby because I instantly recognized that manipulating text via files and command line had missed the point. In short, when you're ready, I'd love to collaborate... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Unifying-Testing-Ideas-tp4726787p4734239.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 4, 2014

Head over to Youtube and Reddit to show Adele Goldberg some love!!

by vfclists .

There is a post on reddit, http://www.reddit.com/r/programming/comments/1udl9x/adele_goldberg_intervie… an interview with Adele Goldberg at http://www.youtube.com/watch?v=IGNiH85PLVg and it isn't seeing much activity. Folks ought to head over and show her some love. She is the First Lady of Smalltalk you know. If it was Alan Kay or Martin Odersky the comments and views would be in 1000s. No wonder Smalltalk appears to be dying. Not enough loyal devotees ready to worship at they feet of their Goddess,:) -- Frank Church ======================= http://devblog.brahmancreations.com

Jan. 4, 2014

Re: [Pharo-dev] Feature for request for GraphET?

by Tudor Girba

Here is one thing I would want: a correspondent Graph-ET functionality to make something like this EyeSee script work as in the first attached picture. renderer := ESDiagramRenderer new. grouped := { #item1->{10 . 12 . 11 . 14 } . #item2-> { 1 . 1 . 20 } . #item3->{ 1 . 1 . 1 . 1 . 1} }. diag := (ESVerticalBarDiagram new) identifier: [:each | each key ]; y: [:each | each value size]; yAxisLabel: 'Count'; valueAxis; rightYAxis; defaultColor: Color veryVeryLightGray; axisColor: Color veryVeryLightGray; models: grouped; rotatedLabels: true; yourself. diag2 := (ESVerticalBarDiagram new) y: [:each | each value sum]; regularAxis; yAxisLabel: 'Sum'; gapFraction: 2 / 3; defaultColor: (Color red); axisColor: (Color red); models: grouped; yourself. (renderer compositeDiagram) add: diag; add: diag2. renderer open [image: Inline image 2] The best I could produce with Graph-ET is this (I commented out the message to which I did not find a correspondent): builder := GETDiagramBuilder new. grouped := { #item1->{10 . 12 . 11 . 14 } . #item2-> { 1 . 1 . 20 } . #item3->{ 1 . 1 . 1 . 1 . 1} }. diag := (GETVerticalBarDiagram new) "identifier: [:each | each key ];" y: [:each | each value size]; yAxisLabel: 'Count'; valueAxisLine; "rightYAxis;" color: Color veryLightGray; "axisColor: Color veryLightGray;" models: grouped; "rotatedLabels: true;" yourself. diag2 := (GETVerticalBarDiagram new) y: [:each | each value sum]; regularAxis; yAxisLabel: 'Sum'; "gapFraction: 2 / 3;" color: (Color red); "axisColor: (Color red);" models: grouped; yourself. (builder compositeDiagram) add: diag; add: diag2. builder open [image: Inline image 4] Cheers, Doru On Thu, Jan 2, 2014 at 7:24 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > Hi! > > Daniel is looking for usage scenarios with GraphET. It would be great to > hear about your need. > Currently, we will work on: > - PDF Export using Artefact > - support for legend > - smarter way to put labels on axis > > Anything else? > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 4, 2014

FFTPlugin is NOT available?

by NISHIHARA Satoshi

FFTPlugin is NOT available? Gofer new smalltalkhubUser: 'PharoExtras' project: 'Sound'; package: 'ConfigurationOfPharoSound'; load. ((Smalltalk at: #ConfigurationOfPharoSound) project version: '6.1') load. CogFamilyCocoaIOSConfig>>defaultInternalPlugins says: FFTPlugin is a InternalPlugin also SoundPlugin. do it: SoundPlayer primSoundAvailableBytes --> 42304 OK. but (FFT new nu: 12) pluginTransformData: true. --> PrimitiveFailed: primitive #pluginTransformData: in FFT failed VM: Pharo-293.app VI: Pharo-30671 Mac OS X regards -- -- "NISHIHARA Satoshi" [:goonsh :nsh | ^ nishis perform: goonsh with: nsh]

Jan. 4, 2014

Re: [Pharo-dev] Spotlight Demo

by Sebastian Sastre

On Jan 4, 2014, at 4:06 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Thanks :) currently, it limits each group to show 7 results. And for messages, it opens an implementors browser, so #asString is only one result, no matter how many classes implement it. That being said, it is highly configurable. One could add a Methods group that does what I think you want... Get it. Clever. 7 is a great number as limit. Can't wait to have Pharo with that :D

Jan. 4, 2014

Re: [Pharo-dev] Spec TabModel and Morphic adaptor...

by Benjamin

Erwan was doing it, so I guess it was working (at some point) I can not tell you without having a deeper look Ben On 04 Jan 2014, at 15:06, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > â¦ and I seeing a log of small details that teach me that probably TabManagerModel, etc. are not being really used, more than a basic usage (otherwise, I do not understand how can be working). > > Why iâm trying to do is dynamic add/remove of tabs. > > Esteban > > On 04 Jan 2014, at 16:44, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> >> On 04 Jan 2014, at 16:39, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: >> >>> The should be a dispatch to not expose widget in: >>>> aTab buildWidget widget >>> >>> Then, this >>>> aTab ensureMorphicAdapter asWidget >>> >>> looks really weird. >>> >>> Could you provide more info about the DNU or should I try to read your mind? :P >> >> it just says that aTab (which is a TabModel) DNU buildWidget. >> >> btwâ¦ I think it MorphicTabManagerAdapter also misses: >> >> removeTab: aTab >> aTab ensureMorphicAdapter asWidget delete. >> >> (or something like that) >> >>> Ben >>> >>> On 04 Jan 2014, at 12:36, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>>> Hi, >>>> >>>> I was playing with Spec and I ran into a DNU problem when trying to add dynamically tabs. Looks for me that this: >>>> >>>> addTab: aTab >>>> >>>> self widgetDo: [ :w | w addTab: aTab buildWidget widget ] >>>> >>>> should instead be: >>>> >>>> addTab: aTab >>>> >>>> self widgetDo: [ :w | w addTab: aTab ensureMorphicAdapter asWidget ] >>>> >>>> but not sure aboutâ¦ >>>> The problem is that original form works fine if adding static (on original initialisation)â¦ >>>> >>>> Esteban >>> >> >

Jan. 4, 2014

Re: [Pharo-dev] copyscript from squeaksource to smalltalkhub

by StÃ©phane Ducasse

Hi johan you have them in the gofer book chapter here are some that I tweak. Stef | go repo | go := Gofer new. repo := MCSmalltalkhubRepository owner: 'Pharo' project: 'Pharo30' user: 'StephaneDucasse' password: ''. go repository: repo. "#('Nautilus' 'NautilusCommon' 'NautilusRefactoring' 'GroupManager' 'GroupManagerUI') do: [ :nam| " ((go allResolved select: [ :each | '*GroupManager*' match: each packageName]) groupedBy: #packageName) keys do: [ :pack | pack crLog. go package: pack ; fetch] | goin goout repo | goin := Gofer new. goin squeaksource3: 'Pharo20'. goin package: 'BLB'; fetch. goout := Gofer new. repo := MCSmalltalkhubRepository owner: 'Pharo' project: 'Pharo20' user: 'StephaneDucasse' password: ''. goout repository: repo. go := Gofer new. go repository: repo. (((FileSystem disk workingDirectory / 'package-cache') allFiles select: [:each | '*.mcz' match: each basename]) groupedBy: [:each | (each base copyUpToLast: $-) ]) keys do: [ :name | name crLog. go package: name; push] | goin goout repo | goin := Gofer new. goin squeaksource3: 'Pharo14'. goout := Gofer new. repo := MCSmalltalkhubRepository owner: 'Pharo' project: 'Pharo14' user: 'StephaneDucasse' password: 'sn00py_papa'. goout repository: repo. #( S T U V W X Y Z) do: [ :nam | 'FETCHING' crLog. (goin allResolved select: [ :each | nam, '*' match: each packageName]) do: [ :pack | self crLog: pack packageName. goin package: pack packageName; fetch].]. ====================================================================================================== | goin goout repo |goin := Gofer new. goin squeaksource3: 'Pharo14'. goout := Gofer new. repo := MCSmalltalkhubRepository owner: 'Pharo' project: 'Pharo14' user: 'StephaneDucasse' password: 'sn00py_papa'. goout repository: repo. 'FETCHING' crLog. (goin allResolved select: [ :each | 'S*' match: each packageName]) do: [ :pack | self crLog: pack name. goin package: pack packageName; fetch] ===================================================================================================== | goin goout repo | goin := Gofer new. goin squeaksource3: 'Pharo14'. goout := Gofer new. repo := MCSmalltalkhubRepository owner: 'Pharo' project: 'Pharo14' user: 'StephaneDucasse' password: ''. goout repository: repo. #(A B C D E F G H IJ K L M N O P Q R S T U V W X Y Z) do: [ :nam | 'FETCHING' crLog. (goin allResolved select: [ :each | nam, '*' match: each packageName]) do: [ :pack | self crLog: pack packageName. goin package: pack packageName; fetch].].

Jan. 4, 2014

Re: [Pharo-dev] copyscript from squeaksource to smalltalkhub

by Sean P. DeNigris

hilaire wrote >> Does anyone still have the script to copy a repository from squeaksource >> to smalltalkhub? It would be good to host it on stub itself for safekeeping... ----- Cheers, Sean -- View this message in context: http://forum.world.st/copyscript-from-squeaksource-to-smalltalkhub-tp473418… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 4, 2014

[pharo-project/pharo-core]

by GitHub

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

Jan. 4, 2014