December 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Streaming over a UTF-8 encoded file using upToAll:

by Stephane Ducasse

Thanks for the submission we will check. On Sun, Dec 31, 2017 at 4:26 PM, Bernhard Pieber <bernhard(a)pieber.com> wrote: > Hi Henrik, > > Thanks for the fix. I just saw it today. In the meantime I have created a pull request with another fix. To be honest, I have just taken the working implementation from Squeak: > https://github.com/pharo-project/pharo/pull/632 > > Alas, the CI check failed for some reason I don't understand. :-/ > > Happy New Year! > Bernhard > >> Am 30.12.2017 um 13:32 schrieb Henrik-Nergaard <draagren(a)outlook.com>: >> >> Here is a fix. >> >> ------------------------------------ >> PositionableStream>>#upToAll: aCollection >> "Answer a subcollection from the current access position to the occurrence >> (if any, but not inclusive) of aCollection. If aCollection is not in the >> stream, answer the entire rest of the stream." >> >> | output pattern | >> >> aCollection ifEmpty: [ ^ collection species empty ]. >> >> output := (collection species new: 100) writeStream. >> pattern := aCollection readStream. >> >> [ pattern atEnd ] whileFalse: [ | item | >> self atEnd ifTrue: [ >> output next: pattern position putAll: aCollection startingAt: 1. >> ^ output contents >> ]. >> >> item := self next. >> (pattern peekFor: item) ifFalse: [ >> output >> next: pattern position putAll: aCollection startingAt: 1; >> nextPut: item. >> >> pattern reset. >> ]. >> ]. >> >> ^ output contents >> ------------------------------------ >> >> Best regards, >> Henrik > >

Dec. 31, 2017

Re: [Pharo-dev] Best wishes for 2018

by Stephane Ducasse

you too :) On Mon, Jan 1, 2018 at 12:15 AM, Cyril Ferlicot <cyril.ferlicot(a)gmail.com> wrote: > > On ven. 29 dÃ©c. 2017 at 09:40, Torsten Bergmann <astares(a)gmx.de> wrote: >> >> Only a few days left for 2017. Thanks to all who helped shaping Pharos >> future. >> May the lighthouse be with you in 2018 as well: >> >> World backgroundImage: >> (ZnEasy >> getJpeg: >> 'https://spotlight.it-notes.ru/wp-content/uploads/2017/08/02c48424be88ee36d5…') >> layout: #scaled >> >> Have fun! >> >> Bye >> T. >> > Happy new year everyone :) > -- > Cyril Ferlicot > https://ferlicot.fr > > http://www.synectique.eu > 2 rue Jacques PrÃ©vert 01, > 59650 Villeneuve d'ascq France

Dec. 31, 2017

Re: [Pharo-dev] Best wishes for 2018

by Cyril Ferlicot

On ven. 29 dÃ©c. 2017 at 09:40, Torsten Bergmann <astares(a)gmx.de> wrote: > Only a few days left for 2017. Thanks to all who helped shaping Pharos > future. > May the lighthouse be with you in 2018 as well: > > World backgroundImage: > (ZnEasy > getJpeg: ' > https://spotlight.it-notes.ru/wp-content/uploads/2017/08/02c48424be88ee36d5… > ') > layout: #scaled > > Have fun! > > Bye > T. > > Happy new year everyone :) -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

Dec. 31, 2017

Re: [Pharo-dev] Simple game framework

by Stephane Ducasse

Hi hilaire Some students at Prague are working on different 2D games with Bloc and this is working. Some did a sokoban, other a miner (check on pharo weekly). They use Bloc and I will ask them to make public their code. No need for SDL. SDL is ***low level***. Now modeling the board and proposing some abstractions that can be easily extended is difficult. and this is what lauraMaximilliano did in MetaBorg. It was on my todo to do a pass. I implemented a grid to help the design of board game. Now having direction/location can be good. What is interesting in the design of metaborg is that we do not test if an object can move to a place. We go to the place and the place pull the item. A wall will not pull for example while a empty slot will pull the item to move. I found it intriguing and I would like to know if this is working for more complex situation. Maximiliano implemented sokoban, tetris, snake, pacman with the same framwork. Now it is a bit abstract but an interesting experience. Stef On Sun, Dec 31, 2017 at 2:41 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > I am *exploring* if Pharo will be suitable to have a simple programming > environment to let kids write simple 2D games, SDL was designed for that. > > Some of my students asked me about programming games, Smalltalk way of > writing code will be neat, but the environment need to be accessible and not > over engineered. > > > Le 30/12/2017 Ã 22:32, Stephane Ducasse a Ã©crit : >> >> What kind of game are you targeting? Did you look at Bloc? Because to >> me this is the way to go except if you want just a canvas >> and reimplement your event loop. in that case SDL + Athens should work. > > > -- > Dr. Geo > http://drgeo.eu > > >

Dec. 31, 2017

Re: [Pharo-dev] Best VM for the Mac>

by Stephane Ducasse

