November 2013 - Pharo-users

Useful (hidden) features in Pharo 3.0

by Juraj Kubelka

Hi, this week I have realized a lot of useful (hidden) features I did not know they exists. Those I have learned: Cmd+t â Nautilus, when method source code is displayed. It shows context menu related to the position of cursor. Cmd+Shift+p â Nautilus, in method source code, it extends selection according to AST Shift+Enter â Spotlight Do you know others? Thanks, Jura

Nov. 17, 2013

Help in St. Petersburg?

by HernÃ¡n Morales Durand

I am sorry for the off-topic. A friend of mine was stolen in Sofia and now she is completely out of money going to St. Petersburg in a few days. Anyone there who can help her a little bit would be really appreciated. Cheers, HernÃ¡n

Nov. 17, 2013

Re: [Pharo-users] Pyret: adding tests directly into classes

by Andy Burnett

Esteban said <<< Hi, It does not really matters where you put the test. What matters is to have the tools that show them properly, and we are going in that direction. We already have ways to "jump to tests" in Nautilus, and we will continue improving that to show them together (for example). But I do not think the tests need to be *in* the class definition to have same level of interoperation. Esteban >>> I agree. The actual architecture doesn't matter. The critical factor is making it as easy as possible to write/navigate tests. I didn't know about the Nautilus features. I shall have to go and experiment. Also, thinking about Doru's point. I wonder if we could write tests/examples in the comments section of code. It might be an interesting addition

Nov. 17, 2013

Re: [Pharo-users] Pyret: adding tests directly into classes

by Andy Burnett

Doru said: <<< I stumbled across this idea when Markus Gaelli chose it as a PhD topic about ten years ago (man, I'm old). The main idea was not to provide tests, but examples that happened to have assertions. The goal was twofold: (1) provide live documentation with real objects, (2) provide another way of composing tests. The project did not really come to fruition, but I still think this is highly interesting topic. Part of the ideas were later implemented in Phexample (http://www.smalltalkhub.com/#!/~Phexample/Phexample/) and JExample (http://scg.unibe.ch/research/jexample) >>> That's really interesting. I had never heard of Phexample - so many interesting projects, so little time! - I like the approach of building on tests. Do you know if this will work in Pharo 3? Also, I may have misunderstood what Pyret was doing. Perhaps it is more about examples.

Nov. 17, 2013

Re: [Pharo-users] Pyret: adding tests directly into classes

by Esteban Lorenzano

Hi, It does not really matters where you put the test. What matters is to have the tools that show them properly, and we are going in that direction. We already have ways to "jump to tests" in Nautilus, and we will continue improving that to show them together (for example). But I do not think the tests need to be *in* the class definition to have same level of interoperation. Esteban On Nov 17, 2013, at 3:08 PM, Andy Burnett <andy.burnett(a)knowinnovation.com> wrote: > I have just come across the Pyret language. It looks interesting, but the part which particularly caught my interest was the way that they had built the unit tests directly into the classes, rather than having separate test classes. > > I think this is an interesting idea. It seems as though it would be easier to manage writing tests if everything were in one location. And this - might - mean that people were more likely to write tests. > > Has anyone else looked at this, and have an opinion on whether it would be a good addition to Pharo 4/5/X? > > Cheers > Andy

Nov. 17, 2013

Re: [Pharo-users] Pyret: adding tests directly into classes

by Tudor Girba

I stumbled across this idea when Markus Gaelli chose it as a PhD topic about ten years ago (man, I'm old). The main idea was not to provide tests, but examples that happened to have assertions. The goal was twofold: (1) provide live documentation with real objects, (2) provide another way of composing tests. The project did not really come to fruition, but I still think this is highly interesting topic. Part of the ideas were later implemented in Phexample (http://www.smalltalkhub.com/#!/~Phexample/Phexample/) and JExample (http://scg.unibe.ch/research/jexample) Cheers, Doru On Sun, Nov 17, 2013 at 3:08 PM, Andy Burnett < andy.burnett(a)knowinnovation.com> wrote: > I have just come across the Pyret language. It looks interesting, but the > part which particularly caught my interest was the way that they had built > the unit tests directly into the classes, rather than having separate test > classes. > > I think this is an interesting idea. It seems as though it would be easier > to manage writing tests if everything were in one location. And this - > might - mean that people were more likely to write tests. > > Has anyone else looked at this, and have an opinion on whether it would be > a good addition to Pharo 4/5/X? > > Cheers > Andy > -- www.tudorgirba.com "Every thing has its own flow"

Nov. 17, 2013

Pyret: adding tests directly into classes

by Andy Burnett

I have just come across the Pyret language. It looks interesting, but the part which particularly caught my interest was the way that they had built the unit tests directly into the classes, rather than having separate test classes. I think this is an interesting idea. It seems as though it would be easier to manage writing tests if everything were in one location. And this - might - mean that people were more likely to write tests. Has anyone else looked at this, and have an opinion on whether it would be a good addition to Pharo 4/5/X? Cheers Andy

Nov. 17, 2013

Re: [Pharo-users] i18n - Where to start?

by btc＠openinworld.com

Stephan Eggermont wrote: > Here is a demo of the i18n support in QCMagritte. > It supports live editing of the languages and strings used in your application. > > youtu.be/cTut44Xs3_U > > Stephan > > Very impressive.

Nov. 17, 2013

Re: [Pharo-users] i18n - Where to start?

by Stephan Eggermont

In the multi language demo of QCMagritte, a magritte visitor is used that changes all label:, checkboxLabel:, comment: and group: sends in descriptions to automatically use a multilanguagestring. The parameter is used as the key. All unique keys are collected. The default translation is the key. That is used for missing translations. Languages can be added on the fly. The demo has a simple UI to directly add and change translations. The whole translation table can be written to csv, and read back. This is not shown in the video Stephan Verstuurd vanaf mijn iPhone

Nov. 16, 2013

Re: [Pharo-users] Finding references to traits

by Camillo Bruni

I think the #users method return what you want, no? TBehavior users On 2013-11-16, at 18:19, btc(a)openinworld.com wrote: > If I come in cold to a system and see some class using trait, and then I want to find all classes that use that trait. I have tried a few ways but failed to work it out. The most obvious action "Extended search > references of it" doesn't show them, and neither does any other action I try. How is this done? > > cheers -ben >

Nov. 16, 2013