- Pharo-dev - lists.pharo.org

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

by Pavel Krivanek

Igor, please publish then server versions of build scripts like build13.sh, build-kernel.sh etc. too. -- Pavel On Mon, Jul 11, 2011 at 7:47 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 11 July 2011 19:33, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: >> What I great change. I think I have asked Marcus about them like 10 times :) > > So, i think you asked for a reason? :) > Because now you have commit rights to this repository, nothing > prevents you from doing what you wanted to do :) > > The changes are quite simple: > Â - avoid using absolute paths (instead use $WORKSPACE) environment variable > all scripts are starting from: > > if [ -z "$WORKSPACE" ] ; then > Â Â Â Â WORKSPACE=`pwd` > fi > > so, you can run them on your local machine, and they will work same on server. > Of course if you don't make stupid mistakes... ( bah it's so easy to > look like an idiot with these bash scripts. I have bash/sh !!!) > > When you need to invoke VM , use PHARO_VM environment variable. Which > is set on slave to point to VM. > Like: > exec "$PHARO_VM" $PHARO_PARAM "$OUTPUT_IMAGE" "$OUTPUT_SCRIPT" -headless > > Of course, for testing freshly built VMs it may point to another > place, but scripts will remain same. > > (tomorrow i will start migrating VM jobs from hudson to jenkins) > Jenkins is more appeal and seems to be less buggy. :) > > -- > Best regards, > Igor Stasenko AKA sig. > >

July 12, 2011

Re: [Pharo-project] Pharo 1.2.1 crashing

by Mariano Martinez Peck

As Igor said, I cannot see anything weird in the dump. Someone someone knows in the VM mailing list. Cheers On Fri, Jul 8, 2011 at 12:51 PM, Bernat Romagosa < tibabenfortlapalanca(a)gmail.com> wrote: > Hi list, > > My Pharo image is crashing every now and then and I can't seem to work out > why, here's my specs: > > 'Pharo1.2.1 > Croquet Closure Cog VM [CoInterpreter VMMaker.oscog-eem.75] > unix i686 linux-gnu' > > I also attach the console dump. > > Could it be a VM bug or something? > > Cheers, > > -- > Bernat Romagosa. > -- Mariano http://marianopeck.wordpress.com

July 12, 2011

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

by Mariano Martinez Peck

Hi Igor. I was looking in the scripts and I found that the version of Pharo1.4 is "hardcoded": https://gitorious.org/pharo-build/pharo-build/blobs/master/pharo-shell-scri… Maybe you can get it from a static url like http://www.pharo-project.org/pharo-download/unstable-core or fetch the previous (successful ?) one from hudson? On Mon, Jul 11, 2011 at 7:19 PM, Igor Stasenko <siguctua(a)gmail.com> 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. > > -- Mariano http://marianopeck.wordpress.com

July 12, 2011

Re: [Pharo-project] keymappings question

by Tudor Girba

Hi, Ahh, I thought that the latest version of Keymappings handles shortcuts per morph instance. It looks like it does not, and this is bad news for me :(. I want to use them in the context of Glamour and for that I need to control the shortcuts of morph instances. How difficult is it to get it working? Cheers, Doru On 12 Jul 2011, at 01:04, Guillermo Polito wrote: > > > 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." > > > > -- www.tudorgirba.com "Value is always contextual."

July 12, 2011

[Pharo-project] MorphicModel needs serious cleaning

by Igor Stasenko

Just found that scrollbars are assigned 'slotname' when you creating them and when it comes to send events to their model, it end up in this method: use: cachedSelector orMakeModelSelectorFor: selectorBody in: selectorBlock | selector | model ifNil: [^ nil]. cachedSelector ifNil: ["Make up selector from slotname if any" selector := (slotName ifNil: [selectorBody] ifNotNil: [slotName , selectorBody]) asSymbol. (model class canUnderstand: selector) ifFalse: [(self confirm: 'Shall I compile a null response for' , Character cr asString , model class name , '>>' , selector) ifFalse: [self halt]. model class compile: (String streamContents: [:s | selector keywords doWithIndex: [:k :i | s nextPutAll: k , ' arg' , i printString]. s cr; nextPutAll: '"Automatically generated null response."'. s cr; nextPutAll: '"Add code below for appropriate behavior..."'.]) classified: 'input events' notifying: nil]] ifNotNil: [selector := cachedSelector]. ^ selectorBlock value: selector this is incredible.. -- Best regards, Igor Stasenko AKA sig.

July 12, 2011

Re: [Pharo-project] keymappings question

by Igor Stasenko

On 12 July 2011 02:04, Guillermo Polito <guillermopolito(a)gmail.com> wrote: > > > 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. > ouch, we definitely need to clean that mess :) > Hope this helps, > Guille > >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "What we can governs what we wish." >> >> >> > > -- Best regards, Igor Stasenko AKA sig.

July 12, 2011

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