June 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [Pharo-dev] PharoDays17 Slides and some Videos

by Marcus Denker

> On 7 Jun 2017, at 20:08, Ben Coman <btc(a)openinworld.com> wrote: > > > > On Wed, Jun 7, 2017 at 10:24 PM, Marcus Denker <marcus.denker(a)inria.fr <mailto:marcus.denker@inria.fr>> wrote: > Hi, > > I have uploaded the Slides and Videos of PharoDays2017. Slides are complete (minus those > talks that were due demos). For the Videos we have right now 8 talks and the âShow Us Your > Projectâ session. More might come in the future (I need to check). > > Slides: > - https://www.slideshare.net/pharoproject/presentations <https://www.slideshare.net/pharoproject/presentations> > - http://files.pharo.org/conferences/2017PharoDays/ <http://files.pharo.org/conferences/2017PharoDays/> > > PlayList: https://www.youtube.com/playlist?list=PL4actYd6bfnw7ous5We-XnWq0NZquP3gM <https://www.youtube.com/playlist?list=PL4actYd6bfnw7ous5We-XnWq0NZquP3gM> > > > > I liked the UI metalinks on mouse clicks. Now what would be really cool is a metalink to bring up a debugger for the next click on a button, to help learn how the system implements that feature. > Yes, it would be nice to experiment in that direction! Marcus

June 8, 2017

No need to move to Application folder for Pharo 6 32 and 64 bit versions

by Dimitris Chloupis

I have latest macos sierra , dowload , opened and saved image for both pharo 6 (32 and 64 bit) and I see no problem doing that from the dowload folder without moving the apps to the Application folder. Am I missing something here ? Because when I dowloaded them there was a warning dialog that said that this would not work.

June 8, 2017

Re: [Pharo-users] Some Metacello issue

by Diego Lont

> On 08 Jun 2017, at 09:36, Diego Lont <diego.lont(a)delware.nl> wrote: > > Hi all, > > To keep the common projects in smalltalkhub stable, we agreed that those should use symbolic versions like release3 // release3.5 etc. This way we can add bug fixes and avoiding loading of different versions through different projects. > > But I might have done something stupid to the configuration of magritte, especially release3: > > When I added some features to Magritte, I saw that that the stable version in the configuration of Magritte3 was unstable for pharo2, 3 and 4 for quite some time. Basically the tests failed, because some changes were made for pharo 5 in order to let Magritte version 3.5 run. > > Since I did not have time to make a proper fix (and the error was there for quite a lot of builds) for the older pharo versions and I believe the tests for the stable version ought to be green, I thought the best way to fix it, was to changed the #release3 magritte version back to release 3.2 for the older pharo versions. Perhaps this is the cause of some of the problems. Tomorrow I have time to look into this problem and make a proper fix. > > Stephane already notified me this is at least a problem for Pillar â¦ > Just a small addition: I just looked at Pillar, but the build of Pillar was building fine until beginning of this month. My change is from the beginning of May â¦

June 8, 2017

Re: [Pharo-users] Some Metacello issue

by Diego Lont

