- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3677 in pharo: A to:do: loop cannot modify the limit inside the block

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #1 on issue 3677 by nicolas....(a)gmail.com: A to:do: loop cannot modify the limit inside the block http://code.google.com/p/pharo/issues/detail?id=3677 SLICE-Issue-3677-DoNotDecompileAWhileLoopIntoAToDoLoopWhenTheLoopWouldModifyTheLimit-nice.1 Test and fix from trunk

March 26, 2011

[Pharo-project] Issue 3882 in pharo: Can't scale imported graphic

by pharo＠googlecode.com

Status: Accepted Owner: hilaire....(a)gmail.com Labels: Type-ReportDefect Milestone-1.2 Importance-High New issue 3882 by hilaire....(a)gmail.com: Can't scale imported graphic http://code.google.com/p/pharo/issues/detail?id=3882 With Pharo 1.2 A DrGeo user dragging and dropping a picture in DrGeo related me the graphic can't be scaled from the halo scale icon. It was possible in the past, what's wrong? When rotating an image morph, it mutates as a transformation morph (TransformationMorph), then you can scale it. Scaling could have the same behavior. Sadly I don't see where it can be done. The logic seems rather complicated

March 26, 2011

Re: [Pharo-project] Issue 453 in pharo: we need a way to fold a package into the system

by pharo＠googlecode.com

Updates: Status: Closed Comment #6 on issue 453 by marcus.d...(a)gmail.com: we need a way to fold a package into the system http://code.google.com/p/pharo/issues/detail?id=453 I added this as an entry to the general wishlist: http://code.google.com/p/pharo/wiki/IdeasToImplement

March 26, 2011

Re: [Pharo-project] Scaling dropped graphic

by Hilaire Fernandes

Hello Denis, I have noted when you rotate the image morph mutates to transformation morph (TransformationMorph), then you can scale it. So a solution is that when scaling the image morph mutates to a transformation morph as well. Sadly I don't see where it could be done. Hilaire Le 26/03/2011 17:58, Denis Kudriashov a Ã©crit : > Hello Hilaire > > It's because in past image opened in World by ScetchMorph. Now Image > morph used for this. But it is not support scaling by resizing morph. > ScetchMorph were removed from Pharo. > Maybe something similar exists in system. > > 2011/3/26 Hilaire Fernandes <hilaire.fernandes(a)gmail.com > <mailto:hilaire.fernandes@gmail.com>> > > A DrGeo user dragging and dropping a picture in DrGeo related me the > graphic can't be scaled from the halo scale icon. It was possible in the > past, what's wrong? > > DrGeo version was based on Pharo 1.2. > > Hilaire > > === > 2. Open Graphic in a Window - allows me to drop in the graphic, but it > does not scale/zoom with the geometry. > > > > -- > Education 0.2 -- http://blog.ofset.org/hilaire > > > -- Education 0.2 -- http://blog.ofset.org/hilaire

March 26, 2011

Re: [Pharo-project] Issue 2841 in pharo: Heap equality should be transitive

by pharo＠googlecode.com

Updates: Status: FixProposed Comment #4 on issue 2841 by nicolas....(a)gmail.com: Heap equality should be transitive http://code.google.com/p/pharo/issues/detail?id=2841 (No comment was entered for this change.)

March 26, 2011

Re: [Pharo-project] Issue 2841 in pharo: Heap equality should be transitive

by pharo＠googlecode.com

Comment #3 on issue 2841 by nicolas....(a)gmail.com: Heap equality should be transitive http://code.google.com/p/pharo/issues/detail?id=2841 SLICE-Issue-2841-HeapEqualityShouldBeTransitive-ButHeapShouldNotBeSequenceable-nice.1 Author: nice I merged trunk changes and also moved Heap off SequenceableCollection hierarchy. I removed plenty of Sequenceable assumptions from HeapTests, and also some assumptions about equality in IntervalTests. I forbid usage of #at: #at:put: #removeAt:, that's not a legitimate API for a Heap. Only #first #add: #removeFirst #remove: shall be used. Of course, one thing remain to be done: move Heap to another package than Collections-Sequenceable. I didn't do it for at least two reasons: 1) I down't know how to classify a Heap, it's Ordered (partially), not Unordered, and not Sequenceable. 2) Heap must not be temporarily removed because used in Delay and World alarms, so package load order will be very important. I let the experts of smooth upgrading do it.

March 26, 2011

Re: [Pharo-project] Scaling dropped graphic

by Denis Kudriashov

Hello Hilaire It's because in past image opened in World by ScetchMorph. Now Image morph used for this. But it is not support scaling by resizing morph. ScetchMorph were removed from Pharo. Maybe something similar exists in system. 2011/3/26 Hilaire Fernandes <hilaire.fernandes(a)gmail.com> > A DrGeo user dragging and dropping a picture in DrGeo related me the > graphic can't be scaled from the halo scale icon. It was possible in the > past, what's wrong? > > DrGeo version was based on Pharo 1.2. > > Hilaire > > === > 2. Open Graphic in a Window - allows me to drop in the graphic, but it > does not scale/zoom with the geometry. > > > > -- > Education 0.2 -- http://blog.ofset.org/hilaire > > >

March 26, 2011

Re: [Pharo-project] COG VM Locale?

by Hilaire Fernandes

Thanks Igor! Hilaire Le 26/03/2011 14:15, Igor Stasenko a Ã©crit : > > On 26 March 2011 08:02, Hilaire Fernandes <hilaire.fernandes(a)gmail.com> wrote: >> Is it likely it'll be fixed? If so when? >> I need to know so I can move to plan B if necessary. >> >> http://code.google.com/p/cog/issues/detail?id=1 >> > > I will take a look at it. But i'm not sure if i can fix that. > >> Hilaire >> >> -- >> Education 0.2 -- http://blog.ofset.org/hilaire >> >> >> > > > -- Education 0.2 -- http://blog.ofset.org/hilaire

March 26, 2011

[Pharo-project] Scaling dropped graphic

by Hilaire Fernandes

A DrGeo user dragging and dropping a picture in DrGeo related me the graphic can't be scaled from the halo scale icon. It was possible in the past, what's wrong? DrGeo version was based on Pharo 1.2. Hilaire === 2. Open Graphic in a Window - allows me to drop in the graphic, but it does not scale/zoom with the geometry. -- Education 0.2 -- http://blog.ofset.org/hilaire

March 26, 2011

Re: [Pharo-project] Issue 2841 in pharo: Heap equality should be transitive

by pharo＠googlecode.com

Comment #2 on issue 2841 by nicolas....(a)gmail.com: Heap equality should be transitive http://code.google.com/p/pharo/issues/detail?id=2841 I also think it is a mistake to inherit from TSortable. TSortable implements a mergeSort algorithm. Heap has it's own idea on how it should sort, so this inheritance does not have much sense. Just using (Heap asArray sort) shall be enough.

March 26, 2011