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

Re: [Pharo-project] pharo0.1-10373dev09.07.2: Contect Menues defective on Vista

by StÃ©phane Ducasse

I guess that you can add bug entry even if you are not registered. stef On Jul 12, 2009, at 6:58 PM, Andreas Leidig wrote: > Hi all, > > context menues do not work in pharo0.1-10373dev09.07.2 on Vista. Did you try to bring a debugger (alt .) because I got a similar problem after loading some packages. > > I experienced the same problem in the previous version. > > Could you pls. add me to code.google.com, so that I can submit that > issue? > > > Cheers, > > Andreas > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 12, 2009

Re: [Pharo-project] Pharo VM setup problem: where is pharo-vm-0.15.1b-linux source package available?

by Mariano Martinez Peck

Thanks Adrian! I didn't find any page related with this. What do you think about creating a page called "ideas to implement". I can put there this topic :) Thanks Mariano On Sun, Jul 12, 2009 at 8:44 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > Hi Mariano, > > I added you to the Pharo Google code project. > > Adrian > > > On Jul 11, 2009, at 21:13 , Mariano Martinez Peck wrote: > > > But I don't have permissions in google code wiki :( > > > > On Sat, Jul 11, 2009 at 3:38 AM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr > >> wrote: > > > >> we can use the wiki (or the inria crappy site :)) > >> > >> Stef > >> > >> On Jul 10, 2009, at 11:42 PM, Mariano Martinez Peck wrote: > >> > >>> Stef: where should I put this type of things so that not to forget > >>> it ? > >>> > >>> Google code seems not to have tickets that aren't bugs...or I don't > >>> see them > >>> > >>> Best, > >>> > >>> Mariano > >>> > >>> On Thu, Jul 2, 2009 at 2:23 PM, StÃ©phane Ducasse < > >> stephane.ducasse(a)inria.fr > >>>> wrote: > >>> Thanks for the idea. > >>> this would be nice to have a pointer to a forge for the vm code. > >>> > >>> Stef > >>> > >>>> Hi Mariano, > >>>> > >>>> I welcome your decision. More reasons: > >>>> > >>>> - Most linux distributions do not have a standard configuration. > >>>> If you cannot go through the configuration/make/install cycle, a > >>>> package may simply not run on a certain target system. > >>>> If you cannot go through these cycles, your possibilities to fix > >>>> that are very limited. > >>>> > >>>> - Without sources, consumers cannot directly contribute to the > >>> defect > >>>> tracking, fixing or development process > >>>> > >>>> > >>>> Cheers, > >>>> > >>>> Andreas > >>>> > >>>> > >>>> > >>>> Mariano Martinez Peck schrieb: > >>>>> I also think adding sources to Pharo webpage is a good idea. I saw > >>>>> a lot of > >>>>> people, who say "I wont use an enviorment in production that I > >>>>> cannot have > >>>>> the code and build it by myself". And I think they are correct! > >>>>> > >>>>> > >>>>> On Wed, Jul 1, 2009 at 2:33 PM, Andreas Leidig < > >> Andreas.Leidig(a)gmx.net > >>>>>> wrote: > >>>>> > >>>>>> Dear List, > >>>>>> > >>>>>> who has/where is pharo-vm-0.15.1b-linux source package? > >>>>>> > >>>>>> I have a setup problem which I think I can determine or even > >>>>>> solve > >>>>>> with > >>>>>> the sources. > >>>>>> > >>>>>> > >>>>>> Cheers, > >>>>>> > >>>>>> Andreas > >>>>>> > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Pharo-project mailing list > >>>>>> Pharo-project(a)lists.gforge.inria.fr > >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- > >>> project > >>>>>> > >>>>> > >>>>> > >>>>> > >>> > ------------------------------------------------------------------------ > >>>>> > >>>>> _______________________________________________ > >>>>> Pharo-project mailing list > >>>>> Pharo-project(a)lists.gforge.inria.fr > >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- > >>>>> project > >>>> > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> Pharo-project(a)lists.gforge.inria.fr > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 12, 2009

Re: [Pharo-project] apparently versions seems to be broken

by Mariano Martinez Peck

