- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Where to get the latest 1.3 dev

by Marcus Denker

On Sep 13, 2011, at 4:02 PM, Torsten Bergmann wrote: > Looks like the old Hudson is down up again: https://pharo-ic.lille.inria.fr/hudson/job/Pharo%201.3/ Yes, we need to move everything to Jenkins... > https://pharo-ic.lille.inria.fr/hudson/ > and the Jenkins provides only the new 1.4 > https://ci.lille.inria.fr/pharo/ > > > The site http://www.pharo-project.org/pharo-download/unstable > also points to 1.4 while > > http://www.pharo-project.org/pharo-download/unstable-core > points to a Pharo 1.3 - but only core image. > > But where to get the latest 1.3 Dev image these days? > > Bye > T. > -- > NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! > Jetzt informieren: http://www.gmx.net/de/go/freephone > -- Marcus Denker -- http://marcusdenker.de

Sept. 13, 2011

Re: [Pharo-project] FS writestream

by Camillo Bruni

Concerning the encoding problem I would say so tooâ¦ But there's another "problem" with FS file streams, they are correctly programmed and have a 1 based index. Whereas existing FileStreams are 0 based (no clue why that..) As an example I remember that we could not dump MCZ files directly to FSFilestreams since the zip compressor relies on 0 based indexingâ¦ I guess we need a big refactoring for this to work completely.. cami On 2011-09-13, at 16:41, Lukas Renggli wrote: > Then you also need to specify an encoding. Otherwise it does not make > sense for a FSReadStream to return a String. > > Strictly speaking the FSWriteStream shouldn't accept a String as input either. > > Lukas > > On 13 September 2011 16:36, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >> or strings and widestrings. >> >> Stef >> On Sep 13, 2011, at 4:11 PM, Alexandre Bergel wrote: >> >>> Looks like there is a confusion between binary and text stream >>> >>> Alexandre >>> >>> On 13 Sep 2011, at 11:09, StÃ©phane Ducasse wrote: >>> >>>> | working stream | >>>> working := FSFilesystem disk workingDirectory. >>>> stream := (working / 'foo.txt') writeStream. >>>> stream nextPutAll: 'Hello World'. >>>> stream close. >>>> stream := (working / 'foo.txt') readStream. >>>> stream contents. >>>> returns >>>> #[72 101 108 108 111 32 87 111 114 108 100] >>>> >>>> instead of 'Hello World' >>>> >>>> Does anybody have a fix..? >>>> >>>> Stef ( editing FS chapter). >>>> >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >>> >>> >> >> >> > > > > -- > Lukas Renggli > www.lukas-renggli.ch >

Sept. 13, 2011

Re: [Pharo-project] FS writestream

by Lukas Renggli

Then you also need to specify an encoding. Otherwise it does not make sense for a FSReadStream to return a String. Strictly speaking the FSWriteStream shouldn't accept a String as input either. Lukas On 13 September 2011 16:36, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > or strings and widestrings. > > Stef > On Sep 13, 2011, at 4:11 PM, Alexandre Bergel wrote: > >> Looks like there is a confusion between binary and text stream >> >> Alexandre >> >> On 13 Sep 2011, at 11:09, StÃ©phane Ducasse wrote: >> >>> | working stream | >>> working := FSFilesystem disk workingDirectory. >>> stream := (working / 'foo.txt') writeStream. >>> stream nextPutAll: 'Hello World'. >>> stream close. >>> stream := (working / 'foo.txt') readStream. >>> stream contents. >>> Â Â Â returns >>> Â Â Â #[72 101 108 108 111 32 87 111 114 108 100] >>> >>> instead of 'Hello World' >>> >>> Does anybody have a fix..? >>> >>> Stef ( editing FS chapter). >>> >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel Â http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> > > > -- Lukas Renggli www.lukas-renggli.ch

Sept. 13, 2011

Re: [Pharo-project] FS writestream

by StÃ©phane Ducasse

