November 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] FileSystem memory bug?

by Martin Dias

Sven, you are right. I checked that MemoryHandle>>readStream creates a ReadStream on it's internal byte array. Then, the answer to #next it's not a Character but a SmallInteger. Ok, anyway I can avoid using `FileSystem memory`. I was just trying to make my test suite not use the physical disk. Just an optimization... Thanks, MartÃn On Fri, Nov 8, 2013 at 3:04 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > Thanks, but it's the same: the streams are instances of WriteStream and > ReadStream... the implementation of #ascii in ReadStream is empty, and > WriteStream doesn't respond to #ascii. > > > > > > > On Fri, Nov 8, 2013 at 2:19 PM, Max Leske <maxleske(a)gmail.com> wrote: > >> >> On 08.11.2013, at 13:59, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> > Hi Martin, >> > >> > I would guess that the stream created by the memory filesystem are >> binary, not character, as STON expects. >> >> Good point, although currently ascii mode is still default I think. >> Try sending #ascii to the stream. That might help. >> >> > >> > Sven >> > >> > On 08 Nov 2013, at 13:55, Martin Dias <tinchodias(a)gmail.com> wrote: >> > >> >> Hi, >> >> >> >> I'm working in latest Pharo (30577) with STON (bleeding edge) and I >> get MNU:SmallInteger>>isSeparator when I evaluate the code below. Is my >> code wrong? The idea is to make my test suite work in the memory file >> system. >> >> >> >> | fileSystem | >> >> fileSystem := FileSystem memory. >> >> >> >> (fileSystem / 'file.txt') ensureCreateFile. >> >> >> >> STON writer >> >> on: (fileSystem / 'file.txt') writeStream; >> >> nextPut: 'hi'. >> >> >> >> STON reader >> >> on: (fileSystem / 'file.txt') readStream; >> >> next. >> >> >> >> Thanks in advance. >> >> >> >> MartÃn >> > >> > >> >> >> >

Nov. 8, 2013

PharoSounds is not heard

by Mariano

Hello All, I am trying to use sound package, but I couldn't make it work. I didn't get any errors but the sounds is not heard. I tested it on Ubuntu and Windows XP, and in both platform the behavior was the same. What I did is the following: 1. Add the Montichello repository "http://smalltalkhub.com/mc/PharoExtras/Sound/main" 2. Then load the ConfigurationOfPharoSound project. 3. Then evaluate (ConfigurationOfPharoSound project version: '6.0') load. 4. Enable the sound with: SoundSystem soundEnabled: true. 5. Test if sound works with: FMSound clarinet2 play (SampledSound fromWaveFileNamed: 'mainLoopMG2.wav') play I will appreciate if someone could help with this. Best regards, Mariano

Nov. 8, 2013

Re: [Pharo-dev] FileSystem memory bug?

by Martin Dias

Thanks, but it's the same: the streams are instances of WriteStream and ReadStream... the implementation of #ascii in ReadStream is empty, and WriteStream doesn't respond to #ascii. On Fri, Nov 8, 2013 at 2:19 PM, Max Leske <maxleske(a)gmail.com> wrote: > > On 08.11.2013, at 13:59, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > > Hi Martin, > > > > I would guess that the stream created by the memory filesystem are > binary, not character, as STON expects. > > Good point, although currently ascii mode is still default I think. > Try sending #ascii to the stream. That might help. > > > > > Sven > > > > On 08 Nov 2013, at 13:55, Martin Dias <tinchodias(a)gmail.com> wrote: > > > >> Hi, > >> > >> I'm working in latest Pharo (30577) with STON (bleeding edge) and I get > MNU:SmallInteger>>isSeparator when I evaluate the code below. Is my code > wrong? The idea is to make my test suite work in the memory file system. > >> > >> | fileSystem | > >> fileSystem := FileSystem memory. > >> > >> (fileSystem / 'file.txt') ensureCreateFile. > >> > >> STON writer > >> on: (fileSystem / 'file.txt') writeStream; > >> nextPut: 'hi'. > >> > >> STON reader > >> on: (fileSystem / 'file.txt') readStream; > >> next. > >> > >> Thanks in advance. > >> > >> MartÃn > > > > > > >

Nov. 8, 2013

Re: [Pharo-dev] FileSystem memory bug?

by Max Leske

