July 2011 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] keymappings question

by Guillermo Polito

On Mon, Jul 11, 2011 at 6:24 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I wanted to play with Keymappings, but I got stuck right at the start :). > > I have two problems: > > 1. I would like to add a simple shortcut (e.g., "$o command") to a text > morph instance. So I have: > > textMorph := TextMorph new contents: 'abcdefgh'. > "what is the magic invocation here ?" > textMorph openInWindow > The shortcuts are defined via the keymapping pragma. A shortcut is attached by now to a particular class and not just an instance. Look at the examples (the ones defined by Camillo, Laurent or me) and tell me if they are understandable, hehe. > > The question is what should I write in the second line? > Nothing. Keymappings are "static" right now. > > > 2. I would like to disable existing shortcuts from the text morph. How > should I do that? > Look at where the shortcuts are defined for TextMorph and remove the declarations. And you shold also reset the KMRepository. But removing keymapping declarations doesn't guarantee the removal in TextMorph since the default -old- shortcut handling is still there. Keymapping is just intercepting them by now. Hope this helps, Guille > > > Cheers, > Doru > > -- > www.tudorgirba.com > > "What we can governs what we wish." > > > >

July 11, 2011

Re: [Pharo-project] keymappings question

by Igor Stasenko

On 12 July 2011 00:24, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > I wanted to play with Keymappings, but I got stuck right at the start :). > > I have two problems: > > 1. I would like to add a simple shortcut (e.g., "$o command") to a text morph instance. So I have: > > textMorph := TextMorph new contents: 'abcdefgh'. > "what is the magic invocation here ?" > textMorph openInWindow > > The question is what should I write in the second line? > > > 2. I would like to disable existing shortcuts from the text morph. How should I do that? > +1 id like to know too. I toying with text right now, and wanna give it a fly and make simple editor. Because i really tired to see the state of text. Maybe i'm not getting it, maybe it has to be complex. But i need to learn it myself. -- Best regards, Igor Stasenko AKA sig.

July 11, 2011

[Pharo-project] keymappings question

by Tudor Girba

Hi, I wanted to play with Keymappings, but I got stuck right at the start :). I have two problems: 1. I would like to add a simple shortcut (e.g., "$o command") to a text morph instance. So I have: textMorph := TextMorph new contents: 'abcdefgh'. "what is the magic invocation here ?" textMorph openInWindow The question is what should I write in the second line? 2. I would like to disable existing shortcuts from the text morph. How should I do that? Cheers, Doru -- www.tudorgirba.com "What we can governs what we wish."

July 11, 2011

Re: [Pharo-project] Jenkins: build scripts are now in public repository

by StÃ©phane Ducasse

Great idea. Stef On Jul 11, 2011, at 7:19 PM, Igor Stasenko wrote: > Hello, > > i put an initial version of build scripts which used by hudson/jenkins > to gitorious: > > git://gitorious.org/pharo-build/pharo-build.git > > I modified build.sh script to work well with this set up. > So, instead of locating scripts on slave, a job takes them from > "Scripts download" job, which just takes them from git. > (https://ci.lille.inria.fr/pharo/job/Scripts%20download/) > > The rest is as usual - run scripts and see what happens. > I added a job to build Pharo 1.4 using new set up.. after couple bugs, > it seems to be working well: > https://ci.lille.inria.fr/pharo/job/new%20scripts%20Pharo%201.4/ > > so, we should migrate all jobs to use these scripts , which is > publicly available through git.. > so, we don't need to manually manage these files on server anymore. > > -- > Best regards, > Igor Stasenko AKA sig. >

July 11, 2011

Re: [Pharo-project] [Moose-dev] petitparser tutorial

by StÃ©phane Ducasse

Thanks a lot doru. I would like to have chapter for PBE so we can join forces. I will read it. Stef On Jul 11, 2011, at 2:18 AM, Tudor Girba wrote: > Hi, > > I put together a tutorial for PetitParser in The Moose Book: > http://www.themoosebook.org/book/internals/petit-parser/mse > > The tutorial is meant to work with a Moose image and it is based on the same scenario as I used at the Deep into Smalltalk School: > http://www.slideshare.net/girba/petitparser-at-the-deep-into-smalltalk-scho… > http://ci.moosetechnology.org/job/moose-latest-dev/lastSuccessfulBuild/arti… > > > Feedback is always appreciated (including the negative one :)). You can either reply by mail, or leave a comment online. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Presenting is storytelling." > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

July 11, 2011

Re: [Pharo-project] About Cocoa VMs

by Igor Stasenko

