- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12314
by Marcus Denker Jan. 20, 2011

Jan. 20, 2011

12314 ----- Issue 3560: Clean of RML -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] Issue 1426 in pharo: Auto completion does not complete symbols
by pharo＠googlecode.com Jan. 20, 2011

Jan. 20, 2011

Comment #7 on issue 1426 by DVCio...(a)gmail.com: Auto completion does not complete symbols http://code.google.com/p/pharo/issues/detail?id=1426 I believe this is not a problem: #od is taken as a literal symbol, similar to #ev, and have no auto-completion. ##od gives the suggestion for odd as ## is evaluated to literal symbol # and od is used for auto-completion; ##ev gives several suggestions.

1 1

[Pharo-project] Hapao for Test coverage!
by Vanessa PeÃ±a Jan. 20, 2011

Jan. 20, 2011

<pharo-project(a)lists.gforge.inria.fr>Hello all, We are happy to introduce you Hapao, an innovative test coverage tool which gives you an intuitive graphical representation to visually assess the quality of the coverage. For more information and download you can visit us at: http://hapao.dcc.uchile.cl/ Of course, all feedback is always welcome :) Have fun! The Hapao Team.

3 2

Re: [Pharo-project] About XML Support in the 1.2
by Marcus Denker Jan. 20, 2011

Jan. 20, 2011

On Jan 19, 2011, at 11:43 AM, Tudor Girba wrote: > Indeed, this is a problem for Moose in general. We depend on XMLSupport, but now we cannot update it in PharoDev. I would also strongly support the idea of removing XMLSupport from PharoDev. > What would be important: we need the latest version in Pharo 1.2... else how can we ever have a version where the tests are green? (not of XML, but in general) Marcus > Cheers, > Doru > > > On 19 Jan 2011, at 11:32, Fabrizio Perin wrote: > >> Hi, >> >> I have a problem with the XMLSupport version from Pharo 1.2. >> >> The problem is that I need to work with one of the last version of XMLSupport but in the pharo image 1.2 is loaded an old version of XMLSupport (I mean a version from Jan 2010). I did try to load a newer version of XMLSupport using ConfigurationOfXMLSupport but some errors make this operation impossible. >> So either Pharo-dev 1.2 load a newer (possibly the last) version of XMLSupport by default or Pharo-dev 1.2 should not load XMLSupport at all. >> >> I think that doesn't make sense to use by default such an old version, also considering that the last XMLSupport has nice and useful features like the XMLPluggableElementFactory. >> >> By avoiding to load XMLSupport in Pharo-dev 1.2 by default you let people free to use the version that they like. >> >> Thanks, >> >> Fabrizio >> > > -- > www.tudorgirba.com > > "We cannot reach the flow of things unless we let go." > > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

10 30

Re: [Pharo-project] [squeak-dev] Re: Kinect and Etoys
by Marcus Denker Jan. 20, 2011

Jan. 20, 2011

