- Pharo-dev - lists.pharo.org

Re: [Pharo-project] color problem?

by Erwan Douaille

Don't know, and i tried with h:s:v: and it doesn't work too, as you can see ... [image: Images intÃ©grÃ©es 1] 2012/8/8 Esteban Lorenzano <estebanlm(a)gmail.com> > Hi, > > try: > > Color r: 255 g: 255 b: 122 alpha: 255. > > AFAIK, that should bring a yellow color. And it is not. > Anyone knows why? > > Esteban > > > -- Best regards, Douaille Erwan <douaille.erwan(a)gmail.com>

Aug. 8, 2012

Re: [Pharo-project] FileSystem differences between Pharo-2.0 and Pharo-1.4

by Camillo Bruni

nope they won't work either... I changed all of that in 2.0's FS overhaul. Maybe we should port these changes back to 1.4 to support a working version of FS there. All the stream selectors in 1.4 create a FSFileStream or so, which is a incomplete reimplementation of FileStream. They might work for a very limited set of operations, but AFAIK there is a big mem leak of low level file handlers which eventually will crash the VM. Porting the changes back to 1.4 for the FileStream subpart should be a 0.5h task (for me ;)). If esteban agrees to include these changes in 1.4 I am willing to create a patch :) On 2012-08-08, at 19:32, Dale Henrichs <dhenrich(a)vmware.com> wrote: > Cami, > > How about writeStream* and readStream* are those working? It looks like you used those variants in your FileTree pull request... > > Thanks, > > Dale > > ----- Original Message ----- > | From: "Camillo Bruni" <camillobruni(a)gmail.com> > | To: Pharo-project(a)lists.gforge.inria.fr > | Sent: Wednesday, August 8, 2012 10:06:18 AM > | Subject: Re: [Pharo-project] FileSystem differences between Pharo-2.0 and Pharo-1.4 > | > | in pharo 1.4 #fileStream and #fileStreamDo: & Co are not working > | properly... > | You'll still have to use something like > | FileStream fileNamed: reference fullName > | otherwise it should more or less work. > | > | > | On 2012-08-08, at 18:36, Dale Henrichs <dhenrich(a)vmware.com> wrote: > | > | > I'm starting a port of FileTree to Pharo-2.0 and I'm planning on > | > using Pharo-1.4 (summer) to do the actual port, since I can't run > | > my development environment in Pharo-2.0 (chicken and egg problem). > | > > | > I'm wondering if there are any significant differences between the > | > FileSystem implementations on the two platforms that I should be > | > aware of... > | > > | > Dale > | > > | > | > | >

Aug. 8, 2012

Re: [Pharo-project] FileSystem differences between Pharo-2.0 and Pharo-1.4

by Dale Henrichs

Cami, How about writeStream* and readStream* are those working? It looks like you used those variants in your FileTree pull request... Thanks, Dale ----- Original Message ----- | From: "Camillo Bruni" <camillobruni(a)gmail.com> | To: Pharo-project(a)lists.gforge.inria.fr | Sent: Wednesday, August 8, 2012 10:06:18 AM | Subject: Re: [Pharo-project] FileSystem differences between Pharo-2.0 and Pharo-1.4 | | in pharo 1.4 #fileStream and #fileStreamDo: & Co are not working | properly... | You'll still have to use something like | FileStream fileNamed: reference fullName | otherwise it should more or less work. | | | On 2012-08-08, at 18:36, Dale Henrichs <dhenrich(a)vmware.com> wrote: | | > I'm starting a port of FileTree to Pharo-2.0 and I'm planning on | > using Pharo-1.4 (summer) to do the actual port, since I can't run | > my development environment in Pharo-2.0 (chicken and egg problem). | > | > I'm wondering if there are any significant differences between the | > FileSystem implementations on the two platforms that I should be | > aware of... | > | > Dale | > | | |

Aug. 8, 2012

