- Pharo-users - lists.pharo.org

ZnClient: how to emulate a curl command
by Offray Vladimir Luna CÃ¡rdenas June 8, 2017

June 8, 2017

Hi, I'm prototyping some integration between Fossil and Pharo for the creation of dynamic distributed web sites [1]. Now I would like to send some messages to store serialized STON domain objects as Fossil wiki pages. The command that makes this, using curl, is: curl -H "Content-Type: application/json" -d '{"authToken": "mytoken", "payload": {"name": "foo", "content": "bar"}}' http://localhost:8081/json/wiki/create and I thought that a similar command would be the one at [2], but there is something about ZnEntity that I'm not understanding. How can I replicate the curl command using ZnClient? [1] http://smalltalkhub.com/#!/~Offray/Brea [2] http://ws.stfx.eu/D61ZOA1LEQNG Thanks, Offray

2 2

Re: [Pharo-users] Bloc/Brick/Spec
by Glenn CavarlÃ© June 8, 2017

June 8, 2017

Hi Marc, It would be so cool but no, it's not planned. Like SDL and Morphic, Gtk is only used as a backend for windowing. This means that only primitives related to windowing are currently implemented (i.e GtkWindow related apis). Working on widget binding with Gtk or Qt is something i would like to start, maybe next year but it is quite hard/long to do well. The Mars framework built by Esteban was a really good starting point but it is not maintained. Thanks for your interest, Cheers, Glenn. ----- Glenn CavarlÃ© -- View this message in context: http://forum.world.st/Bloc-Brick-Spec-tp4949591p4950514.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

1 0

Re: [Pharo-users] Bloc/Brick/Spec
by Glenn CavarlÃ© June 8, 2017

June 8, 2017

Hi all, As well described by Peter, Bloc is a low level graphics library which mainly manages multi-windowing (Morphic, SDL, Gtk soon), user interaction (events) and drawing (using Sparta). Brick is a widget framework on top of Bloc (button, inputField, ...) and Spec is a "multi-backend" UI Builder. I know that the installation of Bloc can be confusing because of the multiple possibilities. For more information, Metacello and Zeroconf scripts are described here : https://github.com/pharo-graphics/Bloc/blob/master/INSTALL.md. Cheers, Glenn. ----- Glenn CavarlÃ© -- View this message in context: http://forum.world.st/Bloc-Brick-Spec-tp4949591p4950481.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

2 1

No need to move to Application folder for Pharo 6 32 and 64 bit versions
by Dimitris Chloupis June 8, 2017

June 8, 2017

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.

3 3

Some Metacello issue
by Holger Freyther June 8, 2017

June 8, 2017

Hi, after having made some new releases I have an odd Metacello issue and I am not sure how to debug it. This happens on my legacy Pharo3/Pharo4 images that I still need to support in deployment. It seems to be related to a dependency chain of "app"->VoyageMongo->Magritte3 3.5.0 and somehow version '3.1.1.1' of Magritte3 doing something with Grease #stable and not finding a 'Core' group. Any idea how to debug it or if any configuration changed recently? It also only seems to happen if there are two dependency chains that try to load the same VoyageMongo version. Broken: pharo Pharo3.image config http://smalltalkhub.com/mc/osmocom/Osmocom/main ConfigurationOfOsmoUniverse --install=bleedingEdge Error: Name not found: Core MetacelloMCVersionSpec(Object)>>error: MetacelloMCVersionSpec(MetacelloVersionSpec)>>resolveToLoadableSpec:forLoad:forMap:packages: in Block: [ ^ self error: 'Name not found: ' , aString ] MetacelloMCVersionSpec(MetacelloVersionSpec)>>packageNamed:forLoad:forMap:ifAbsent: in Block: [ ... Dictionary>>at:ifAbsent: MetacelloMCVersionSpec(MetacelloVersionSpec)>>packageNamed:forLoad:forMap:ifAbsent: MetacelloMCVersionSpec(MetacelloVersionSpec)>>resolveToLoadableSpec:forLoad:forMap:packages: MetacelloMCVersionSpec(MetacelloVersionSpec)>>resolveToLoadableSpecs:forLoad:map: in Block: [ :req | ... Array(SequenceableCollection)>>do: MetacelloMCVersionSpec(MetacelloVersionSpec)>>resolveToLoadableSpecs:forLoad:map: MetacelloMCVersionSpec(MetacelloVersionSpec)>>resolveToLoadableSpecs: MetacelloMCVersionSpec(MetacelloVersionSpec)>>expandToLoadableSpecNames: in Block: [ :cache | ... MetacelloPharo30Platform(MetacelloPlatform)>>stackCacheFor:cacheClass:at:doing: in Block: [ :dict | ... MetacelloPharo30Platform(MetacelloPlatform)>>useStackCacheDuring:defaultDictionary: in Block: [ ^ aBlock value: dict ] BlockClosure>>on:do: ... Working: Metacello new configuration: 'Magritte3'; repository: 'http://www.smalltalkhub.com/mc/Magritte/Magritte3/main'; version: '3.5.0'; load

4 6

Re: [Pharo-users] About patterns, UML and documentation
by Peter Uhnak June 8, 2017

June 8, 2017

> > 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 > > > > > >

1 0

Re: [Pharo-users] About patterns, UML and documentation
by jtuchel＠objektfabrik.de June 8, 2017

June 8, 2017

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

2 1

Re: [Pharo-users] About patterns, UML and documentation
by Todd Blanchard June 8, 2017

June 8, 2017

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 > >

1 0

About patterns, UML and documentation
by Marc Hanisch June 8, 2017

June 8, 2017

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

1 0

How to migrate an object to a subclass of its class but with new inst vars ?
by Steven Costiou June 7, 2017

June 7, 2017

Hi, i'm trying to migrate an object from a given class A to a subclass of A with new inst vars. Can't get it to work. I have a class and an instance of it, say: Object subclass: #A instanceVariableNames: '' |a| a := A new. A has no instance variables. Now i create a subclass B of A with a new inst var: A subclass: #B instanceVariableNames: 'x' I want to do the following: B adoptInstance: a It does'nt work, for what i understand it is because the format of the classes are different (B has an inst var and A has not). How can i make the a object become an instance of B (subclass of a's class), making a acquiring the new inst var x (and in more complex cases keeping its own previous inst vars) ? Steven.

3 9