On Sun, Jul 12, 2009 at 3:53 AM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > > Wow! I didn't know about this feature :( It is like the > > "available" of VAST > > Is there an example in SqueakByExample about it? If not, we can add > > one :) > > Or to PharoByExample! > > It would nice to have it working. +99999 a lot of times I remove a method and then regrated about that :( > > > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 12, 2009

[Pharo-project] pharo0.1-10373dev09.07.2: Contect Menues defective on Vista

by Andreas Leidig

Hi all, context menues do not work in pharo0.1-10373dev09.07.2 on Vista. I experienced the same problem in the previous version. Could you pls. add me to code.google.com, so that I can submit that issue? Cheers, Andreas

July 12, 2009

Re: [Pharo-project] problem with TextMorph>>handleInteraction:fromEvent:

by StÃ©phane Ducasse

Thanks I was doing the same. Can you chekc the next update and let me know? Stef On Jul 12, 2009, at 6:12 PM, Esteban Lorenzano wrote: > Hi, > is just #handleInteraction: in pharo (my mistake) > I'm uploading a changeset. > > Cheers, > Esteban > > <TextMorphFix.1.cs> > > > On 2009-07-12 12:58:42 -0300, StÃ©phane Ducasse <stephane.ducasse-MZpvjPyXg2s(a)public.gmane.org > > said: > > in TextMorph I do not see this method > > On Jul 12, 2009, at 4:25 PM, Esteban Lorenzano wrote: > > Ouch, bad method, please replace: #handleInteraction:fromEvent: (the > squeak event), for #handleInteraction: (the pharo equivallent) > > Cheers, > Esteban > > On 2009-07-12 11:22:47 -0300, Esteban Lorenzano > <estebanlm-Re5JQEeQqe8AvxtiuMwx3w(a)public.gmane.org> said: > > Hi, > I'm working to make Algernon works on pharo, and I found what seems > to > be a bug (or at least something that "revesls" a bug), in > TextMorph>>handleInteraction: > This is what happens: the Algernon starts and you type a class, > then go > inside to look for a method, and that sends a keyStroke: to a new > TextMorph, who sends a #handleInteraction:fromEvent:. > So... old implementation on #handleInteraction:fromEvent: had a first > line removed in new implementation: > > self editor sensor: (KeyboardBuffer new startingEvent: evt). > > > The problem is this: #editor message instances editor attribute if > nil. > Now... that line is not anymore, introducing a DNU when sending a > subsecuent message to editor attribute. > I "solved" it bu changing this line: > > oldEditor := editor. > > > for this other: > > oldEditor := self editor. > > > (who restores the editor instantiation). > > What I don't know is: > > a) is this a bug? > b) the bug is there or is a collateral damage? > c) my hack really solves the problem? > d) is possible to introduce this bugfix into a new version? > > Cheers, > Esteban > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project-bM+ny+RY8h+a+bCvCPl5/gCzwTLBPCX0(a)public.gmane.org > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 12, 2009

Re: [Pharo-project] problem with TextMorph>>handleInteraction:fromEvent:

by Esteban Lorenzano