can you add an entry to http://code.google.com/p/pharo/issues/list ? thanks, Marcus On Jan 20, 2011, at 4:55 PM, Ricardo Moran wrote: > I think I found the cause of the problem: I'm updating the position of each morph inside a WorldState>>#addDeferredUIMessage:. In Pharo, this seems to be really slow. You can test it by executing this: > > | rnd | > rnd := Random new. > 100 timesRepeat: [ > WorldState addDeferredUIMessage: [ > Morph new openInWorld; center: rnd next @ rnd next * Display extent. > ] > ]. > > You'll notice it takes a couple of seconds to finish opening all the morphs, but if you remove the #addDeferredUIMessage: send, it is instantaneous. In Squeak and Etoys both versions are equally fast. > > I looked at it a little, and I think Pharo has a bug in WorldState>>#runStepsMethodsIn:. It seems it only executes one deferred ui message per step. With the implementation below the problem is fixed. > > WorldState>>#runStepMethodsIn: aWorld > "Perform periodic activity inbetween event cycles" > | queue nextInQueue| > > "If available dispatch some deferred UI Message" > queue := self class deferredUIMessages. > [(nextInQueue := queue nextOrNil) isNil] > whileFalse: [ nextInQueue value]. > > self runLocalStepMethodsIn: aWorld. > > Best regards, > Richo > > On Wed, Jan 19, 2011 at 6:40 PM, Ricardo Moran <richi.moran(a)gmail.com> wrote: > The latest stable 1.1.1. I will look at it tomorrow and try to find out more. > > On Wed, Jan 19, 2011 at 6:38 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > hi ricardo, > > which version are you using? > > Stef > > On Jan 19, 2011, at 10:32 PM, Ricardo Moran wrote: > > > I forgot to say it works in Squeak and Pharo (although in Pharo it's *painfully* slow, I don't know why yet...) > > > > Cheers > > Richo > > > > On Wed, Jan 19, 2011 at 6:04 PM, Ricardo Moran <richi.moran(a)gmail.com> wrote: > > Hi guys! > > I want to tell you some exciting news. Thanks to the ESUG Innovation Technology Awards we've been able to buy ourselves a Microsoft Kinect. We don't have a Xbox 360 yet, but that doesn't mean we can't have a little fun with it. Who needs and Xbox if you can use Kinect with Etoys? :) > > > > After seeing Stephen Howell's great work using Kinect with Scratch, we followed his steps and made it available for Etoys as well. > > See it for yourselves: http://www.youtube.com/watch?v=YnqqaHvbeqg > > > > You can find installation steps in our blog: http://tecnodacta.com.ar/gira > > > > Cheers! > > Richo > > > > > > > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

2 1

[Pharo-project] Finder question
by Mariano Martinez Peck Jan. 20, 2011

Jan. 20, 2011

Hi. It would be cool if Finder could be a little similar to RecentMessagesList. For example, doing a double click on a Message can browse its implementors. In addition, in RecentMessages you can also select/unselect items. Here in Finder is not possible? What about shortcuts? I would love to be able to do cmd+m, cmd+n, cmd+b, etc, both in RecentMessages and in Finder. cheers mariano

2 1

[Pharo-project] Problems with Recent Messages List
by Mariano Martinez Peck Jan. 20, 2011

Jan. 20, 2011

Hi, I found a couple of problems: 1) - Open a Recent Messages List and directly click to change the ordering to "by version". You will get a "MessageNotUnderstood: TimeStamp>>isByteString" 2) If we sort by date, we cannot see the class names. Maybe put the date and next to it the class name . For example: "20 January 2011 (ScriptLoader)" 3) we should clean its history in #cleanUpForRelease or in #cleanUpForProduction For the rest, it is really cool. mariano

2 1

[Pharo-project] A reset question
by Henrik Johansen Jan. 20, 2011

Jan. 20, 2011

|writeStream| writeStream := String new writeStream. writeStream nextPut: $a. writeStream reset. writeStream isEmpty. What would you expect? Cheers, Henry

3 3

Jan. 20, 2011

hi guys what should be the load or loadDefault definition if I want to load the latest version as defined by a method of this style? version02: spec <version: '0.2'> spec for: #common do: [ spec repository: 'http://www.squeaksource.com/Soup'. spec package: 'Soup-Core' with: 'Soup-Core-StephaneDucasse.8'; package: 'Soup-Tests-Core' with: 'Soup-Tests-Core-StephaneDucasse.2'; package: 'Soup-Help' with: 'Soup-Help-StephaneDucasse.2' ]. AM I correct to believe that load "self load" ^self project latestVersion load execute version02: if this is the last method version? Stef

3 2

Re: [Pharo-project] Issue 1249 in pharo: Debugger fails to launch after stacktrace is dumped to SqueakDebug file
by pharo＠googlecode.com Jan. 20, 2011

Jan. 20, 2011

Updates: Status: Closed Comment #7 on issue 1249 by marcus.d...(a)gmail.com: Debugger fails to launch after stacktrace is dumped to SqueakDebug file http://code.google.com/p/pharo/issues/detail?id=1249 i think this has been fixed. (at least I can not reproduce)

1 0