On 08.11.2013, at 13:59, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > Hi Martin, > > I would guess that the stream created by the memory filesystem are binary, not character, as STON expects. Good point, although currently ascii mode is still default I think. Try sending #ascii to the stream. That might help. > > Sven > > On 08 Nov 2013, at 13:55, Martin Dias <tinchodias(a)gmail.com> wrote: > >> Hi, >> >> I'm working in latest Pharo (30577) with STON (bleeding edge) and I get MNU:SmallInteger>>isSeparator when I evaluate the code below. Is my code wrong? The idea is to make my test suite work in the memory file system. >> >> | fileSystem | >> fileSystem := FileSystem memory. >> >> (fileSystem / 'file.txt') ensureCreateFile. >> >> STON writer >> on: (fileSystem / 'file.txt') writeStream; >> nextPut: 'hi'. >> >> STON reader >> on: (fileSystem / 'file.txt') readStream; >> next. >> >> Thanks in advance. >> >> MartÃn > >

Nov. 8, 2013

Re: [Pharo-dev] FileSystem memory bug?

by Sven Van Caekenberghe

Hi Martin, I would guess that the stream created by the memory filesystem are binary, not character, as STON expects. Sven On 08 Nov 2013, at 13:55, Martin Dias <tinchodias(a)gmail.com> wrote: > Hi, > > I'm working in latest Pharo (30577) with STON (bleeding edge) and I get MNU:SmallInteger>>isSeparator when I evaluate the code below. Is my code wrong? The idea is to make my test suite work in the memory file system. > > | fileSystem | > fileSystem := FileSystem memory. > > (fileSystem / 'file.txt') ensureCreateFile. > > STON writer > on: (fileSystem / 'file.txt') writeStream; > nextPut: 'hi'. > > STON reader > on: (fileSystem / 'file.txt') readStream; > next. > > Thanks in advance. > > MartÃn

Nov. 8, 2013

Re: [Pharo-dev] FileSystem memory bug?

by Martin Dias

Note: It works fine if I use `FileSystem workingDirectory`. Also it works with: | aWriteStream | aWriteStream := '' writeStream. STON writer on: aWriteStream; nextPut: 'hi'. STON reader on: aWriteStream contents readStream; next. Thanks again, MartÃn On Fri, Nov 8, 2013 at 1:55 PM, Martin Dias <tinchodias(a)gmail.com> wrote: > Hi, > > I'm working in latest Pharo (30577) with STON (bleeding edge) and I get > MNU:SmallInteger>>isSeparator when I evaluate the code below. Is my code > wrong? The idea is to make my test suite work in the memory file system. > > | fileSystem | > fileSystem := FileSystem memory. > > (fileSystem / 'file.txt') ensureCreateFile. > > STON writer > on: (fileSystem / 'file.txt') writeStream; > nextPut: 'hi'. > STON reader > on: (fileSystem / 'file.txt') readStream; > next. > > Thanks in advance. > > MartÃn >

Nov. 8, 2013

FileSystem memory bug?

by Martin Dias

Hi, I'm working in latest Pharo (30577) with STON (bleeding edge) and I get MNU:SmallInteger>>isSeparator when I evaluate the code below. Is my code wrong? The idea is to make my test suite work in the memory file system. | fileSystem | fileSystem := FileSystem memory. (fileSystem / 'file.txt') ensureCreateFile. STON writer on: (fileSystem / 'file.txt') writeStream; nextPut: 'hi'. STON reader on: (fileSystem / 'file.txt') readStream; next. Thanks in advance. MartÃn

Nov. 8, 2013

Re: [Pharo-dev] Opal, Pharo 3.0 and popup raising for none existing methods

by Mariano Martinez Peck

On Fri, Nov 8, 2013 at 4:50 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On 07 Nov 2013, at 16:41, Mariano Martinez Peck <marianopeck(a)gmail.com> > wrote: > > > Hi guys, > > > > In Pharo 2.0 we have the setting #warningAllowed in Parser. This allow > us to disable the popups each time you save a method with a selector that > doesn't exist. > > In Pharo 3.0 with the new Opal this setting doesn't exist anymore. > > Is there a way to get this behavior??? > > Not yet implemented. Yes, needs to be done. I will put it on the TODO. > > OK, thanks Marcus. > Marcus > > > -- Mariano http://marianopeck.wordpress.com

Nov. 8, 2013

Re: [Pharo-dev] extracting a pier book into pillar files

by Damien Cassou

thanks Doru On Fri, Nov 8, 2013 at 11:58 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Ok. I will try to write the script myself and let you know. > > Doru > > > On Fri, Nov 8, 2013 at 11:33 AM, Damien Cassou <damien.cassou(a)gmail.com> > wrote: >> >> On Thu, Nov 7, 2013 at 4:17 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> > Should I understand that you are working on this? Any timeline? >> >> >> I'm working on reimplementing a nice visitor for the document model >> (because the one of Pier-Book was really hackish). But the Pier-Book >> still works fine and you can use that for now. >> >> I don't have any plan to write a script to do the migration of existing >> books. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Nov. 8, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30557 Home: https://github.com/pharo-project/pharo-core

Nov. 8, 2013