April 2018 - Pharo-users - lists.pharo.org

"News" section of the website down
by Mathieu Dubois April 9, 2018

April 9, 2018

Hello, I don't know how to report that but for several weeks (maybe months), I can't reach the "News" section of the website (I have tried from several locations with different ISP). I usually get a timeout error (error 524 from Cloudflare) that comes from pharo.org. Mathieu

1 1

[ann] gt diagrammer
by Tudor Girba April 8, 2018

April 8, 2018

Hi, We are happy to announce an initial version of GT Diagrammer, an engine for constructing diagrams interactively. This is the newest addition to the next generation GT built on Bloc. It looks like this: https://twitter.com/feenkcom/status/976341449267531776 We chose to work on Diagrammer for multiple reasons. First, developers often need to create hand built diagrams to communicate intentions, and an integrated experience should not require us to leave our environment to create them. At the same time, Diagrammer is an application that requires a widgets and interactions, and thus it is a nice exercise for Bloc and Brick. One requirement we had from the beginning was to make it work with any Bloc element. This means that the editing part had to be reasonably generic. To this end, we now have elements that can define visual editors. This is somewhat a combination between Magritte descriptions, and inspector extensions. An interesting side effect is that now we can edit visual properties when inspecting any element. In other words, we got the basic infrastructure of a UI painter. It looks like this: https://twitter.com/feenkcom/status/982656456968241152 The user interface essentially relies on two widgets: scrollable list and toggle button. While the visual look of the toggle button is inspired from material design, the most interesting part is that now we have an implementation for controlling looks per element instance. A key issue here is that looks can react to events coming from the element and inject visual attributes and possible even change behavior (for example, changing an icon while pressing a button). We will post more about looks soon. We now also have a nice solution for overlays. For example, we have an overlay showing selection and an overlay for resizing elements. Perhaps less obvious, Diagrammer also offers a basic infrastructure for the area of visual languages. As Diagrammer works with any Bloc elements, we can simply create dedicated visual elements. As an example, Diagrammer comes with an implementation of a UML class figure. Furthermore, as the functionality does not impose a specific model, custom language semantics can be mapped on visual actions. There are several things to do still for it to become a mature solution. An important next step is to serialize a diagram scene in a reproducible manner. Currently, the diagram (or any element) can be exported as pdf (https://twitter.com/feenkcom/status/976580153802358786) svg (https://twitter.com/feenkcom/status/976578060429484032) png, gif or jpeg by directly using the low level canvas. However, for the diagram to be truly useful we need to store the result in either code or another reloadable form such as STON. Other future directions are related to figure controlling (for example, custom anchors or line bending points) and to enhanced editors. To play with it, the easiest way is to download the new GT in a Pharo 6.1 image: Metacello new baseline: 'GToolkit'; repository: 'github://feenkcom/gtoolkit/src'; load. And then inspect: GtDiagrammerElement new Cheers, The feenk team -- www.tudorgirba.com www.feenk.com "Presenting is storytelling."

2 2

Did magritte change? Magritte-Morph-SeasnDeNigris.95 is not found
by Stephane Ducasse April 7, 2018

April 7, 2018