Hi all, To keep the common projects in smalltalkhub stable, we agreed that those should use symbolic versions like release3 // release3.5 etc. This way we can add bug fixes and avoiding loading of different versions through different projects. But I might have done something stupid to the configuration of magritte, especially release3: When I added some features to Magritte, I saw that that the stable version in the configuration of Magritte3 was unstable for pharo2, 3 and 4 for quite some time. Basically the tests failed, because some changes were made for pharo 5 in order to let Magritte version 3.5 run. Since I did not have time to make a proper fix (and the error was there for quite a lot of builds) for the older pharo versions and I believe the tests for the stable version ought to be green, I thought the best way to fix it, was to changed the #release3 magritte version back to release 3.2 for the older pharo versions. Perhaps this is the cause of some of the problems. Tomorrow I have time to look into this problem and make a proper fix. Stephane already notified me this is at least a problem for Pillar â¦ Regards, Diego > On 07 Jun 2017, at 20:01, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > > > On 06/07/2017 03:46 AM, Holger Freyther wrote: >>> On 7. Jun 2017, at 14:09, Stephan Eggermont <stephan(a)stack.nl> wrote: >>> >>> Never refer to fixed versions unless you know why (you need to avoid a >>> specific bug fix). >> When wanting to have repeatable builds (e.g. for bugfixes) and in the >> absence of other means to lock/define versions externally, I think using >> a fixed version is the way to go. >> >> >>> What is most likely is that there is some overconstrained configuration. >>> Does your ConfigurationOfVoyageMongo or one of the configurations it >>> pulls in refer to different versions of grease or magritte? Another >>> issue can be that there are older configurations already loaded that >>> conflict with the newest ones. Indeed, the ConfigurationOfMongoTalk >>> is broken, refering to a fixed and older version of Grease. >>> ConfigurationOfVoyageMongo should probably be using #'release3' of >>> Magritte, but that doesn't break it. >> Right. So we have a "OsmocomUniverse" build job that pulls in all the >> apps into a single image. This helps to make API modifications and not >> forget any of the client code. >> >> The configuration has such dependencies: >> >> ConfigurationOfOsmocomUniverse >> -> ConfigurationOfHLR >> -> ConfigurationOfVoyageMongo >> -> Mongotalk >> -> Grease A >> -> Magritte3 >> -> Grease B >> -> ConfigurationOfSMPPRouter >> -> ConfigurationOfVoyageMongo >> -> Mongotalk >> -> Grease A >> -> Magritte3 >> -> Grease B >> >> What happens is that somehow "Grease A" gets loaded, then "Grease B" and >> when it is time for "Grease A" again.. the system kind of explodes and this >> is for Pharo3 and Pharo6. Now the question to me is.. why is this coming >> up right now? Did MongoTalk change or Magritte3 or something else? >> >> Is there an easy way for Metacello to try a mirror instead of the original, >> e.g. to inject an older ConfigurationOfMagritte3? >> > > I think that the `lock` command[1] is what you are looking for ... > > Dale > > [1] https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse… <https://github.com/dalehenrich/metacello-work/blob/master/docs/MetacelloUse…>

June 8, 2017

Re: [Pharo-users] About patterns, UML and documentation

by Peter Uhnak

