- Pharo-users - lists.pharo.org

Re: [Pharo-users] type checking in Smalltalk

by Denis Kudriashov

2017-03-30 16:03 GMT+02:00 Marc Hanisch via Pharo-users < pharo-users(a)lists.pharo.org>: > It is advised not to use the message isKindOf: in applications. > > I do understand that it is not a good idea to do different operations > depending on the kind of an object in one method. But in my (Javascript) > production code I do a lot of checking if an argument to a function is > "instanceof" someObject. When it is not the expected type of object, an > exception is thrown. I do this to ensure that someone (=another developer) > does not by accident passes a wrong type into my method. > > Reading this, I realized, that I never saw such type-checking in Pharo > production code. > In Pharo you will got DNU error automatically when object will receive message which it *d*oes *n*ot *u*nderstands. Then Pharo will show debugger to investigate and fix the problem. This is called dynamic typing and I guess JS will do something similar. So I wonder why you need custom error when program breaks types.

March 30, 2017

Re: [Pharo-users] type checking in Smalltalk

by Alexandre Bergel

Hi Marc, > Reading this, I realized, that I never saw such type-checking in Pharo production code. So the question is, what are recommended design principles for that problem in Smalltalk? Do you use what is called duck typing? I have carefully studied the topic of type checking in the past. I came to the conclusion that type errors are too easy to fix to justify a support in the language. There are always exceptions, for example, if you wish to provide guaranties and proof on some aspect of the language, interesting to hardware driver developers and critical software developers. In that case, you may want to have type annotation, maybe. But all in all, static type checking is more a distraction than a real benefit for practitioners in my opinion. Cheers, Alexandre

March 30, 2017

Re: [Pharo-users] type checking in Smalltalk

by Stephan Eggermont

On 30/03/17 16:03, Marc Hanisch via Pharo-users wrote: > Reading this, I realized, that I never saw such type-checking in > Pharo production code. So the question is, what are recommended > design principles for that problem in Smalltalk? Do you use what is > called duck typing? Normally I'm not interested in what an object is, but what it can do. So a test on #respondsTo: can tell me if the object knows how to do something. In smalltalk, I can add methods to existing classes, so there are a lot of extension methods on Object isXYZ, returning false. Morph returns true to isMorph, so all subclasses of Morph can be recognized that way. Instead of adding a test method, there are also empty implementations or ones that return self or an appropriate null-value. Stephan

March 30, 2017

Re: [Pharo-users] diff'ing with metacello

by Thierry Goubier

