May 2014 - Pharo-users - lists.pharo.org

Re: [Pharo-users] Problem learning about Magritte
by Stephan Eggermont May 15, 2014

May 15, 2014

EstebanLM wrote >Other thing, to the maintainers of Magritte: Why is 3.2 not promoted? it is there since a couple of months nowâ¦ It should be fixed first. Grease stable is 1.1.8, and 3.2 refers to 1.1.6. Lots of configurations use references to #stable of Grease. That does not combine well with configurations using numbered versions. We are working on tooling to check configurations Stephan

1 0

Re: [Pharo-users] Problem learning about Magritte
by Stephan Eggermont May 14, 2014

May 14, 2014

Peter wrote: >Thanks. I have Magritte-Morph in my image, but I wonder if anyone has >debugged it. I send asMagritteMorph to a Magritte description and I get a >MAContainerMorph, which is OK. Try sending openInWorld to this, and it falls >over in MADescriptionMorph>>buildMorph, which calls >MADescriptionMorph>>rectangleMorph, which tries to create an instance of the >non-existent class RectangleMorph. Hmm, that looks like you have an old version of Magritte-Morph loaded. If you open the Monticello browser, you can select the Magritte-Morph package and then open its repository to see if there is a newer version. If you select a newer version and click Changes, you can see if this newer version is likely to solve your problem (it is). If you take a look at the ConfigurationOfMagritte3, you can see what goes wrong. version32 is the first one referring to a Magritte-Morph newer than version 70. stable: installs version311 however. So ConfigurationOfMagritte3 needs a new stable version. (Done) >I have tried to trace this back, and it is true that my original Pharo 3.0 >image, downloaded on 30 Apr 2014, does not have the class RectangleMorph. I >have looked at older images, and the class exists. Maybe my mistake was to >try to use the Pharo 3.0 image the day it was announced. Perhaps I would be >better off using one of the pre-packed images you mention. Pharo 3 has lots of improvements and clean-ups. RectangleMorph behavior was folded back into BorderedMorph. The projects running on top of Pharo have different ideas of what should be stable and what development versions. The people developing them mostly use development releases or specific versions. If there are not a lot of non-developing users the stable version tends to lag behind. And if the specific problem is not in the tests, CI will not break. Just before the release, there are lots of fixes and the image changes fast. Not all projects will be able to synchronize fast, and have sufficient trust to declare a new version stable. So just after a release, you might have to use a lot of development versions, check repositories and ask questions on the mailing lists. Please do, that is the only way we can improve. >My only worry is that there is a list of dozens of contributions on >https://ci.inria.fr/pharo-contribution/, and unless you have far more >knowledge than I have it is impossible to know which might be helpful. For >now I will follow your hint and use the Forum image. That's a helpful comment. Thank you. We should improve the project descriptions (at least I should for mine). Stephan

7 11

Some code to share - Twitter access
by Arturo Zambrano May 14, 2014

May 14, 2014