or strings and widestrings. Stef On Sep 13, 2011, at 4:11 PM, Alexandre Bergel wrote: > Looks like there is a confusion between binary and text stream > > Alexandre > > On 13 Sep 2011, at 11:09, StÃ©phane Ducasse wrote: > >> | working stream | >> working := FSFilesystem disk workingDirectory. >> stream := (working / 'foo.txt') writeStream. >> stream nextPutAll: 'Hello World'. >> stream close. >> stream := (working / 'foo.txt') readStream. >> stream contents. >> returns >> #[72 101 108 108 111 32 87 111 114 108 100] >> >> instead of 'Hello World' >> >> Does anybody have a fix..? >> >> Stef ( editing FS chapter). >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > >

Sept. 13, 2011

[Pharo-project] missing basicRename:

by StÃ©phane Ducasse

rename: sourcePath ifAbsent: aBlock as: destPath ifPresent: pBlock "Rename the file referenced as sourcePath to the destination referred as destPath. Perform associate actions in case of problems." | source destination | source := self resolve: sourcePath. destination := self resolve: destPath. self basicRename: source ifAbsent: aBlock as: destination ifPresent: pBlock I went in the fs project and looked in even old version and it seems that it was not defined at all.... :(

Sept. 13, 2011

Re: [Pharo-project] FS writestream

by Alexandre Bergel

Looks like there is a confusion between binary and text stream Alexandre On 13 Sep 2011, at 11:09, StÃ©phane Ducasse wrote: > | working stream | > working := FSFilesystem disk workingDirectory. > stream := (working / 'foo.txt') writeStream. > stream nextPutAll: 'Hello World'. > stream close. > stream := (working / 'foo.txt') readStream. > stream contents. > returns > #[72 101 108 108 111 32 87 111 114 108 100] > > instead of 'Hello World' > > Does anybody have a fix..? > > Stef ( editing FS chapter). > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Sept. 13, 2011

Re: [Pharo-project] Developing on virtualized Android

by Dimitry Golubovsky

Torsten, No, I started on a real ARM device. ARM emulator was way too slow on my 2 GHz Athlon64x2. I considered it cheaper to buy an actual device (cost me $160, and I needed one anyway) than to buy a faster PC ;). That was in January 2011; now I think these devices got even cheaper. I never really considered x86 Android. Thanks. On Tue, Sep 13, 2011 at 9:53 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Dimitry, > > did you try Pharo/Squeak for android on Android x86 and virtualbox (without a device) > > http://androidspin.com/2011/01/24/howto-install-android-x86-2-2-in-virtualb… > > Is there a short howto? Would be nice for people to play with > it even without an android device... > > Thanks > Torsten > > > -- > NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! > Jetzt informieren: http://www.gmx.net/de/go/freephone > -- Dimitry Golubovsky Anywhere on the Web

Sept. 13, 2011

[Pharo-project] FS writestream

by StÃ©phane Ducasse

| working stream | working := FSFilesystem disk workingDirectory. stream := (working / 'foo.txt') writeStream. stream nextPutAll: 'Hello World'. stream close. stream := (working / 'foo.txt') readStream. stream contents. returns #[72 101 108 108 111 32 87 111 114 108 100] instead of 'Hello World' Does anybody have a fix..? Stef ( editing FS chapter).

Sept. 13, 2011

[Pharo-project] Where to get the latest 1.3 dev

by Torsten Bergmann

Looks like the old Hudson is down https://pharo-ic.lille.inria.fr/hudson/ and the Jenkins provides only the new 1.4 https://ci.lille.inria.fr/pharo/ The site http://www.pharo-project.org/pharo-download/unstable also points to 1.4 while http://www.pharo-project.org/pharo-download/unstable-core points to a Pharo 1.3 - but only core image. But where to get the latest 1.3 Dev image these days? Bye T. -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone

Sept. 13, 2011

[Pharo-project] Fix for Explorer->Browse full

by Sean P. DeNigris

You may have noticed the very annoying bug in 1.3 and 1.4, where when you try to browse the class, the browser always takes you to ByteString, no matter what's selected. This has been fixed in both 1.3 and 1.4 (http://code.google.com/p/pharo/issues/detail?id=4548) If you have a version of 1.3 dev without the fix, you can file http://forum.world.st/file/n3810137/Inspector-browseMethodFull.st Inspector-browseMethodFull.st in. Cheers, Sean -- View this message in context: http://forum.world.st/Fix-for-Explorer-Browse-full-tp3810137p3810137.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 13, 2011