2017-03-30 16:42 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > On Thu, Mar 30, 2017 at 2:58 PM, Siemen Baader <siemenbaader(a)gmail.com> > wrote: > > Below is a fileout of 'ConfigurationOfPharoJS'. I download new releases > of > > PharoJS as they become available. Recently I found a regression - a > method > > 'PjApplication class >> playgroundWithoutLaunch' did not work any more. > What > > I wanted to do was to revert the whole project to an earlier version > until > > the method worked again - then look for the code that has been changed > > between releases and find the bug. > > > > In practice, even the earliest version (version 1.0 - method #version10) > did > > have the bug and I could not roll back the project to earlier release > states > > because there is no metadate for them. But I'd still like to learn how > to do > > it, so let's just say I want to compare version 1.2 and 1.3: > > > > version12: spec > > <version: '1.2' imports: #('0.1-baseline' )> > > > > version13: spec > > <version: '1.3' imports: #('0.2-baseline' )> > > > > > > I hope this makes sense. Thanks for helping me understand! > > You can only directly diff the Configurations themselves. > I fairly sure you can't auto-diff the packages loaded by each > configuration. > This is a missing feature. It would be nice to have something like > the merge-diff, > but there are probably other priorities. Maybe the new git workflow > will open some possibilities?? > If you have a project-oriented way of committing to git (you commit both the configuration and all the packages in one commit), then diffing via git would work. Current status on that feature is: - BaselineOf and all related packages save in one commit can be done with GitFileTree. I added an API for that and made a few experiments by organising and saving projects via the Metacello registry (with GUI support). I rolled back that extension in AltBrowser and I will reimplement it soon in a different, better way. - Iceberg ? - ConfigurationOf ? The approach of storing a configurationOf inside a meta repository makes implementing that harder. Now, I think the tools would probably be able to get that to work over Monticello with few changes, but they are a tad complex to implement, as in loading two different configurationsOf and resolving related packages (without loading them), and then changing the diff viewer to project all differences between all classes of the two groups of packages. One thing to remember is that complete packages, in multiple versions, can be loaded simultaneously as Monticello models without disrupting the code currently loaded and active in the image, as when you "browse" a Monticello package on disk. Thierry > > cheers -ben > >

March 30, 2017

Re: [Pharo-users] diff'ing with metacello

by Ben Coman

On Thu, Mar 30, 2017 at 2:58 PM, Siemen Baader <siemenbaader(a)gmail.com> wrote: > Below is a fileout of 'ConfigurationOfPharoJS'. I download new releases of > PharoJS as they become available. Recently I found a regression - a method > 'PjApplication class >> playgroundWithoutLaunch' did not work any more. What > I wanted to do was to revert the whole project to an earlier version until > the method worked again - then look for the code that has been changed > between releases and find the bug. > > In practice, even the earliest version (version 1.0 - method #version10) did > have the bug and I could not roll back the project to earlier release states > because there is no metadate for them. But I'd still like to learn how to do > it, so let's just say I want to compare version 1.2 and 1.3: > > version12: spec > <version: '1.2' imports: #('0.1-baseline' )> > > version13: spec > <version: '1.3' imports: #('0.2-baseline' )> > > > I hope this makes sense. Thanks for helping me understand! You can only directly diff the Configurations themselves. I fairly sure you can't auto-diff the packages loaded by each configuration. This is a missing feature. It would be nice to have something like the merge-diff, but there are probably other priorities. Maybe the new git workflow will open some possibilities?? cheers -ben

March 30, 2017

type checking in Smalltalk

by Marc Hanisch

Hello, I have a question which is more related to software engineering than to Pharo, but I hope that someone can give me an useful hint ;-) In Pharo By Example 5, Page 308, in the Chapter "Introspection", it is written: "Although these features (type inspection) are especially useful for imple- menting development tools, they are normally not appropriate for typical applications. Asking an object for its class, or querying it to discover which messages it understands, are typical signs of design problems, since they violate the principle of encapsulation." It is advised not to use the message isKindOf: in applications. I do understand that it is not a good idea to do different operations depending on the kind of an object in one method. But in my (Javascript) production code I do a lot of checking if an argument to a function is "instanceof" someObject. When it is not the expected type of object, an exception is thrown. I do this to ensure that someone (=another developer) does not by accident passes a wrong type into my method. Reading this, I realized, that I never saw such type-checking in Pharo production code. So the question is, what are recommended design principles for that problem in Smalltalk? Do you use what is called duck typing? Thanks for any advice :-) Marc

March 30, 2017

Re: [Pharo-users] Morphic component to display images/pictures

by Stephan Eggermont

On 30/03/17 13:24, Peter Uhnak wrote: > do we have a Morphic/Brick/whatever component for displaying pictures/images in Pharo? You can combine something with ImageMorph, ImagePreviewMorph, Form and TransformMorph. I don't know about mousewheel support, I vaguely remember something about mousewheel events being tranformed, and forgot if that was vm- or image-side. > 1) zooming with mousewheel (now it scrolls vertically) > 2) dragging the image around to scroll both vertically and horizontally (now I have to use manually the scrollbars) > 3) ideally also buttons like "show 1:1 size", "show fit to window"

March 30, 2017

Morphic component to display images/pictures

by Peter Uhnak

Hi, do we have a Morphic/Brick/whatever component for displaying pictures/images in Pharo? The "best" I found was GTInspector extension on PNG files, which provides scrollbars, however I would like to also have: 1) zooming with mousewheel (now it scrolls vertically) 2) dragging the image around to scroll both vertically and horizontally (now I have to use manually the scrollbars) 3) ideally also buttons like "show 1:1 size", "show fit to window" Do we have something like that? Thanks, Peter

March 30, 2017

Re: [Pharo-users] diff'ing with metacello

by Siemen Baader