Well, do NOT rely on them on Sierra. I can crash such VM while typing code. They have two issues: - typing - freeType I removed the freeType plugin to be able to work on my machine but this is clearly not a solution. Now crashing every 20 min when typing code is not something that we can claim is production ready. And this is both for 6.1 and 7.0 Stef On Sun, Dec 31, 2017 at 4:02 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > >> On 31 Dec 2017, at 16:00, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> >> >> >>> On 31 Dec 2017, at 15:59, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> >>> yes. >>> and I will promote them to stable this month. >> bah, not this month but january ;) > > ah, maybe is confusing, hehâ¦ yes, usually latest VMs are *not* for production. But this ones have been tested last three months and they work fine so yes, *this ones* can be used for production. > > Esteban > >> >>> >>>> On 31 Dec 2017, at 15:56, Bernhard Pieber <bernhard(a)pieber.com> wrote: >>>> >>>> These are not for production, right? >>>> >>>> Bernhard >>>> >>>>> Am 31.12.2017 um 11:58 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: >>>>> >>>>> wget -O- get.pharo.org/vmLatest70 | bash >>>>> wget -O- get.pharo.org/64/vmLatest70 | bash >>>>> >>>>> Esteban >>>>> >>>>>> On 31 Dec 2017, at 11:48, Sean P. DeNigris <sean(a)clipperadams.com> wrote: >>>>>> >>>>>> Sean P. DeNigris wrote >>>>>>> What is the best VM right now for the Mac? Where/how would one get it? >>>>>> >>>>>> Bump ;) >>>>>> >>>>>> >>>>>> >>>>>> ----- >>>>>> Cheers, >>>>>> Sean >>>>>> -- >>>>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html >>>> >>>> >>> >> > >

Dec. 31, 2017

Re: [Pharo-dev] Replacement for deprected MultiByteFileStream?

by Stephane Ducasse

On Sun, Dec 31, 2017 at 12:55 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Denis Kudriashov <dionisiydk(a)gmail.com> > wrote: >> Hi Bernhard. >> >> The deprecation is still in progress. > > Considering the amount of non-image code using this, I would be interested > to hear how this is going to be supported and documented. Step by step. :) We cannot continue to have so bad streams without taking action. So we start to make sure that Pharo itself does not use the old streams. Then it means that we will be able to have the old stream library as a separate package and people will slowly migrate. Now it would be nice to have a rewrite rule to help but it requires time. Stef

Dec. 31, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Stephane Ducasse

Tx Stephan I have too many dreams :) so I will have to prioritize but let's the first three :). Stef On Sun, Dec 31, 2017 at 12:58 PM, Stephan Eggermont <stephan(a)stack.nl> wrote: > Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: >> Hi everybody, >> >> This looks like a good moment of the year to ask all of you what would >> you want to see in Pharo next year. > > I wish you all the time and good health to realize some of your Pharo > dreams > > Stephan > >

Dec. 31, 2017

Re: [Pharo-dev] [Pharo-users] Best wishes for 2018

by Stephane Ducasse

:) I like this kind of metrics :) I want more of them :) I wish everybody lot of success and business. Stef On Sun, Dec 31, 2017 at 2:18 PM, Norbert Hartl <norbert(a)hartl.name> wrote: > I want to second that. It has been another amazing year for pharo. And I think things have changed significantly. So 2018 should be really great! > I matched my personal not-to-serious goal > > # ps aux | grep pharo | wc -l > 59 > > So I have 59 pharo images in production. Next step will be to exceed 100 in 2018! And yes, Iâm definitely interested in a bootstrapped image ;) > > Thank you all for your amazing work. We are a great community! > > Norbert > > >> Am 29.12.2017 um 09:39 schrieb Torsten Bergmann <astares(a)gmx.de>: >> >> Only a few days left for 2017. Thanks to all who helped shaping Pharos future. >> May the lighthouse be with you in 2018 as well: >> >> World backgroundImage: >> (ZnEasy >> getJpeg: 'https://spotlight.it-notes.ru/wp-content/uploads/2017/08/02c48424be88ee36d5…') >> layout: #scaled >> >> Have fun! >> >> Bye >> T. >

Dec. 31, 2017

FreeCell resurrection

by Pavel Krivanek

Hi, I fixed the old FreeCell code from Squeak to be able to run on Pharo 6 and 7. Repository: https://github.com/pavel-krivanek/FreeCell How to load: Metacello new baseline: 'FreeCell'; repository: 'github://pavel-krivanek/FreeCell/src'; load. How to run: FreeCell open. Cheers, -- Pavel

Dec. 31, 2017

Re: [Pharo-dev] Replacement for deprected MultiByteFileStream?

by Bernhard Pieber

IIUC that means that a stream implementation compatible with the standard streams cannot be implemented on top of the new streams, right? What is the plan about #upToAll:, #match: and similar messages which are very useful for parsing? Where should they go? Bernhard > Am 31.12.2017 um 17:07 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: > >> On 31 Dec 2017, at 16:21, Bernhard Pieber <bernhard(a)pieber.com> wrote: >> >> Hi Sven, >> >> Thanks for the answer. This is exactly what I was looking for. And it is great that there is also documentation. >> >> However, ZnCharacterReadStream does not implement #upToAll:. The implementation from PositionableStream cannot easily be borrowed because there seems to be no way to reset the position. Is there a plan to support the most commonly used messages from the normal streams? > > The Stream API is much too wide, it has to be reduced and split in a number of elementary streams that can be composed to add desired behaviour (like character encoding/decoding, buffering, line end translation, ...). Positioning in a stream (moving backwards without restrictions) is not generally possible (think of a network stream), that is why it is not implemented. > >> Bernhard >> >>> Am 30.12.2017 um 18:03 schrieb Sven Van Caekenberghe <sven(a)stfx.eu>: >>> >>> https://ci.inria.fr/pharo-contribution/job/EnterprisePharoBook/lastSuccessf… >>> >>> 1.4. Converting Streams >>> >>>> On 30 Dec 2017, at 13:27, Bernhard Pieber <bernhard(a)pieber.com> wrote: >>>> >>>> I just saw that the FileStream hierarchy including MultiByteFileStream is deprecated. However, I can't find what file stream class should be used to read a UTF-8 encoded file instead. FileReference>>#readStreamDo: also uses MultiByteFileStream. >>>> >>>> Can someone please point me to the right code? >>>> >>>> Bernhard

Dec. 31, 2017