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

CFP - IWST 2018 - International Workshop on Smalltalk Technologies

by Stephane Ducasse

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

April 5, 2018

Failure with GitFileTree commiting changes in Traits

by Rafael Luque

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.

April 5, 2018

Re: [Pharo-users] Slower

by Hilaire

After some more investigation, I think it is not the greated bottleneck. When I render points not as discs but as Square, Athens is happy. I guess the Cairo way of doing this is very slow because its seems Cairo does not come with dedicated disc rendering code, it must be render with portion of arc, as far as I remember. If I prevent to render empty text label attached with each point, Athens is even happier. Text font rendering through Athens seems to be slow. Hilaire Le 04/04/2018 Ã 23:05, Hilaire a Ã©critÂ : > It reduces by 50% the time to execution. Need to check if this trick > #1 and #2 are still needed at P7 time. -- Dr. Geo http://drgeo.eu

April 5, 2018

Re: [Pharo-users] Black screen on Mac OSX

by Hilaire

Le 04/04/2018 Ã 12:13, Stephane Ducasse a Ã©critÂ : > Let me know for P7 because this is easier to check and help. Ah, so please test this one on your Mac. It is a P7 image based built: https://www.dropbox.com/s/f51fh7wa9x52grv/DrGeo.app-18.06a.zip?dl=0 Thanks Hilaire -- Dr. Geo http://drgeo.eu

April 5, 2018

Re: [Pharo-users] conditional loading of packages in BaselineOf/ConfigurationOf

by Cyril Ferlicot D.

On 05/04/2018 09:53, Peter UhnÃ¡k wrote: > 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 Hi Peter, Maybe this can help you: https://code.google.com/archive/p/metacello/wikis/CustomProjectAttrributes.… -- Cyril Ferlicot https://ferlicot.fr

April 5, 2018

conditional loading of packages in BaselineOf/ConfigurationOf

by Peter UhnÃ¡k

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

April 5, 2018

Re: [Pharo-users] Slower

by Hilaire

Looking at the profile, Athens spend time on some of my widgets: 1. LabelMorph with a workaround in the draw method as: drawOnAthensCanvas: aCanvas "Work around for the conflicting size font problem" Â Â Â aCanvas pathTransform restoreAfter: [ Â Â Â aCanvas pathTransform scaleBy: 1.00001. Â Â Â Â Â Â "draw text here" Â Â Â Â Â Â super drawOnAthensCanvas: aCanvas]. Do we still need to do that, may be not. 2. TextMorph with another workaround: drawOnAthensCanvas: aCanvas Â Â Â | cached | Â Â Â myForm ifNil: [myForm := self imageForm]. Â Â Â cached := aCanvas cacheAt: myForm ifAbsentPut: [ Â Â Â Â Â Â myForm asAthensPaintOn: aCanvas.Â Â Â ]. Â Â Â aCanvas setPaint: cached. Â Â Â aCanvas paintTransform restoreAfter: [ Â Â Â Â Â Â aCanvas paintTransform translateBy: self fullBounds origin truncated. Â Â Â Â Â Â aCanvas drawShape: self fullBounds]. It should be faster but it is slower. 3. PointMorph, painting as round shape is slow, painting point as square is way faster. It reduces by 50% the time to execution. Need to check if this trick #1 and #2 are still needed at P7 time. Hilaire Le 04/04/2018 Ã 22:31, Hilaire a Ã©critÂ : > From the profile, there are a lot of activities with Athens. I can't > say if it is normal... Someone with good knowledge could dig on it. I > can provide the environment to test. -- Dr. Geo http://drgeo.eu

April 4, 2018

Re: [Pharo-users] Slower

by Hilaire

You mean one iteration? Hilaire Le 04/04/2018 Ã 20:05, Thierry Goubier a Ã©critÂ : > > Can you profile a refresh / a redraw? > > We've seen many times Morphic being qualified as slow, and the culprit > were very badly programmed widgets. > > Thierry -- Dr. Geo http://drgeo.eu

April 4, 2018

Re: [Pharo-users] To be there or not to be there

by Sean P. DeNigris

HilaireFernandes wrote > I come to a situation where methods seems to be there without been > there. I encountered two seemingly similar problems, not sure yet how to reproduce and also may have been fixed since then, but for reference they were: - extension methods saved 2 places in filetree - both in the correct package and the package of the extended class - extension methods which are clearly there, but don't show up in Iceberg. IIRC I had to move the method from a package tag up one level to the package (i.g. from 'Package-Tag' to 'Package') ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

April 4, 2018

Re: [Pharo-users] Slower

by Thierry Goubier

Le 04/04/2018 Ã 19:31, Hilaire a Ã©critÂ : > It is already animated :) > https://twitter.com/GNUDrGeo/status/981583820037160961 > > But canvas get slow when I push to 500 montecarlo iterations, for example. Can you profile a refresh / a redraw? We've seen many times Morphic being qualified as slow, and the culprit were very badly programmed widgets. Thierry > > Le 04/04/2018 Ã 19:03, Stephane Ducasse a Ã©critÂ : >> Hilaire >> >> do you want to see an animation? >> >> Stef >

April 4, 2018