> > with the tool and layout and stuff rather than concentrate on what is Well there are tools such as PlantUML that generate it for you, you can provide some hints, but generally it tends to be good enough to not be worried about layout. I have a Pharo -> PlantUML generator for class, object, and sequence diagrams somewhere, as I've used it to gain insight about some subsystems on several occasions, but I never published it... it's a bit of hacky code around Pharo's metaprogramming and reflecting capabilities... so you could in principle write it by hand in an hour or so... in fact doing so by hand might be beneficial for specific problem, because you can reverse-engineer only the parts that you care about instead of having everything or having a complex generator parametrization... > > Take Sven's NeoCSV package as an example. Great documentation and very > > good method names. and a complete set of tests. > > > > Sounds frightening at first if you come from a static typing background, > > but in my experience it works quite well. I don't think that this is a good example. From user perspective you usually interact with only two classes (reader and writer)... and I don't really see how UML could help you there. The internal architecture on the other hand, or tools with models could benefit from it much more (at least in class diagrams, the relationships between elements tends to be the most important part, so if you have one or two classes... then you won't have much connections...). Peter On Thu, Jun 08, 2017 at 08:40:34AM +0200, Marc Hanisch via Pharo-users wrote: > Date: Thu, 8 Jun 2017 08:40:34 +0200 > From: Marc Hanisch <marc.hanisch(a)googlemail.com> > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > Subject: Re: [Pharo-users] About patterns, UML and documentation > > Thanks Todd and Joachim for your fast responses, > > your examples are very interesting! I think I got the point! ...And you are > so true about your experience with UML and the struggle to group / align > all graphical objects so it is still understandable ;-) > > Best regards, > Marc > > 2017-06-08 7:53 GMT+02:00 jtuchel(a)objektfabrik.de <jtuchel(a)objektfabrik.de>: > > > I think the key to this is intention revealing names and comments. And > > shipping unit tests that are the best example of "running documentation". > > > > Take Sven's NeoCSV package as an example. Great documentation and very > > good method names. and a complete set of tests. > > > > Sounds frightening at first if you come from a static typing background, > > but in my experience it works quite well. > > > > There are UML tools. Some even allow round-trips where the UML diagrams > > can be generated from code (e.g. IBM/Instantiations have the UML Designer > > add-on), but to be honest, these only put you in high danger of playing > > with the tool and layout and stuff rather than concentrate on what is > > important. UML is fine for communicating the raw structure and basic ideas. > > Generating UML from code on the fly can help understand code, but I've seen > > too many projects that made the UML design documents an art of itself, and > > most of the times the diagrams were out of sync anyways... > > > > Just my 2 cents, > > > > Joachim > > > > > > -- > > ----------------------------------------------------------------------- > > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > > Fliederweg 1 http://www.objektfabrik.de > > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > > > > >

June 8, 2017

Re: [Pharo-users] About patterns, UML and documentation

by Marc Hanisch

Thanks Todd and Joachim for your fast responses, your examples are very interesting! I think I got the point! ...And you are so true about your experience with UML and the struggle to group / align all graphical objects so it is still understandable ;-) Best regards, Marc 2017-06-08 7:53 GMT+02:00 jtuchel(a)objektfabrik.de <jtuchel(a)objektfabrik.de>: > I think the key to this is intention revealing names and comments. And > shipping unit tests that are the best example of "running documentation". > > Take Sven's NeoCSV package as an example. Great documentation and very > good method names. and a complete set of tests. > > Sounds frightening at first if you come from a static typing background, > but in my experience it works quite well. > > There are UML tools. Some even allow round-trips where the UML diagrams > can be generated from code (e.g. IBM/Instantiations have the UML Designer > add-on), but to be honest, these only put you in high danger of playing > with the tool and layout and stuff rather than concentrate on what is > important. UML is fine for communicating the raw structure and basic ideas. > Generating UML from code on the fly can help understand code, but I've seen > too many projects that made the UML design documents an art of itself, and > most of the times the diagrams were out of sync anyways... > > Just my 2 cents, > > Joachim > > > -- > ----------------------------------------------------------------------- > Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de > Fliederweg 1 http://www.objektfabrik.de > D-71640 Ludwigsburg http://joachimtuchel.wordpress.com > Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1 > > >

June 8, 2017

Re: [Pharo-users] About patterns, UML and documentation

by jtuchel＠objektfabrik.de

I think the key to this is intention revealing names and comments. And shipping unit tests that are the best example of "running documentation". Take Sven's NeoCSV package as an example. Great documentation and very good method names. and a complete set of tests. Sounds frightening at first if you come from a static typing background, but in my experience it works quite well. There are UML tools. Some even allow round-trips where the UML diagrams can be generated from code (e.g. IBM/Instantiations have the UML Designer add-on), but to be honest, these only put you in high danger of playing with the tool and layout and stuff rather than concentrate on what is important. UML is fine for communicating the raw structure and basic ideas. Generating UML from code on the fly can help understand code, but I've seen too many projects that made the UML design documents an art of itself, and most of the times the diagrams were out of sync anyways... Just my 2 cents, Joachim -- ----------------------------------------------------------------------- Objektfabrik Joachim Tuchel mailto:jtuchel@objektfabrik.de Fliederweg 1 http://www.objektfabrik.de D-71640 Ludwigsburg http://joachimtuchel.wordpress.com Telefon: +49 7141 56 10 86 0 Fax: +49 7141 56 10 86 1

June 8, 2017

Re: [Pharo-users] About patterns, UML and documentation

by Todd Blanchard