Because now when I load pillar Metacello new baseline: 'Pillar'; repository: 'github://pillar-markup/pillar:newpipeline/src'; load I get an error because Magritte-MOrph-SeasnDeNigris.95 is not found So I cannot build pillar anymore! :(

1 0

Slower
by Hilaire April 7, 2018

April 7, 2018

Hi, I discover this Dr. Geo Smalltalk sketch to animate is about 60% slowler on P7 compare to P3: | fig point comment x y random inArc tries| "Monte-Carlo PI approximation" fig := DrGeoCanvas new fullscreen scale: 400. fig arcCenter: 0@0 from:Â 1@0 to: 0@1. fig polygon: { 0@0. 0@1. 1@1. 1@0 }. comment := fig texte: '' a: 0@ -0.1. random := Random seed: Time millisecondClockValue. tries := 500. inArc := 0. [1 a: tries faire: [: try | Â Â Â x := random next. Â Â Â y := random next. Â Â Â point := (fig point: x@y) small. Â Â Â (x squared + y squared) > 1 Â Â Â Â Â Â ifTrue: [point color: Color blueÂ ] Â Â Â Â Â Â ifFalse: [inArc := inArc + 1 ]. comment text: 'Tries: ', try asString, ' approx: ', (inArc * 4 / try) asFloat asString. World doOneCycle. ] ] timeProfile The log are enclosed to compare. The mains differences seems to be during the world update. Years ago when porting to P3 I also see an important time performance degradation[1] and it remained unresolved. [1] http://forum.world.st/Slowness-question-tt4761717.html -- Dr. Geo http://drgeo.eu

6 14

line drawing bug
by joe＠boremaj.net April 7, 2018

April 7, 2018

Hello everyone! Im trying use the balloon canvas to draw some nice smooth anti aliased lines, but now i seem to have hit upon a bug which i dont know how to fix. if i draw just lines i get everything i want. Â but if i add a âdrawString:â¦â in there at any point, all the lines i try to draw subsequently dont show up. Here is code that shows the exact issue: > form := Form extent: 100@100 depth: 32. > form fillWhite. > canvas := BalloonCanvas on: form. > canvas aaLevel: 4. > "canvas := FormCanvas on: form." > points := { {10@10 . 50@43} . {50@42 . 90@75} . {90@75 . 50@90 } }. > > points do: [ :p | > Â Â canvas drawPolygon: p > Â Â Â color: Color transparent > Â Â Â borderWidth: 1 > Â Â Â borderColor: Color red. > > Â Â canvas drawString: p first asString > Â Â Â at: p first > Â Â Â font: nil > Â Â Â color: Color green. > ]. > > morph := ImageMorph new. > morph image: form. > morph openCenteredInWorld. if i comment out the canvas drawstring i get what you would expect: a squiggly line. if i add in the drawstring, the first line shows up but all the subsequent lines do not get drawn. Â (both images attached) I spent a bunch of time tracking it down to its most purest form and then a bunch of time debugging it and im out of my depth with the baloon code, i cant seem to figure out whats wrong. Â if anyone knows whats wrong or can give me a clue on how to fix it iâd greatly appreciate it. thanks in advance. { jb }

7 11

Plans for XSD in XML(Parser) the foreseeable future?
by Peter UhnÃ¡k April 7, 2018

April 7, 2018

Hi, are there any plans in the foreseeable future to add support for XSD to the XML (Parser) ecosystem? Thanks, Peter

2 2

configurable space in XML Writer tag
by Peter UhnÃ¡k April 7, 2018

April 7, 2018

Hi, what would be the best approach to not generate space at the end of single tag? Right now it generates <item /> but I would like <item/> The space is added in XMLTagWriter>>writeEpilogue, but to "cleanly" change it I would need to * subclass tag writer * subclass xml writer * figure out how to provide different writer so it plays with XMLDocument>>printOn: and that certainly doesn't feel like a nice approach. Maybe this can be made configurable in similar fashion to indentation? Thanks, Peter

2 2

Failure with GitFileTree commiting changes in Traits
by Rafael Luque April 5, 2018

April 5, 2018

Hello all, I'm getting the below error each time a try to commit changes in Traits in a project that uses GitFileTree and Pharo 6.0. I've noticed that ConfigurationOfGitFileTree loads (for Pharo 6.0) FileTree from: github://dalehenrich/filetree:pharo6.0_dev/repository/ If I update to use the "pharo6.0" branch instead of "pharo6.0_dev" then I can commit the changes without error. By the way, should not the "stable" version of GitFileTree depends on an stable branch of FileTree, instead of the development branch? This is the stack trace of the error I get: ===== UndefinedObject(Object)>>doesNotUnderstand: #select:thenCollect: MCTraitDefinition(MCClassDefinition)>>selectVariables: MCTraitDefinition(MCClassDefinition)>>instVarNames MCGitFileTreeWriter>>buildClassDefinition: MCGitFileTreeWriter>>writeClassDefinition:in: [ :each | self writeClassDefinition: each in: aPackagePath , '/' , each className , '.class' ] in MCGitFileTreeWriter>>writeClassDefinitions:in: OrderedCollection>>do: MCGitFileTreeWriter>>writeClassDefinitions:in: [ :job | job title: 'Building snapshot'. orderedDefinitions := MCDependencySorter sortItems: aSnapshot definitions. job progress: 0.1. classDefinitions := orderedDefinitions select: [ :e | e isKindOf: MCClassDefinition ]. traitDefinitions := orderedDefinitions select: [ :e | (e isKindOf: MCTraitDefinition) or: [ e isKindOf: MCClassTraitDefinition ] ]. classAndTraitNames := (classDefinitions , traitDefinitions collect: [ :e | e className ]) asSet. job progress: 0.2. methodDefinitions := orderedDefinitions select: [ :e | (e isKindOf: MCMethodDefinition) and: [ classAndTraitNames includes: e className ] ]. extensionMethodDefinitions := orderedDefinitions select: [ :e | (e isKindOf: MCMethodDefinition) and: [ (classAndTraitNames includes: e className) not ] ]. organization := orderedDefinitions select: [ :e | e isKindOf: MCOrganizationDefinition ]. extensionClasses := (extensionMethodDefinitions collect: [ :e | e className ]) asSet. job progress: 0.3. self outputFileDelete: aPackagePath. self writePackageGitPropertiesIn: aPackagePath. self writeOrganization: organization in: aPackagePath. job progress: 0.4. self writeClassDefinitions: classDefinitions in: aPackagePath. self writeTraitDefinitions: traitDefinitions in: aPackagePath. job progress: 0.5. self writeMethodDefinitions: methodDefinitions in: aPackagePath. job progress: 0.6. self writeExtensionClassDefinitions: extensionClasses in: aPackagePath. self writeExtensionMethodDefinitions: extensionMethodDefinitions in: aPackagePath. job progress: 0.7. self writeInitializers: methodDefinitions in: aPackagePath ] in MCGitFileTreeWriter>>writeSnapshot:in: BlockClosure>>cull: [ ^ block cull: self ] in [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run [ activeProcess psValueAt: index put: anObject. aBlock value ] in CurrentJob(DynamicVariable)>>value:during: BlockClosure>>ensure: CurrentJob(DynamicVariable)>>value:during: CurrentJob class(DynamicVariable class)>>value:during: [ self prepareForRunning. CurrentJob value: self during: [ ^ block cull: self ] ] in Job>>run BlockClosure>>ensure: Job>>run MCGitFileTreeWriter>>writeSnapshot:in: [ :each | | packageDir | packageDir := subDirectoryString , each package name , '.package'. aWriter writeSnapshot: each snapshot in: packageDir. aWriter outputFileModify: packageDir , '/monticello.meta/package' with: '(name ''' , each package name , ''')'. aWriter writeDependencies: each dependencies in: packageDir ] in MCGitFileTreeWriter class>>fileOutAll:on: OrderedCollection>>do: MCGitFileTreeWriter class>>fileOutAll:on: MCFileTreeGitRepository>>fiStoreVersions: MCFileTreeGitRepository>>fiStoreVersion: MCFileTreeGitRepository>>basicStoreVersion: MCFileTreeGitRepository(MCRepository)>>storeVersion: MCFileTreeGitRepository(MCFileBasedRepository)>>storeVersion: MCWorkingCopyBrowser>>storeVersion:in: [ self storeVersion: newVersion in: aRepository; storeDependencies: newVersion in: aRepository ] in [ [ self storeVersion: newVersion in: aRepository; storeDependencies: newVersion in: aRepository ] ensure: [ (MCVersionInspector new version: newVersion) show ] ] in MCWorkingCopyBrowser>>basicSaveVersionIn: BlockClosure>>ensure: [ [ self storeVersion: newVersion in: aRepository; storeDependencies: newVersion in: aRepository ] ensure: [ (MCVersionInspector new version: newVersion) show ] ] in MCWorkingCopyBrowser>>basicSaveVersionIn: BlockClosure>>ensure: CursorWithMask(Cursor)>>showWhile: MCWorkingCopyBrowser>>basicSaveVersionIn: [ self basicSaveVersionIn: self repository ] in MCWorkingCopyBrowser>> saveVersion [ self value. Processor terminateActive ] in BlockClosure>>newProcess ==== Thank you in advance.

3 7

CFP - IWST 2018 - International Workshop on Smalltalk Technologies
by Stephane Ducasse April 5, 2018

April 5, 2018

CFP - IWST 2018 - International Workshop on Smalltalk Technologies [Please accept our apologies if you receive multiple copies of this call] [Please send to interested colleagues / mailing-lists] ************************************************************************************************************ CALL FOR PAPERS IWST 2018 â International Workshop on Smalltalk Technologies http://esug.org/wiki/pier/Conferences/2018/International-Workshop-IWST_18 Cagliari, Italy; Between September 10th and 14th, 2018 ************************************************************************************************************ ------------------- Goals and scopes ------------------- The goals of the workshop is to create a forum around advances or experience in Smalltalk and to trigger discussions and exchanges of ideas. The topics of your paper can be on all aspect of Smalltalk, theoretical as well as practical. Participants are invited to submit research articles or industrial papers. This year we want to open two different tracks: one research track and one industrial track with less scientific constraints. We expect papers of three kinds: Short position papers describing emerging ideas Long research papers with deeper description of experiments and of research results. Industrial papers with presentation of real and innovative Smalltalk applications; this kind of paper should enlighten why Smalltalk is really appropriate for your application. We will not enforce any length restriction. -------------------- Important Dates -------------------- Submission deadline: June 15th, 2018 Notification deadline: July 20th, 2018 Workshop : between September 10th and 14th, 2018 All accepted papers will be published in ACM DL (To be confirmed) ------------------- Topics ------------------- We welcome contributions on all aspects, theoretical as well as practical, of Smalltalk related topics such as: -Aspect-oriented programming, -Design patterns, -Experience reports, -Frameworks, -Implementation, new dialects or languages implemented in Smalltalk, -Interaction with other languages, -Meta-programming and Meta-modeling, -Tools ------------------- Best Paper Award ------------------- To encourage the submission of high-quality papers, the IWST organizing committee is very proud to announce a Best Paper Award for this edition of IWST. We thank the Lam Research Corporation for its financial contribution which makes it possible for prizes for the three best papers: 1000 USD for first place, 600 USD for second place and 400 USD for third place. The ranking will be decided by the program committee during the review process. The awards will be given during the ESUG conference social event. The Best Paper Award will take place only with a minimum of six submissions. Notice also that to be illegible, a paper must be presented at the workshop by one of the author and that the presenting author must be registered at the ESUG conference. ------------------- Publication ------------------- Both submissions and final papers must be prepared using the ACM SIGPLAN 10 point format. Templates for Word and LaTeX are available at http://www.acm.org/sigs/sigplan/authorInformation.htm. This site also contains links to useful informations on how to write effective submissions. ------------------- Submission ------------------- All submissions must be sent via easychair: https://easychair.org/conferences/?conf=iwst18 ------------------- Program chairs ------------------- Anne Etien (UniversitÃ© de Lille, France) Loic Lagadec (Ensta Bretagne, France) ------ Plus d'infos sur le GDR GPL : http://gdr-gpl.cnrs.fr -------------------------------------------- StÃ©phane Ducasse http://stephane.ducasse.free.fr http://www.synectique.eu / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, BÃ¢t.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

conditional loading of packages in BaselineOf/ConfigurationOf
by Peter UhnÃ¡k April 5, 2018

April 5, 2018

Hi, is it possible to specify _natively_ (in the BaselineOf spec itself) a conditional loading of packages? Example usage: I have package with extensions for Calypso, but Calypso is not always loaded, so I want to load the package only if Calypso is present. The ugly way (because it's a hack and you cannot see the condition by looking at the project spec): self environment at: #ClyBrowser ifPresent: [ spec package: 'My-Calypso-Extensions'. ]. The imagined way (or something along the lines): spec package: 'My-Calypso-Extensions' with: [ spec condition: [ self environment includesKey: #ClyBrowser ] ] Is this possible? Or is there some other recommended way how to approach this? Thanks, Peter

2 1