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

Re: [Pharo-users] [Pharo-dev] Pillar 0.56 : New features, new syntax

by Norbert Hartl

> Am 26.05.2015 um 11:03 schrieb Damien Cassou <damien.cassou(a)inria.fr>: > > > Ben Coman <btc(a)openinworld.com> writes: > >> This might be a case where is reasonable for both to be valid: >> @ for backward compatibility >> # for compatibility with internet conventions > > - Pillar is not an Internet-related tool. It produces HTML, but not only: > Pillar produces LaTeX and Markdown and we plan to make it support > Docbook. For example, LaTeX uses \ref to represent anchors, should > Pillar use \ref instead of @? > No, of course not. I see an URI as good and common known abstraction to reference resources. It is useful regardless how you access different resources and that is what are the semantics behind the anchor and the reference. > - Creating anchors in the document is done through the @@ syntax. As a > result, both links and anchors use the same character. Switching to # > for links only would break this similarity. Switching to # for both > links and anchors would break even more document and website (but I > think that's ok). > > Breaking backward compatibility is ok, but we should pay attention when > we do it. > As it was proposed already there could be a time where both would work. So this is not an argument. I can see that the meaning of an anchor or a reference in pillar can exceed the semantics of an URI. In this case it wouldn't be a good idea to use URI syntax. But I doubt this will be the case. So I'm opting for a format that is commonly known and that enables URI aware software not be mislead by a format. Norbert

May 26, 2015

How to update to Pharo 5 in Ubuntu 14.04 ?

by Dimitris Chloupis

I have tried to use sudo apt-get update , but when i open pharolauncher using the pharo command in the terminal i see no option to download a pharo 5 image, Any clue how I can update it ?

May 26, 2015

Re: [Pharo-users] [Pharo-dev] Pillar 0.56 : New features, new syntax

by Damien Cassou

Ben Coman <btc(a)openinworld.com> writes: > This might be a case where is reasonable for both to be valid: > @ for backward compatibility > # for compatibility with internet conventions - Pillar is not an Internet-related tool. It produces HTML, but not only: Pillar produces LaTeX and Markdown and we plan to make it support Docbook. For example, LaTeX uses \ref to represent anchors, should Pillar use \ref instead of @? - Creating anchors in the document is done through the @@ syntax. As a result, both links and anchors use the same character. Switching to # for links only would break this similarity. Switching to # for both links and anchors would break even more document and website (but I think that's ok). Breaking backward compatibility is ok, but we should pay attention when we do it. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

May 26, 2015

Roassal-Woden on mouse events

by Lusa Nicolas

Hi, until now was working with the interaction on roassal-woden only with the RWMouseButtonDown event, but I would like to distinguish the left from the right click (which right now is not possible, correct me if I am wrong please). I took a look to the code which is handling the mouse events but it looks like I have to modify classes of roassal-woden itself if I want that to work. Any hint/tip on how to do it trying not to impact your classes? Cheers, Nicolas

May 26, 2015

Re: [Pharo-users] Some Pharo 4 Getting-Started tips

by stepharo

Le 25/5/15 18:30, Ben Coman a Ã©crit : > On Mon, May 25, 2015 at 10:38 PM, Avdi Grimm <avdi(a)avdi.org> wrote: >> http://devblog.avdi.org/2015/05/25/some-pharo-4-getting-started-tips/ > Thanks Avdi. > > We should at least change the Nautilus title bar to "Nautilus System > Browser" (or just "System Browser" ?) Yes I thought the same Nautilus Systeme Browser is good. > > This would be a simple one for anyone wanting to dip their toe into > the Pharo development workflow for the first time. Just log into > Fogbugz and assign the issue to yourself. > https://pharo.fogbugz.com/default.asp?15608 > http://pharo.org/contribute-propose-fix > > cheers -ben > >

May 26, 2015

Re: [Pharo-users] Some Pharo 4 Getting-Started tips

by Offray Vladimir Luna CÃ¡rdenas