Re: [Pharo-project] Can you say "fuel" when one of its packages is changed?

by Sean P. DeNigris

Mariano Martinez Peck wrote > > in each issue that you provide a fix touches any of the Fuel packages, > just > say "Fuel" somewhere in the issue? I added a label "Target-Fuel" to the issue tracker. Cheers, Sean -- View this message in context: http://forum.world.st/Can-you-say-fuel-when-one-of-its-packages-is-changed-… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 8, 2012

Re: [Pharo-project] FileSystem differences between Pharo-2.0 and Pharo-1.4

by Camillo Bruni

in pharo 1.4 #fileStream and #fileStreamDo: & Co are not working properly... You'll still have to use something like FileStream fileNamed: reference fullName otherwise it should more or less work. On 2012-08-08, at 18:36, Dale Henrichs <dhenrich(a)vmware.com> wrote: > I'm starting a port of FileTree to Pharo-2.0 and I'm planning on using Pharo-1.4 (summer) to do the actual port, since I can't run my development environment in Pharo-2.0 (chicken and egg problem). > > I'm wondering if there are any significant differences between the FileSystem implementations on the two platforms that I should be aware of... > > Dale >

Aug. 8, 2012

[Pharo-project] StartupPreferences gone wild in 1.4

by Sean P. DeNigris

StartupPreferences calls #loadStartupScript (loading all the StartupPreferences) ~10 times!! Also, will there be another 1.4 bug fix release? Thanks, Sean -- View this message in context: http://forum.world.st/StartupPreferences-gone-wild-in-1-4-tp4643586.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Aug. 8, 2012

[Pharo-project] FileSystem differences between Pharo-2.0 and Pharo-1.4

by Dale Henrichs

I'm starting a port of FileTree to Pharo-2.0 and I'm planning on using Pharo-1.4 (summer) to do the actual port, since I can't run my development environment in Pharo-2.0 (chicken and egg problem). I'm wondering if there are any significant differences between the FileSystem implementations on the two platforms that I should be aware of... Dale

Aug. 8, 2012

Re: [Pharo-project] I'm going to integrate Metacello into Pharo 2.0

by Dale Henrichs

Cool! Looks like I'm going to have to get busy on that FileTree rewrite so you can integrate the Metacello Preview:) Dale ----- Original Message ----- | From: "Esteban Lorenzano" <estebanlm(a)gmail.com> | To: "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> | Sent: Wednesday, August 8, 2012 3:22:52 AM | Subject: [Pharo-project] I'm going to integrate Metacello into Pharo 2.0 | | Hi, | | Just as Gofer, it is just too important to keep it outside. | Also, most of our packages now are loaded through a configuration (if | there is one god, thanks him for that :), so it will be in most | installations anyway. | Of course, I will make sure that it is unloaded in a | #cleanUpForProduction. | | Cheers, | Esteban | | |

Aug. 8, 2012

[Pharo-project] color problem?

by Esteban Lorenzano

Hi, try: Color r: 255 g: 255 b: 122 alpha: 255. AFAIK, that should bring a yellow color. And it is not. Anyone knows why? Esteban

Aug. 8, 2012

[Pharo-project] [update 2.0] #20248

by Esteban Lorenzano

20248 ----- Issue 6441: Several CompiledMethod fixes from Squeak http://code.google.com/p/pharo/issues/detail?id=6441 Issue 6444: Improve NonInteractiveUIManager>>nonInteractive: http://code.google.com/p/pharo/issues/detail?id=6444 Issue 6486: Fix Slider missing method http://code.google.com/p/pharo/issues/detail?id=6486 Issue 6488: Fix SplitterMorph http://code.google.com/p/pharo/issues/detail?id=6488 Issue 6543: GeneralScrollPane>>#newScroller is wrongly assigning red color http://code.google.com/p/pharo/issues/detail?id=6543

Aug. 8, 2012