On 2009-07-12 12:06:46 -0300, Michael Rueger <m.rueger(a)acm.org> said: > On Sun, Jul 12, 2009 at 4:22 PM, Esteban > Lorenzano<estebanlm(a)gmail.com> wrote: > >> What I don't know is: >> >> a) is this a bug? >> b) the bug is there or is a collateral damage? >> c) my hack really solves the problem? >> d) is possible to introduce this bugfix into a new version? > > This part was refactored, the variable editor shouldn't be used anymore IIRC. > > Michael But there are several places in TextMorph using it :(

July 12, 2009

Re: [Pharo-project] problem with TextMorph>>handleInteraction:fromEvent:

by Esteban Lorenzano

Hi, is just #handleInteraction: in pharo (my mistake) I'm uploading a changeset. Cheers, Esteban On 2009-07-12 12:58:42 -0300, StÃ©phane Ducasse <stephane.ducasse-MZpvjPyXg2s(a)public.gmane.org > said: in TextMorph I do not see this method On Jul 12, 2009, at 4:25 PM, Esteban Lorenzano wrote: Ouch, bad method, please replace: #handleInteraction:fromEvent: (the squeak event), for #handleInteraction: (the pharo equivallent) Cheers, Esteban On 2009-07-12 11:22:47 -0300, Esteban Lorenzano <estebanlm-Re5JQEeQqe8AvxtiuMwx3w(a)public.gmane.org> said: Hi, I'm working to make Algernon works on pharo, and I found what seems to be a bug (or at least something that "revesls" a bug), in TextMorph>>handleInteraction: This is what happens: the Algernon starts and you type a class, then go inside to look for a method, and that sends a keyStroke: to a new TextMorph, who sends a #handleInteraction:fromEvent:. So... old implementation on #handleInteraction:fromEvent: had a first line removed in new implementation: self editor sensor: (KeyboardBuffer new startingEvent: evt). The problem is this: #editor message instances editor attribute if nil. Now... that line is not anymore, introducing a DNU when sending a subsecuent message to editor attribute. I "solved" it bu changing this line: oldEditor := editor. for this other: oldEditor := self editor. (who restores the editor instantiation). What I don't know is: a) is this a bug? b) the bug is there or is a collateral damage? c) my hack really solves the problem? d) is possible to introduce this bugfix into a new version? Cheers, Esteban _______________________________________________ Pharo-project mailing list Pharo-project-bM+ny+RY8h+a+bCvCPl5/gCzwTLBPCX0(a)public.gmane.org http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 12, 2009

Re: [Pharo-project] problem with TextMorph>>handleInteraction:fromEvent:

by StÃ©phane Ducasse

Oops I checked and the code is full of editor direct accesses Stef On Jul 12, 2009, at 5:06 PM, Michael Rueger wrote: > On Sun, Jul 12, 2009 at 4:22 PM, Esteban > Lorenzano<estebanlm(a)gmail.com> wrote: > >> What I don't know is: >> >> a) is this a bug? >> b) the bug is there or is a collateral damage? >> c) my hack really solves the problem? >> d) is possible to introduce this bugfix into a new version? > > This part was refactored, the variable editor shouldn't be used > anymore IIRC. > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 12, 2009

Re: [Pharo-project] problem with TextMorph>>handleInteraction:fromEvent:

by StÃ©phane Ducasse

in TextMorph I do not see this method On Jul 12, 2009, at 4:25 PM, Esteban Lorenzano wrote: > Ouch, bad method, please replace: #handleInteraction:fromEvent: (the > squeak event), for #handleInteraction: (the pharo equivallent) > > Cheers, > Esteban > > On 2009-07-12 11:22:47 -0300, Esteban Lorenzano > <estebanlm(a)gmail.com> said: > >> Hi, >> I'm working to make Algernon works on pharo, and I found what seems >> to >> be a bug (or at least something that "revesls" a bug), in >> TextMorph>>handleInteraction: >> This is what happens: the Algernon starts and you type a class, >> then go >> inside to look for a method, and that sends a keyStroke: to a new >> TextMorph, who sends a #handleInteraction:fromEvent:. >> So... old implementation on #handleInteraction:fromEvent: had a first >> line removed in new implementation: >> >> self editor sensor: (KeyboardBuffer new startingEvent: evt). >> >> >> The problem is this: #editor message instances editor attribute if >> nil. >> Now... that line is not anymore, introducing a DNU when sending a >> subsecuent message to editor attribute. >> I "solved" it bu changing this line: >> >> oldEditor := editor. >> >> >> for this other: >> >> oldEditor := self editor. >> >> >> (who restores the editor instantiation). >> >> What I don't know is: >> >> a) is this a bug? >> b) the bug is there or is a collateral damage? >> c) my hack really solves the problem? >> d) is possible to introduce this bugfix into a new version? >> >> Cheers, >> Esteban > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 12, 2009

Re: [Pharo-project] problem with TextMorph>>handleInteraction:fromEvent:

by Michael Rueger

On Sun, Jul 12, 2009 at 4:22 PM, Esteban Lorenzano<estebanlm(a)gmail.com> wrote: > What I don't know is: > > a) is this a bug? > b) the bug is there or is a collateral damage? > c) my hack really solves the problem? > d) is possible to introduce this bugfix into a new version? This part was refactored, the variable editor shouldn't be used anymore IIRC. Michael

July 12, 2009