Below is a fileout of 'ConfigurationOfPharoJS'. I download new releases of PharoJS as they become available. Recently I found a regression - a method 'PjApplication class >> playgroundWithoutLaunch' did not work any more. What I wanted to do was to revert the whole project to an earlier version until the method worked again - then look for the code that has been changed between releases and find the bug. In practice, even the earliest version (version 1.0 - method #version10) did have the bug and I could not roll back the project to earlier release states because there is no metadate for them. But I'd still like to learn how to do it, so let's just say I want to compare version 1.2 and 1.3: version12: spec <version: '1.2' imports: #('0.1-baseline' )> version13: spec <version: '1.3' imports: #('0.2-baseline' )> I hope this makes sense. Thanks for helping me understand! -- Siemen Fileout: ------------ 'From Pharo5.0 of 16 April 2015 [Latest update: #50765] on 30 March 2017 at 8:41:59.866839 am'! Object subclass: #ConfigurationOfPharoJS instanceVariableNames: 'project' classVariableNames: 'LastVersionLoad' poolDictionaries: '' category: 'ConfigurationOfPharoJS'! !ConfigurationOfPharoJS methodsFor: 'symbolic versions' stamp: 'NouryBouraqadi 3/9/2017 17:03'! development: spec <symbolicVersion: #'development'> spec for: #'common' version: '0.2-baseline'. ! ! !ConfigurationOfPharoJS methodsFor: 'symbolic versions' stamp: 'NouryBouraqadi 3/9/2017 17:03'! stable: spec <symbolicVersion: #'stable'> spec for: #'common' version: '1.3'. ! ! !ConfigurationOfPharoJS methodsFor: 'accessing' stamp: 'NouryBouraqadi 12/6/2016 10:27'! customProjectAttributes "Edit to return a collection of any custom attributes e.g. for conditional loading: Array with: #'Condition1' with: #'Condition2. For more information see: http://code.google.com/p/metacello/wiki/CustomProjectAttrributes " ^ #()! ! !ConfigurationOfPharoJS methodsFor: 'accessing' stamp: 'NouryBouraqadi 12/6/2016 10:27'! project ^ project ifNil: [ "Bootstrap Metacello if it is not already loaded" self class ensureMetacello. project := MetacelloMCProject new projectAttributes: self customProjectAttributes. "Create the Metacello project" (Smalltalk at: #'MetacelloVersionConstructor') on: self project: project. "Construct the project" project loadType: #'linear'. "change to #atomic if desired" project ]! ! !ConfigurationOfPharoJS methodsFor: 'versions' stamp: 'NouryBouraqadi 3/9/2017 17:03'! version13: spec <version: '1.3' imports: #('0.2-baseline' )> spec for: #'common' do: [ spec blessing: #'stable'. spec description: 'version 1.3'. spec author: 'NouryBouraqadi'. spec timestamp: '3/9/2017 17:03'. spec project: 'ReusableBricks' with: '1.2'; project: 'WebBrowser' with: '0.2.0'; project: 'ZincHTTPComponents' with: '2.8.3'. spec package: 'PharoJsApp' with: 'PharoJsApp-DaveMason.27'; package: 'PharoJsBridge' with: 'PharoJsBridge-DaveMason.114'; package: #PharoJsCoreLibraries with: 'PharoJsCoreLibraries-NouryBouraqadi.85'; package: #PharoJsCoreLibrariesTest with: 'PharoJsCoreLibrariesTest-NouryBouraqadi.5'; package: 'PharoJsExamples' with: 'PharoJsExamples-NouryBouraqadi.24'; package: #PharoJsExporter with: 'PharoJsExporter-DaveMason.67'; package: 'PharoJsTestFramework' with: 'PharoJsTestFramework-NouryBouraqadi.43'; package: #PharoJsTiming with: 'PharoJsTiming-DaveMason.20'; package: 'PharoJsTools' with: 'PharoJsTools-DaveMason.33'; package: 'PharoJsTranspiler' with: 'PharoJsTranspiler-DaveMason.251'; package: #PharoJsTranspilerOptimization with: 'PharoJsTranspilerOptimization-DaveMason.36'. ]. ! ! !ConfigurationOfPharoJS methodsFor: 'versions' stamp: 'NouryBouraqadi 2/18/2017 20:29'! version12: spec <version: '1.2' imports: #('0.1-baseline' )> spec for: #'common' do: [ spec blessing: #'stable'. spec description: 'version 1.2'. spec author: 'NouryBouraqadi'. spec timestamp: '2/18/2017 20:29'. spec project: 'ReusableBricks' with: '1.2'; project: 'WebBrowser' with: '0.2.0'; project: 'ZincHTTPComponents' with: '2.8.3'. spec package: 'PharoJsApp' with: 'PharoJsApp-NouryBouraqadi.25'; package: 'PharoJsBridge' with: 'PharoJsBridge-DaveMason.111'; package: #PharoJsCoreLibraries with: 'PharoJsCoreLibraries-DaveMason.79'; package: 'PharoJsExamples' with: 'PharoJsExamples-NouryBouraqadi.22'; package: #PharoJsExporter with: 'PharoJsExporter-DaveMason.65'; package: 'PharoJsTestFramework' with: 'PharoJsTestFramework-NouryBouraqadi.38'; package: #PharoJsTiming with: 'PharoJsTiming-DaveMason.20'; package: 'PharoJsTools' with: 'PharoJsTools-DaveMason.33'; package: 'PharoJsTranspiler' with: 'PharoJsTranspiler-DaveMason.248'; package: #PharoJsTranspilerOptimization with: 'PharoJsTranspilerOptimization-DaveMason.36'. ]. ! ! !ConfigurationOfPharoJS methodsFor: 'versions' stamp: 'NouryBouraqadi 12/7/2016 13:19'! version10: spec <version: '1.0' imports: #('0.1-baseline' )> spec for: #'common' do: [ spec blessing: #'stable'. spec description: 'version 1.0'. spec author: 'NouryBouraqadi'. spec timestamp: '12/7/2016 13:19'. spec project: 'ReusableBricks' with: '1.2'; project: 'WebBrowser' with: '0.2.0'; project: 'ZincHTTPComponents' with: '2.8.0'. spec package: 'PharoJsApp' with: 'PharoJsApp-DaveMason.23'; package: 'PharoJsBridge' with: 'PharoJsBridge-NouryBouraqadi.86'; package: #PharoJsCoreLibraries with: 'PharoJsCoreLibraries-NouryBouraqadi.67'; package: 'PharoJsExamples' with: 'PharoJsExamples-NouryBouraqadi.17'; package: #PharoJsExporter with: 'PharoJsExporter-DaveMason.54'; package: 'PharoJsTestFramework' with: 'PharoJsTestFramework-NouryBouraqadi.35'; package: #PharoJsTiming with: 'PharoJsTiming-DaveMason.16'; package: 'PharoJsTools' with: 'PharoJsTools-DaveMason.22'; package: 'PharoJsTranspiler' with: 'PharoJsTranspiler-NouryBouraqadi.237'; package: #PharoJsTranspilerOptimization with: 'PharoJsTranspilerOptimization-DaveMason.35'. ]. ! ! !ConfigurationOfPharoJS methodsFor: 'versions' stamp: 'NouryBouraqadi 2/6/2017 17:53'! version11: spec <version: '1.1' imports: #('0.1-baseline' )> spec for: #'common' do: [ spec blessing: #'stable'. spec description: 'version 1.1'. spec author: 'NouryBouraqadi'. spec timestamp: '2/6/2017 17:53'. spec project: 'ReusableBricks' with: '1.2'; project: 'WebBrowser' with: '0.2.0'; project: 'ZincHTTPComponents' with: '2.8.2'. spec package: 'PharoJsApp' with: 'PharoJsApp-NouryBouraqadi.25'; package: 'PharoJsBridge' with: 'PharoJsBridge-NouryBouraqadi.109'; package: #PharoJsCoreLibraries with: 'PharoJsCoreLibraries-NouryBouraqadi.77'; package: 'PharoJsExamples' with: 'PharoJsExamples-NouryBouraqadi.22'; package: #PharoJsExporter with: 'PharoJsExporter-nouryBouraqadi.64'; package: 'PharoJsTestFramework' with: 'PharoJsTestFramework-NouryBouraqadi.38'; package: #PharoJsTiming with: 'PharoJsTiming-DaveMason.20'; package: 'PharoJsTools' with: 'PharoJsTools-NouryBouraqadi.32'; package: 'PharoJsTranspiler' with: 'PharoJsTranspiler-NouryBouraqadi.246'; package: #PharoJsTranspilerOptimization with: 'PharoJsTranspilerOptimization-DaveMason.35'. ]. ! ! !ConfigurationOfPharoJS methodsFor: 'baselines' stamp: 'NouryBouraqadi 12/6/2016 10:29'! baseline01: spec <version: '0.1-baseline'> spec for: #'common' do: [ spec blessing: #'baseline'. spec repository: 'http://smalltalkhub.com/mc/noury/PharoJS/main/'. spec project: 'ReusableBricks' with: [ spec className: #ConfigurationOfReusableBricks; versionString: #'stable'; loads: #('Equals' ); repository: 'http://smalltalkhub.com/mc/CAR/ReusableBricks/main/' ]; project: 'WebBrowser' with: [ spec className: #ConfigurationOfWebBrowser; versionString: #'stable'; repository: 'http://smalltalkhub.com/mc/TorstenBergmann/WebBrowser/main/' ]; project: 'ZincHTTPComponents' with: [ spec className: #ConfigurationOfZincHTTPComponents; versionString: #'stable'; loads: #('Zinc-WebSocket-Core' ); repository: 'http://mc.stfx.eu/ZincHTTPComponents' ]. spec package: 'PharoJsApp' with: [ spec requires: #('PharoJsTranspiler' ). ]; package: 'PharoJsBridge' with: [ spec requires: #(#PharoJsCoreLibraries #PharoJsExporter 'PharoJsApp' 'WebBrowser' 'ZincHTTPComponents' ). ]; package: #PharoJsCoreLibraries with: [ spec requires: #('PharoJsTranspiler' ). ]; package: 'PharoJsExamples' with: [ spec requires: #('PharoJsApp' 'PharoJsTranspiler' 'PharoJsTestFramework' ). ]; package: #PharoJsExporter with: [ spec requires: #('PharoJsTranspiler' 'PharoJsApp' ). ]; package: 'PharoJsTestFramework' with: [ spec requires: #(#PharoJsExporter 'PharoJsBridge' 'PharoJsApp' ). ]; package: #PharoJsTiming with: [ spec requires: #(#PharoJsTranspilerOptimization 'PharoJsBridge' ). ]; package: 'PharoJsTools' with: [ spec requires: #('PharoJsBridge' ). ]; package: 'PharoJsTranspiler' with: [ spec requires: #('ReusableBricks' ). ]; package: #PharoJsTranspilerOptimization with: [ spec requires: #('PharoJsTranspiler' ). ]. ]. ! ! !ConfigurationOfPharoJS methodsFor: 'baselines' stamp: 'NouryBouraqadi 3/3/2017 12:36'! baseline02: spec <version: '0.2-baseline'> spec for: #'common' do: [ spec blessing: #'baseline'. spec repository: 'http://smalltalkhub.com/mc/noury/PharoJS/main/'. spec project: 'ReusableBricks' with: [ spec className: #ConfigurationOfReusableBricks; versionString: #'stable'; loads: #('Equals' ); repository: 'http://smalltalkhub.com/mc/CAR/ReusableBricks/main/' ]; project: 'WebBrowser' with: [ spec className: #ConfigurationOfWebBrowser; versionString: #'stable'; repository: 'http://smalltalkhub.com/mc/TorstenBergmann/WebBrowser/main/' ]; project: 'ZincHTTPComponents' with: [ spec className: #ConfigurationOfZincHTTPComponents; versionString: #'stable'; loads: #('Zinc-WebSocket-Core' ); repository: 'http://mc.stfx.eu/ZincHTTPComponents' ]. spec package: 'PharoJsApp' with: [ spec requires: #('PharoJsTranspiler' ). ]; package: 'PharoJsBridge' with: [ spec requires: #(#PharoJsCoreLibraries #PharoJsExporter 'PharoJsApp' 'WebBrowser' 'ZincHTTPComponents' ). ]; package: #PharoJsCoreLibraries with: [ spec requires: #('PharoJsTranspiler' ). ]; package: #PharoJsCoreLibrariesTest with: [ spec requires: #(#PharoJsCoreLibraries 'PharoJsBridge' ). ]; package: 'PharoJsExamples' with: [ spec requires: #('PharoJsApp' 'PharoJsTranspiler' 'PharoJsTestFramework' ). ]; package: #PharoJsExporter with: [ spec requires: #('PharoJsTranspiler' 'PharoJsApp' ). ]; package: 'PharoJsTestFramework' with: [ spec requires: #(#PharoJsExporter 'PharoJsBridge' 'PharoJsApp' ). ]; package: #PharoJsTiming with: [ spec requires: #(#PharoJsTranspilerOptimization 'PharoJsBridge' ). ]; package: 'PharoJsTools' with: [ spec requires: #('PharoJsBridge' ). ]; package: 'PharoJsTranspiler' with: [ spec requires: #('ReusableBricks' ). ]; package: #PharoJsTranspilerOptimization with: [ spec requires: #('PharoJsTranspiler' ). ]. ]. ! ! "-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- "! ConfigurationOfPharoJS class instanceVariableNames: ''! !ConfigurationOfPharoJS class methodsFor: 'loading' stamp: 'NouryBouraqadi 12/6/2016 10:27'! loadDevelopment "Load the #development version defined for this platform. The #development version will change over time and is not expected to be stable." "self loadDevelopment" <apiDocumentation> ^(self project version: #development) load! ! !ConfigurationOfPharoJS class methodsFor: 'loading' stamp: 'NouryBouraqadi 12/6/2016 10:27'! load "Load the #stable version defined for this platform. The #stable version is the version that is recommended to be used on this platform." "self load" <apiDocumentation> ^(self project version: #stable) load! ! !ConfigurationOfPharoJS class methodsFor: 'loading' stamp: 'NouryBouraqadi 12/6/2016 10:27'! loadBleedingEdge "Load the latest versions of the mcz files defined for this project. It is not likely that the #bleedingEdge has been tested." "self loadBleedingEdge" <apiDocumentation> ^(self project version: #bleedingEdge) load! ! !ConfigurationOfPharoJS class methodsFor: 'private' stamp: 'NouryBouraqadi 12/6/2016 10:27'! ensureMetacello (self baseConfigurationClassIfAbsent: []) ensureMetacello! ! !ConfigurationOfPharoJS class methodsFor: 'private' stamp: 'NouryBouraqadi 12/6/2016 10:27'! baseConfigurationClassIfAbsent: aBlock ^Smalltalk at: #'ConfigurationOf' ifAbsent: [ self ensureMetacelloBaseConfiguration. Smalltalk at: #'ConfigurationOf' ifAbsent: aBlock ].! ! !ConfigurationOfPharoJS class methodsFor: 'private' stamp: 'NouryBouraqadi 12/6/2016 10:27'! ensureMetacelloBaseConfiguration Smalltalk at: #'ConfigurationOf' ifAbsent: [ | repository version | repository := MCHttpRepository location: 'http://smalltalkhub.com/mc/dkh/metacello/main' user: '' password: ''. repository versionReaderForFileNamed: 'Metacello-Base-dkh.107' do: [ :reader | version := reader version. version load. version workingCopy repositoryGroup addRepository: repository ] ]! ! !ConfigurationOfPharoJS class methodsFor: 'development support' stamp: 'NouryBouraqadi 12/6/2016 10:27'! DevelopmentSupport "See the methods in the 'development support' category on the class-side of MetacelloBaseConfiguration. Decide what development support methods you would like to use and copy them the the class-side of your configuration." <apiDocumentation>! ! !ConfigurationOfPharoJS class methodsFor: 'development support' stamp: 'NouryBouraqadi 12/6/2016 10:27'! validate "Check the configuration for Errors, Critical Warnings, and Warnings (see class comment for MetacelloMCVersionValidator for more information). Errors identify specification issues that will result in unexpected behaviour when you load the configuration. Critical Warnings identify specification issues that may result in unexpected behavior when you load the configuration. Warnings identify specification issues that are technically correct, but are worth take a look at." "self validate" <apiDocumentation> self ensureMetacello. ^ ((Smalltalk at: #MetacelloToolBox) validateConfiguration: self debug: #() recurse: false) explore! ! !ConfigurationOfPharoJS class methodsFor: 'accessing' stamp: 'NouryBouraqadi 12/6/2016 10:27'! project ^self new project! ! !ConfigurationOfPharoJS class methodsFor: 'metacello tool support' stamp: 'NouryBouraqadi 12/6/2016 10:27'! isMetacelloConfig "Answer true and the Metacello tools will operate on you" ^true! ! On Tue, Mar 28, 2017 at 2:56 PM, Ben Coman <btc(a)openinworld.com> wrote: > Can you provide a concrete case of two versions you want to compare? > cheers -ben > > On Tue, Mar 28, 2017 at 8:51 PM, Siemen Baader <siemenbaader(a)gmail.com> > wrote: > > > > > > Sent from my iPhone > > > > On 28/03/2017, at 13.52, Ben Coman <btc(a)openinworld.com> wrote: > > > >> Do you mean the difference between two "ConfigurationXXX....mcz" files? > > > > I didn't know there were 'ConfigurationOfX.mcz' files. What do they > contain? > > > > What I want to see is what code has changed between two releases. In Git > I would do it with a diff of the two releases' checksums. In other words, I > want to see for releases described with metacello what the > > Monticello browser can show us for versions of packages. Does this make > sense? It seems like a very common use case to me, people must be doing it > all the time, or...? > > > > cheers, > > Siemen > > > > > >> As a workaround, perhaps load one and then from Monticello, > >> "start" to merge the other from Monticello and you will see a diff > between them. > >> > >> cheers -ben > >> > >> On Tue, Mar 28, 2017 at 7:06 PM, Siemen Baader <siemenbaader(a)gmail.com> > wrote: > >>> Hi all, > >>> > >>> is there a tool to diff two Metacello versions with different > baselines? I > >>> tried MetacelloBrowser > >>> (http://www.squeaksource.com/@6xz1bzmNF75EduBA/vZ263dVA) but it does > not > >>> install on Pharo 5.0. > >>> > >>> I need it to see what has changed when I install a new release of > PharoJS > >>> and to bisect in search for regressions. > >>> > >>> thanks, > >>> Siemen > >> > > > >

March 30, 2017

Re: [Pharo-users] Smacc debugger

by Tudor Girba

Hi, It is actually the economic reasoning that prevailed here. John was willing to invest effort to both work with and benefit from the Moose/GT environment. The consequence was that he built the GT extensions for SmaCC while Andrei and I offered a bit of support. In this process, we also got updates and fixes to several grammars that are now shipped with Moose. Furthermore, as John is the primary author of SmaCC it only makes sense that he gets to control what he maintains. As for the repository, I asked him kindly to keep it in SmalltalkHub at the beginning to make the integration with Moose cheaper and easier. Now, that the GitHub solution grows we can certainly consider moving it together with the rest of Moose. As for the need to have a fork of SmaCC, I think there is little need for that and John was always responsive to requests. Cheers, Doru > On Mar 29, 2017, at 6:21 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > So I browsed the mailing-list and I foind the mail of thierry saying that there is no difference. > I will try to tools in moose then. > > > On Wed, Mar 29, 2017 at 6:07 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > Ok I should say that I do not understand the differences and why there are two versions of Smacc. > So I will stop maintaining the tutorial because now may be I should revert what I wrote. > I was too stupid to do it in fact I should focus on my stuff and nothing else. > This saddens me a lot. > We are a small community and we split ourselves into little chunks. > I do not get why there is no notion of economy and sharing in our culture. > > Stef > > > > On Wed, Mar 29, 2017 at 2:30 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > > On Mar 28, 2017, at 11:50 AM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > > OK > > I loaded Smacc from github as mentioned by thierry. > > > > Metacello new > > baseline: 'SmaCC'; > > repository: 'github://ThierryGoubier/SmaCC'; > > load > > > > Are there two configurationOfSmacc? > > May be we should only have one no? > > > > I have the impression that even thierry and jason working heavily with Smacc do not know that. > > And we should not force them to use Moose. At least we do not have to win > > anything with it. > > I did not mean to force anyone to use Moose. I just said it is already loaded there, in case you use it. > > Moose relies on the ConfigurationOfSmaCC maintained by John. Thierry has another repository that he created before John moved his work to Pharo. But, now that he does work with Pharo Moose relies on his version. > > Cheers, > Doru > > > > > Stef > > > > On Mon, Mar 27, 2017 at 6:31 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > > They come with the ConfigurationOfSmaCC which is already in the Moose image. > > > > Doru > > > > > > > On Mar 27, 2017, at 4:52 PM, Stephane Ducasse <stepharo.self(a)gmail.com> wrote: > > > > > > Hi > > > > > > where can I load the Smacc gt extension and debugger extensions? > > > > > > Stef > > > > -- > > www.tudorgirba.com > > www.feenk.com > > > > "Speaking louder won't make the point worthier." > > > > > > > > -- > www.tudorgirba.com > www.feenk.com > > "There are no old things, there are only old ways of looking at them." > > > > > > > -- www.tudorgirba.com www.feenk.com "We cannot reach the flow of things unless we let go."

March 29, 2017