January 2014 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] IncompatibleLayoutConflict with NativeBoost in recent #30700

by Torsten Bergmann

Igor wrote: >i start feeling guilty that NB uses anonymous classes, which brings so much problems to everyone... :) So now you should really be ashamed and repair the mess you created :) Bye T.

Jan. 16, 2014

Re: [Pharo-dev] IncompatibleLayoutConflict with NativeBoost in recent #30700

by Igor Stasenko

i start feeling guilty that NB uses anonymous classes, which brings so much problems to everyone... :) On 16 January 2014 20:54, Torsten Bergmann <astares(a)gmx.de> wrote: > OK, any expert in the new class builder who could help here? > > Thx > T. > -- Best regards, Igor Stasenko.

Jan. 16, 2014

Re: [Pharo-dev] Smalltalk Impact

by Hilaire Fernandes

Le 16/01/2014 12:55, H. Hirzel a Ã©crit : >>> âWe are not payed to work on Squeakâ, that is what I got toldâ¦ > > Probably correct at that time... It doesn't matter. The silliness of such answer is the lack of vision and lack of community empowerment. > Noteworthy however: Scratch is successful in spite of being built on a > early version of Squeak. I see this has an extremely weakness. Imagine Java applications forking Java, a total nonsense too expensive in the long term. Hopefully Smalltalk Scratch is being ported to the recent Pharo and saved from a long and slow bits death. And more important: it is not a fork anymore. We are greatfull to the new Pharo Smalltalk vessel. Its constant care to tiers developers willing to develop and design standalone Smalltalk application with an opensource Smalltalk environment really open perspective for the Smalltalk community build up. The vision is clear, the target on sight! > The situation of Etoys to the contrary is not so clear. A comparison > needs to consider more factors than just the platform it is built > on.... Well, each one should take the share it deserves: forking was decided as the path for Etoys, so now Bonne chance and bon voyage... Hilaire -- Dr. Geo http://drgeo.eu

Jan. 16, 2014

Re: [Pharo-dev] errorImproperStore error because of change in GRPharoPlatform>>readWriteByteStream

by Johan Brichau

Sabine, This might be a bug in Grease 1.1 for Pharo3 because Grease 1.0 has identical code for that method in Pharo 2 and 3. The timestamp of that method in Grease1.1 is even older than the one in Grease1.0... so it definitely smells buggy... Johan On 16 Jan 2014, at 17:41, Sabine KnÃ¶fel <sabine.knoefel(a)gmail.com> wrote: > Hi, > > I am migrating from Pharo 2.0 to Pharo3.0 > > My updateRoot contains the following statement: > > updateRoot: aHtmlRoot > aHtmlRoot link url: RKALibrary / #mainStylesLess; relationship: > 'stylesheet/less'; beCss. > > In Pharo 3.0 I get ByteArray errorImproperStore error (Pharo2.0 works) > > When debugging into, I see: > In Pharo 2.0 > > GRPharoPlatform>>readWriteByteStream > "ByteArray based read write stream" > ^ RWBinaryOrTextStream on: (ByteArray new: 4096) > > In Pharo 3.0 > GRPharoPlatform>>readWriteByteStream > "ByteArray based read write stream" > ^ ReadWriteStream on: (ByteArray new: 4096) > > This is the reason for the error improperStore error. > If I change from ReadWriteStream to RWBinaryOrTextStream, it works. > > Can anyone fix this or is my conclusion wrong? > Regards > Sabine > > > > > > -- > View this message in context: http://forum.world.st/errorImproperStore-error-because-of-change-in-GRPharo… > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

Jan. 16, 2014

Re: [Pharo-dev] IncompatibleLayoutConflict with NativeBoost in recent #30700

by Torsten Bergmann

Jan. 16, 2014

RPackage vs. MCPackagew

by Sean P. DeNigris

What is the rationale behind not immediately creating an MCPackage when a new RPackage is created? ----- Cheers, Sean -- View this message in context: http://forum.world.st/RPackage-vs-MCPackagew-tp4737326.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 16, 2014