Hi All, I have some code that allows to access Twitter data using its REST API and the Streaming API (thanks Sven for helping me in It is rudimentary and needs more work, but it is useful for what I'm doing as a hobby in: http://www.tweetreport.com.ar/ I would like to share it but it is still mixed with some other code of my Twitter toy (thanks Alex , Pablo and all the Roassal team). So, if there is people interested in this code, I will separate and publish it. I just need to know if someone wants it to play, to avoid useless work. Best regards art

6 7

Migrating to Nautilus
by Hilaire Fernandes May 14, 2014

May 14, 2014

Hi, In DrGeo, I add this code snippet to: browser := Browser newOnClass: DrGeoUserScripts selector: mathItem script. browser addDependent: self domain. browser codeTextMorph owner owner extent: 450@350. browser topView setProperty: #morphicLayerNumber toValue: 5. 1. open a minimal browser 2. set a dependency so DrGeo is noticed when the user edited and compile its script (so Drgeo can update the sketch) 3. rescale the browser so the user can still see his sketch 4. set the minimal browser in a permanent top position. As Browser is broken and not gonna be fixed, I need to redo the same with Nautilus, but this one is a big beast. Any tips how to do it? Thansk Hilaire -- Dr. Geo http://drgeo.eu

3 6

Re: [Pharo-users] Problem learning about Magritte
by Stephan Eggermont May 14, 2014

May 14, 2014

Peter wrote >Well, I am carrying on, but I do wonder why Pharo has to be such a rapidly >moving target. There are virtues in stability, and perhaps there should be a >filtering process before any change is made, to ensure that the benefits >outweigh any disruption. I must admit that, at times, Pharo looks like a >playground for a fairly small group of very clever people who are in love >with the process of development. There is virtue in stability as well as in innovation and in cleaning up. Pharo errs on the side of innovation and radical cleaning up. While doing that, we find out how to get better and faster at change. we do that by breaking things and then fixing them, trying to create as fast a feedback loop as possible. Squeak errs on the side of stability, trying to make things unloadable while keeping up compatibility. To work well with Pharo, as soon as possible set up a ci project in the inria infrastructure. That way you know when something gets broken (and the pharo core developers can see when they break something). A lot of the names are explained in Pharo by Example, Deep into Pharo and pharo for the enterprise https://github.com/SquareBracketAssociates/PharoForTheEnterprise-english In the Forum image are also parts of Moose (Glamour, Roassal). FOBrowser open FOTutorial open Stephan

1 0

Re: [Pharo-users] Problem learning about Magritte
by Stephan Eggermont May 14, 2014

May 14, 2014

Peter wrote: >It all looks a maze of >new terminology to me - I don't understand the difference between Monticello >and Metacello, for instance. Both are part of configuration management. Historically, Monticello came first. It supports distributed version control of a single package. Package is a problematic concept in Pharo (and Squeak), as multiple class categories belong to one package. Class category and package are often used as if they are the same. The Magritte-Model package contains all categories starting with 'Magritte-Model', a.o. Magritte-Model-Core. Monticello has support for required packages, but this is better expressed in Metacello. Metacello solves the problem of dealing with multiple platforms, dependencies of packages and different status. Better and longer explanations can be found in the Deep into Pharo book http://www.deepintopharo.com >I am sure to an expert your explanation of how >to check the correct version of Magritte3 is quite straightforward, but I >would never have found my way to that conclusion myself. Yes, that takes time and experience. A smalltalk system is large and finding your way around is not simple. I hope explaining how I find out helps. >As I pointed out to >Esteban, I used the configuration browser on 5 May to get the stable version >of Magritte3. If that was already out of date, I am pretty well lost. There was no test for this, so the build was green :( >Still, I am making progress with my original aim of learning about Magritte, >and there are many helpful people on this group, so you can just regard this >as me blowing off steam after things had not gone completely easily. Good. Just continue telling us where we need to improve. Stephan

1 0

Re: [Pharo-users] Problem learning about Magritte
by Stephan Eggermont May 14, 2014

May 14, 2014

Peter wrote: >is there a method #asMorph which will give the >morphic version as easily, or if not how do I get an editor as a Pharo >window? There is asMagritteMorph yes, defined in Magritte-Morph. You might need to load that additionally (it is loaded in the Forum image). Stephan

3 3

Scaling an Athens surface
by Hilaire Fernandes May 14, 2014

May 14, 2014

I have morph embedded in a AthensWrapMorph, before exporting it to a bitmap, I would like to rescale the AthenSurface. How can I do it at the Athens level to get the best quality. Hilaire -- Dr. Geo http://drgeo.eu

1 0

Gorgeous
by Hilaire Fernandes May 13, 2014

May 13, 2014

DrGeo canvas with Athens looks really nice. Hilaire -- Dr. Geo http://drgeo.eu

2 2

Re: [Pharo-users] Problem learning about Magritte
by Stephan Eggermont May 13, 2014

May 13, 2014

Hi Peter That sounds like you have independently installed Seaside and Magritte. You might miss the part connecting them together. Seaside can be used without Magritte, and Magritte without Seaside. That happens if you just install stable Seaside and stable Magritte from the configuration browser. Can you check if you have Magritte-Seaside loaded? That is in the Seaside group of Magritte. If not, you need the other option in the configuration browser, just loading the configuration of Magritte3. Then in a workspace, do-it (ConfigurationOfMagritte3 project version: #stable) load: 'Seaside'. A faster way to start can be to use one of the images from https://ci.inria.fr/pharo-contribution/ Pier, QCMagritte and Forum all come with both Magritte and Seaside preloaded. Stephan

5 5