On 11 July 2011 22:38, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Igor Stasenko wrote: >> >> I'd like to ask you to try and use the recent VMs built by Esteban. >> > > I am always prevented from using the newest VMs because all the plugins are > not built (Applescript, for instance, which I use extensively). > Yes, but lurking and remain silent won't helps to make it available. Now, thanks to you we know what is missing. :) > Also, when I just downloaded the newest stack vm, I was surprised that > OSProcess worked because I didn't see the plugin in the Resources folder. > What am I missing? > it's because i built it internally :) You can list internal modules by issuing: Smalltalk listBuiltinModules > Sean > > -- > View this message in context: http://forum.world.st/About-Cocoa-VMs-tp3654044p3660621.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > -- Best regards, Igor Stasenko AKA sig.

July 11, 2011

Re: [Pharo-project] About Cocoa VMs

by Sean P. DeNigris

Igor Stasenko wrote: > > I'd like to ask you to try and use the recent VMs built by Esteban. > I am always prevented from using the newest VMs because all the plugins are not built (Applescript, for instance, which I use extensively). Also, when I just downloaded the newest stack vm, I was surprised that OSProcess worked because I didn't see the plugin in the Resources folder. What am I missing? Sean -- View this message in context: http://forum.world.st/About-Cocoa-VMs-tp3654044p3660621.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 11, 2011

Re: [Pharo-project] Jenkins: build scripts are now in public repository

by Pavel Krivanek

On Mon, Jul 11, 2011 at 8:28 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 11 July 2011 20:08, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >> On Mon, Jul 11, 2011 at 8:00 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >>> On 11 July 2011 19:53, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >>>> Great, thank you, >>>> >>>> what about to create wiki page with configuration descriptions? >>> >>> what you meant by configuration descriptions? you mean job descriptions? >>> Like: "This job runs a, b then c" ? >> >> No, I mean description of the job configuration together with >> installation instructions by Lukas >> (https://github.com/renggli/builder) something like: >> >> Project name: PharoKernel-Core-1.4 >> Source Code Management: none >> Execute shell Command: >> /var/lib/jenkins/builder/build-kernel.sh -t PharoCore-1.4 -c >> exportAccuny -i PharoKernel-Gofer-1.4 -s loadCore -s initCore -o >> PharoKernel-Core-1.4 >> Archive the artifacts: **/*.image, **/*.changes >> etc. >> >> So everyone can have the same CI settings and simply create own. >> > > Why forcing people to do additional manual work? > I just installed a plugin > (https://wiki.jenkins-ci.org/display/JENKINS/Extended+Read+Permission+Plugin) > so anonymous users can see the jobs configurations > like this one: > https://ci.lille.inria.fr/pharo/job/new%20scripts%20Pharo%201.4/configure > coool :-) -- Pavel

July 11, 2011

Re: [Pharo-project] Jenkins: build scripts are now in public repository

by Igor Stasenko

On 11 July 2011 20:08, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: > On Mon, Jul 11, 2011 at 8:00 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: >> On 11 July 2011 19:53, Pavel Krivanek <pavel.krivanek(a)gmail.com> wrote: >>> Great, thank you, >>> >>> what about to create wiki page with configuration descriptions? >> >> what you meant by configuration descriptions? you mean job descriptions? >> Like: "This job runs a, b then c" ? > > No, I mean description of the job configuration together with > installation instructions by Lukas > (https://github.com/renggli/builder) something like: > > Project name: PharoKernel-Core-1.4 > Source Code Management: none > Execute shell Command: > /var/lib/jenkins/builder/build-kernel.sh -t PharoCore-1.4 -c > exportAccuny -i PharoKernel-Gofer-1.4 -s loadCore -s initCore -o > PharoKernel-Core-1.4 > Archive the artifacts: **/*.image, **/*.changes > etc. > > So everyone can have the same CI settings and simply create own. > Why forcing people to do additional manual work? I just installed a plugin (https://wiki.jenkins-ci.org/display/JENKINS/Extended+Read+Permission+Plugin) so anonymous users can see the jobs configurations like this one: https://ci.lille.inria.fr/pharo/job/new%20scripts%20Pharo%201.4/configure > -- Pavel > -- Best regards, Igor Stasenko AKA sig.

July 11, 2011

Re: [Pharo-project] Another OB2 issue ( Fwd: [RSUG] Ð ÐµÐºÑÑÑÐ¸Ð²Ð½ÑÐµ Ð¾ÑÐ¸Ð±ÐºÐ¸)

by Lukas Renggli

2011/7/11 Igor Stasenko <siguctua(a)gmail.com>: > 2011/7/11 Lukas Renggli <renggli(a)gmail.com>: >> What is OB2? > > OMenuMorph is part of OmniBrowser, no? No. > Or OCompletion? Heck i have no idea :) Looks like it, I don't have this class in my images. Likely it needs to be adapted to the changes of ECMenuMorph. Lukas -- Lukas Renggli www.lukas-renggli.ch

July 11, 2011