Re: [Pharo-dev] [Showstopper] Issue 12667: Showstopping Bug in LRUCache

by Sean P. DeNigris

Let's continue the discussion in the issue. I added some more info thereâ¦ https://pharo.fogbugz.com/default.asp?12667 ----- Cheers, Sean -- View this message in context: http://forum.world.st/Showstopper-Issue-12667-Showstopping-Bug-in-LRUCache-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 16, 2014

Re: [Pharo-dev] Two videos to explain what we do when integrating a fix.

by Sven Van Caekenberghe

BTW: there is an error in the second github download, it is the wrong project, must be pharo-update. On 16 Jan 2014, at 20:20, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 16 Jan 2014, at 19:56, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > >> too many fan wanted to watch these amazing videosâ¦. :) >> Should put them on youtbue but I dod not how. > > We have an account for Pharo, I can show you next week. > >> On 16 Jan 2014, at 19:50, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >> >>> StÃ©phane Ducasse wrote >>>> Can you retry? >>> >>> Huh, works now. Thanks :) >>> >>> >>> >>> ----- >>> Cheers, >>> Sean >>> -- >>> View this message in context: http://forum.world.st/Two-videos-to-explain-what-we-do-when-integrating-a-f… >>> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >>> >> >> > >

Jan. 16, 2014

Re: [Pharo-dev] [Showstopper] Issue 12667: Showstopping Bug in LRUCache

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > Do you have a PharoDebug.log ? LRUCache(Object)>>error: Receiver: <<error during printing>> Arguments and temporary variables: aString: 'No factory specified' Receiver's instance variables: store: nil cachedValues: nil reloadPolicy: nil clock: nil loadTimes: nil lruList: a DoubleLinkedList keyIndex: a Dictionary({#bottom. 13. (Color r: 0.42 g: 0.42 b: 0.42 alpha: 1.0)...etc... LRUCache(Cache)>>at: Receiver: <<error during printing>> Arguments and temporary variables: key: {#top. 13.0. (Color r: 0.743 g: 0.743 b: 0.743 alpha: 1.0)} Receiver's instance variables: store: nil cachedValues: nil reloadPolicy: nil clock: nil loadTimes: nil lruList: a DoubleLinkedList keyIndex: a Dictionary({#bottom. 13. (Color r: 0.42 g: 0.42 b: 0.42 alpha: 1.0)...etc... ScrollBar class>>arrowOfDirection:size:color: Receiver: ScrollBar Arguments and temporary variables: aSymbol: #top finalSizeInteger: 13.0 aColor: (Color r: 0.743 g: 0.743 b: 0.743 alpha: 1.0) Receiver's instance variables: superclass: Slider methodDict: a MethodDictionary(#adoptGradientColor:->ScrollBar>>#adoptGradientC...etc... format: 184 layout: a FixedLayout instanceVariables: #('upButton' 'downButton' 'pagingArea' 'scrollDelta' 'pageDe...etc... organization: a ClassOrganization subclasses: {GeneralScrollBar} name: #ScrollBar classPool: <<error during printing>> ScrollBar>>upImage ... ----- Cheers, Sean -- View this message in context: http://forum.world.st/Showstopper-Issue-12667-Showstopping-Bug-in-LRUCache-… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Jan. 16, 2014

Re: [Pharo-dev] Two videos to explain what we do when integrating a fix.

by Marcus Denker

On 16 Jan 2014, at 19:56, Pharo4Stef <pharo4Stef(a)free.fr> wrote: > too many fan wanted to watch these amazing videosâ¦. :) > Should put them on youtbue but I dod not how. We have an account for Pharo, I can show you next week. > On 16 Jan 2014, at 19:50, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > >> StÃ©phane Ducasse wrote >>> Can you retry? >> >> Huh, works now. Thanks :) >> >> >> >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/Two-videos-to-explain-what-we-do-when-integrating-a-f… >> Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >> > >

Jan. 16, 2014