+1 to some side name to the main tools. I have my "grafoscopio" project, but is a long shot to get into the image, and in Spanish it seems to work. Cheers, Offray El 25/05/15 a las 19:50, Sean P. DeNigris escribiÃ³: > Ben Coman wrote >> We should at least change the Nautilus title bar to "Nautilus System >> Browser" (or just "System Browser" ?) > > Part of the problem is that we have overloaded system categories to package > code for SCM. System categories should be tags (preferably multiple allowed) > which offer a logical view of the system. Packages, the POV we show now, are > orthogonal and much less useful for users. > > The other complication is that we have jumped onto the fad now to have cool > names for all software projects which offer no guidance as to what the code > actually does - a la Ruby, Sinatra, Rails. While this mysteriousness may > generate excitement for the project, it seems far less useful once we > integrate things in the image. What does/could Nautilus mean to a new user? > Taking a cue from Mac - the core apps are called Mail, Contacts, Maps, > Notes; not Sandcastle, Cabana, SkippingStone, and Umbrella ;) At least Opal > has the word Compiler attached to it! > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Some-Pharo-4-Getting-Started-tips-tp4828493p4828538.h… > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

May 26, 2015

Re: [Pharo-users] Some Pharo 4 Getting-Started tips

by Sean P. DeNigris

Ben Coman wrote > We should at least change the Nautilus title bar to "Nautilus System > Browser" (or just "System Browser" ?) Part of the problem is that we have overloaded system categories to package code for SCM. System categories should be tags (preferably multiple allowed) which offer a logical view of the system. Packages, the POV we show now, are orthogonal and much less useful for users. The other complication is that we have jumped onto the fad now to have cool names for all software projects which offer no guidance as to what the code actually does - a la Ruby, Sinatra, Rails. While this mysteriousness may generate excitement for the project, it seems far less useful once we integrate things in the image. What does/could Nautilus mean to a new user? Taking a cue from Mac - the core apps are called Mail, Contacts, Maps, Notes; not Sandcastle, Cabana, SkippingStone, and Umbrella ;) At least Opal has the word Compiler attached to it! ----- Cheers, Sean -- View this message in context: http://forum.world.st/Some-Pharo-4-Getting-Started-tips-tp4828493p4828538.h… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 26, 2015

Re: [Pharo-users] PharoCommonTools methods

by Damien Pollet

On 25 May 2015 at 19:34, Matthieu Lacaton <matthieu.lacaton(a)gmail.com> wrote: > What is the main purpose of doing this instead of actually implementing a > method ? > Being lazy: #doesNotUnderstand is implemented only once, independent of the number of different tools that will be added in the future.

May 25, 2015

Re: [Pharo-users] Accessibility?

by Thierry Goubier

Le 25/05/2015 19:58, Avdi Grimm a Ã©crit : > Some of the discussions we've had here, particularly with regard to > pointing-and-clicking being the primary, and sometimes only, way to do > something, made me wonder: are there any projects in progress for making > Pharo accessible to the blind or vision-impaired? There isn't any. I started a brltty support layer and opened it so that, say, an internship could be done with it, but nothing yet. http://smalltalkhub.com/#!/~ThierryGoubier/BRLTTY I can have very precise and effective evaluations of the behavior (or lack thereof) of Orca, NVDA and Jaws and of any Pharo based solution, if someone is interested. Thierry > -- > Avdi Grimm > http://avdi.org >

May 25, 2015

Re: [Pharo-users] Accessibility?

by Tudor Girba

The GT project does have as goal full keyboard reachability, but we still have a long way to go. But, your request sounds like a challenge. I am certainly not aware of an initiative in this direction. Do you have any pointers to literature for supporting developer needs for these category of people? Cheers, Doru On Mon, May 25, 2015 at 7:58 PM, Avdi Grimm <avdi(a)avdi.org> wrote: > Some of the discussions we've had here, particularly with regard to > pointing-and-clicking being the primary, and sometimes only, way to do > something, made me wonder: are there any projects in progress for making > Pharo accessible to the blind or vision-impaired? > > -- > Avdi Grimm > http://avdi.org > > -- www.tudorgirba.com "Every thing has its own flow"

May 25, 2015