Hi Marc. In Smalltalk, we rely on naming conventions a lot. The great thing is that Smalltalk selectors/symbols/method names read like English. aDictionary at: aKey put: anObject. aString indexOf: aCharacter startingAt: start ifAbsent: aBlock Seems pretty clear, no? We also rely on comments. For instance this is the class comment for IceRepository - an abstraction of a git repo. I represent an interface to a git repository. My main responsibilities are: - Load/update both baselines and individual packages from the repository. - Commit changes to the local repository and publish them to a remote repository. - Browse other versions of the loaded packages. - Handle branches For the Collaborators Part: State my main collaborators and one line about how I interact with them. Public API and Key Messages - loadPackage: packageName - createBranch: newBranchName Sample usage: Git new origin: 'git@github.com:npasserini/pharo-git-test.git'. git loadPackage: 'Pharo-Git-Test'. Instance Variables - origin: A string representing the url of a remote git repository (used as origin) - repository: An IceGitTreeGitRemoteRepository, which provides underlying git operations. - location: <FileReference> The directory of the local repository. - commitDictionary: <Dictionary of IceCommitInfo> Cached dictonary from commitId (hex string) to all commits in the current branch (in the local repo). - subdirectory: <String> The subdirectory of the local repository which is handled by the underlying GitFileTree - versionDescriptors: <List of GitFileTreePackageEntry> cached list of all package versions saved in the (currently selected branch) of the (local) repository. - announcer: <Announcer> - branch: <IceBranch> currently selected branch. - loadedCode: <IceLoadedCode> Contains information about the loaded code for each package in this repository. (TODO: maybe handle special cases about loading different versions loaded for different packages, see: https://github.com/npasserini/iceberg/issues/139) I hope this helps. -Todd Blanchard > On Jun 7, 2017, at 10:17 PM, Marc Hanisch via Pharo-users <pharo-users(a)lists.pharo.org> wrote: > > > From: Marc Hanisch <marc.hanisch(a)googlemail.com> > Subject: About patterns, UML and documentation > Date: June 7, 2017 at 10:17:11 PM PDT > To: Any question about pharo is welcome <pharo-users(a)lists.pharo.org> > > > Hello, > > I don't know Smalltalk well enough to give myself an answer about the following topic: > > When using design patterns, one benefit of writing interfaces and passing objects, that implement this interface, to methods is, that the reader instantly knows: okay, here the method A expects something that implements method B. > > Due to the nature of being a dynamically typed language, Smalltalk does not need interfaces. An exception object is thrown when a message is passed to an object that does not implement that method. But this message send could be deep inside the code. > > How do you show to the reader of your code your intention, that you are expecting, let's say for example, an iterator or an object that implements method X, Y and Z? > > Just with your method comments? Do you use UML? If so, how (without interfaces that point to the required methods)? > > Sorry, but I think my understanding of OOP is still to much influenced by C++ and Java based teachings... > > Thanks and best regards, > Marc > >

June 8, 2017

About patterns, UML and documentation

by Marc Hanisch

Hello, I don't know Smalltalk well enough to give myself an answer about the following topic: When using design patterns, one benefit of writing interfaces and passing objects, that implement this interface, to methods is, that the reader instantly knows: okay, here the method A expects something that implements method B. Due to the nature of being a dynamically typed language, Smalltalk does not need interfaces. An exception object is thrown when a message is passed to an object that does not implement that method. But this message send could be deep inside the code. How do you show to the reader of your code your intention, that you are expecting, let's say for example, an iterator or an object that implements method X, Y and Z? Just with your method comments? Do you use UML? If so, how (without interfaces that point to the required methods)? Sorry, but I think my understanding of OOP is still to much influenced by C++ and Java based teachings... Thanks and best regards, Marc

June 8, 2017

Re: [Pharo-users] Traits, method flatten

by Sean P. DeNigris

HilaireFernandes wrote > I made another attempt to > persist this time with filetree://. The net result is the same, the > Traits logic is lost in the classes using the Traits: all traits methods > are duplicated !! I just got burned by this in ##50768. Methods inherited from traits were saved as part of the package containing the extended class, as well as the package containing the Trait itself. Ugh. Was this ever fixed by Pharo 6? ----- Cheers, Sean -- View this message in context: http://forum.world.st/Traits-method-flatten-tp4941799p4950378.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

June 8, 2017