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

About cr and lf
by Stephane Ducasse Aug. 6, 2017

Aug. 6, 2017

Hi guys While writing pillar code, I ended up using "stream cr" and it worries me to still expand usage of a pattern I would like to remove. Let us imagine that we would like to prepare the migration from cr. I was thinking that we could replace cr invocation by newLine so that after newLine could be redefined as Stream >> newLine self nextPutAll: OSPlatform current lineEnding what do you think about this approach? Stef

17 39

Re: [Pharo-dev] PharoLauncher - uninformative Pharo7 template names
by Torsten Bergmann Aug. 6, 2017

Aug. 6, 2017

1 0

[Calypso] Inherited methods checkbox look backwards to me
by Mariano Martinez Peck Aug. 4, 2017

Aug. 4, 2017

Hi Denis, I love the inherited methods feature. Really. Seconds ago, I just clicked to show inherited methods, I checkboxed the superclass, then I saw both methods (the one I override and the one of the superclass), clicked on both, and magic...I was comparing them with a nice diff. AESOME!!!!! The only seem that didn't look obvious to me is the "sort" of the classes of the inherited protocols. It goes contrary to everwhere else. ProtoObject is on the bottom and immediate superclass on the top. Can't we make it as always? ProtoObject on the bottom and immediate on top? I know, this is a very little detail...but I also wanted to express my happiness with this feature hahaha. Cheers, -- Mariano http://marianopeck.wordpress.com

4 5

Re: [Pharo-dev] [vwnc] Live Programming in Smalltalk development environments survey + raffle
by Juraj Kubelka Aug. 3, 2017

Aug. 3, 2017

Hi Helge, we are targeting it to ICSE 2018. With crossed fingers it will happen :-) Cheers, Juraj > El 03-08-2017, a las 10:30, Nowak, Helge <HNowak(a)cincom.com> escribiÃ³: > > Dear Juraj, Romain and Alexandre, <> > > this is indeed an interesting piece of research! Where will you publish the results with detailed analysis? > > Cheers > Helge > > Helge Nowak > Cincom Smalltalk Technical Account Manager EMEA > <image001.png> <http://www.cincomsmalltalk.com/> > Cincom Systems GmbH & Co. oHG > Am Kronberger Hang 4 > 65824 Schwalbach/Ts. > GERMANY > office > mobile > fax > > website > email > +49 89 89 66 44 94 > +49 172 74 00 402 > +49 89 89 66 44 95 > > http://www.cincomsmalltalk.com <http://www.cincomsmalltalk.com/> > hnowak(a)cincom.com <mailto:hnowak@cincom.com> > A standpoint is an intellectual horizon of radius zero. -- Albert Einstein > > GeschÃ¤ftsfÃ¼hrer/Managing Directors: Thomas M. Nies, Donald E. Vick > oHG mit Sitz/based in Schwalbach/Ts. (Amtsgericht KÃ¶nigstein/Ts. HRA 2653) > Pers. haftender Gesellschafter/Partner liable to unlimited extent: > Cincom Systems Verwaltungsgesellschaft mbH (Amtsgericht KÃ¶nigstein/Ts. HRB 5069) > > --- CONFIDENTIALITY STATEMENT --- > This e-mail transmission contains information that is intended to be privileged and confidential. It is intended only for the addressee named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited, please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. > > > Von: Juraj Kubelka [mailto:juraj.kubelka@icloud.com] > Gesendet: Donnerstag, 3. August 2017 09:31 > An: Any question about pharo is welcome <pharo-users(a)lists.pharo.org>; Pharo Development List <pharo-dev(a)lists.pharo.org>; Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org>; squeak-dev(a)lists.squeakfoundation.org; vwnc(a)lists.cs.illinois.edu > Betreff: [vwnc] Live Programming in Smalltalk development environments survey + raffle > > â âWe are apologize for multiple copies.â â > > Dear Smalltalker, > > Live programming frees developers from the "edit-compile-run" loop and allows people to interact with running programs very easily. Live programming is getting popular, but many of its features have > been present in Smalltalk for a very long time. > > We want to understand how Smalltalk software developers use live programming features in practice. We would be grateful if you could participate in our 10-minute survey on this subject: > http://bit.ly/2ufcg2D <http://bit.ly/2ufcg2D> > > As a thank you for your participation, you will be able to participate in a raffle to win a Smalltalk book of your choice. If you wish to participate, you will need to share your email with us, so > that we can contact you. > We will appreciate if you share the survey > - Twitter post: https://twitter.com/JurajKubelka/status/893006267085709312 <https://twitter.com/JurajKubelka/status/893006267085709312> > - Facebook post: https://www.facebook.com/juraj.kubelka/posts/10212505941300008 <https://www.facebook.com/juraj.kubelka/posts/10212505941300008> > > By participating in the survey you will: > - help me to successfully finish my PhD, > - push Smalltalk awareness in Live Programming research community, > - bring new integrated electronic communication ideas, and > - bring new ideas to improve our Smalltalk Live Programming experience :-) > > We will close the survey on Wednesday, August 9, 2017 AoE. > > Thank you and we really hope you enjoy participating in our survey! > > Juraj Kubelka, PhD Student at the University of Chile > > Romain Robbes, Professor at Free University of Bozen-Bolzano > > Alexandre Bergel, Professor at the University of Chile

1 0

Live Programming in Smalltalk development environments survey + raffle
by Juraj Kubelka Aug. 3, 2017

Aug. 3, 2017

â âWe are apologize for multiple copies.â â Dear Smalltalker, Live programming frees developers from the "edit-compile-run" loop and allows people to interact with running programs very easily. Live programming is getting popular, but many of its features have been present in Smalltalk for a very long time. We want to understand how Smalltalk software developers use live programming features in practice. We would be grateful if you could participate in our 10-minute survey on this subject: http://bit.ly/2ufcg2D <http://bit.ly/2ufcg2D> As a thank you for your participation, you will be able to participate in a raffle to win a Smalltalk book of your choice. If you wish to participate, you will need to share your email with us, so that we can contact you. We will appreciate if you share the survey - Twitter post: https://twitter.com/JurajKubelka/status/893006267085709312 <https://twitter.com/JurajKubelka/status/893006267085709312> - Facebook post: https://www.facebook.com/juraj.kubelka/posts/10212505941300008 <https://www.facebook.com/juraj.kubelka/posts/10212505941300008> By participating in the survey you will: - help me to successfully finish my PhD, - push Smalltalk awareness in Live Programming research community, - bring new integrated electronic communication ideas, and - bring new ideas to improve our Smalltalk Live Programming experience :-) We will close the survey on Wednesday, August 9, 2017 AoE. Thank you and we really hope you enjoy participating in our survey! Juraj Kubelka, PhD Student at the University of Chile Romain Robbes, Professor at Free University of Bozen-Bolzano Alexandre Bergel, Professor at the University of Chile

1 0

[IMPORTANT] Following changes in the bootstrapping process
by Pavel Krivanek Aug. 3, 2017

Aug. 3, 2017

Hello, we are checking a huge pull request #177 ( https://github.com/pharo-project/pharo/pull/177) that will change some basics of the bootstrap process: Now we will bootstrap a smaller image that will not include compiler/parser. Compiler and related packages are exported and loaded using a binary exporter named Hermes. The compiler is then used to load FileSystem and Monticello. The rest of the bootstrap process will be the same as before. As the result we will have faster bootstrap and better system modularization and possibilities. It required some modularization efforts: - simplified initialization scripts - Use Zinc converters and encoders instead of FilePathEncoder and old TextConverter - Use Stdio instead of FileStream - Using File instead of FileSystem - Deprecated FileStream & childs (Moved to Deprecated70) - Extracted Path classes to their on package: FileSystem-Path - Moved OpalEncoders to their own package. They are required by the runtime (not only for compilation) - Introduced AsciiCharset in the kernel to answer to #isLetter #isUppercase and so on without requiring full Unicode tables from the beginning - Cleaning up a bit the full exception logging infrastructure (streams, transcript, files, stack printing...) - Split Ring methods required for system navigation to the Ring-Navigation package - Remove usages of #translated in the kernel - Refactored the bootstrapping classes to remove duplications - Cleaning up dependencies in CompiledMethod>>printOn: - fix path printing We need to merge these changes at once and of course it can cause some conflicts with the existing pull requests or external code. Anyway, we need to merge it as soon as possible. So please, try to look at the PR and test the resultant image [1] to avoid some major problems. [1] https://ci.inria.fr/pharo/view/7.0/job/70-PR-Check-Load/lastSuccessfulBuild… Cheers, -- Pavel

11 27

Question about Bloc
by Alexandre Bergel Aug. 3, 2017

Aug. 3, 2017

Hi! We were wondering whether someone did some workload with Bloc. How many elements can Bloc render, at the same time? Is there a support for Quad-Tree ? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

Epicea: Revert the removal of a class
by Cyril Ferlicot D. Aug. 2, 2017

Aug. 2, 2017

Hi, Today I tried to remove a class, go in Epicea and revert the removal of the class. At the end the class was here but with no methods. Is that the normal behaviour? I think it is a bug but since I don't really use Epicea a lot for know I am not sure. Have a nice day. -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques PrÃ©vert 01, 59650 Villeneuve d'ascq France

3 2

Calypso browser and categories?
by Mariano Martinez Peck Aug. 2, 2017

Aug. 2, 2017

Hi Denis, I wanted to give a serious test to Calypso, that is, start using it all day long. However, there is a critical thing I am missing, which is the grouping of categories (inside packages). I do not want to start discussing again packages vs categories and what are good and bad practices. I do have a few packages and each package may have several categories inside. So... seeing all classes together inside a package is not nice for me. Is there a way in calypso to auto-escope to category level? I mean... say my package is XXX and I have categories XXX-A and XXX-B. I know I can go to left side column and with the tree, I can go to XXX-A and I get what I want. But, for example, when I browse a class of XXX-A, the "focus" of the left side column is XXX and not XXX-A. So I am wondering if we can make it auto-scope to the category everywhere in Calypso. Thanks in advance, -- Mariano http://marianopeck.wordpress.com

2 8

Lots of "UTF8InvalidText: Invalid utf8 input detected" from OMBU
by Mariano Martinez Peck Aug. 2, 2017

Aug. 2, 2017

Guys, I am getting "UTF8InvalidText: Invalid utf8 input detected" quite frequently on Pharo 6.0 which come from ombu background job. Has anything seen this too? Quite annoying... This is not the first time I hit it. This time I analyzed a bit why it was failing and it's because I removed a method manually...I mean, I did MyClass removeSelector: #myMethod And the omEntry is a EpMethodRemoval which represents the exact method I deleted... Also I can see the MultiByteFileStream internal 'collection' is full of none ascii things. I can share a fuelout as well as the image with the files if you want. I can also share the ombu file in question. Contact me in private. ---- [ :error | (OmFileStoreReadingError readingError: error on: self fileReference position: readStream position) signal ] in [ :readStream | [ ^ aBlockClosure value: readStream ascii ] on: Error do: [ :error | (OmFileStoreReadingError readingError: error on: self fileReference position: readStream position) signal ] ] in OmBlockFileStore(OmFileStore)>>readEntriesWith: in Block: [ :error | ... BlockClosure>>cull: Context>>evaluateSignal: Context>>handleSignal: UTF8InvalidText(Exception)>>signal UTF8InvalidText(Exception)>>signal: UTF8TextConverter>>errorMalformedInput UTF8TextConverter>>nextFromStream: MultiByteFileStream>>next MultiByteFileStream(PositionableStream)>>match: MultiByteFileStream(PositionableStream)>>upToAll: OmSTONEntryReader>>nextEntryPositionIfFound:ifNone: OmBlockFileStore>>refreshNewBlocksFrom: [ :readStream | self refreshNewBlocksFrom: readStream ] in OmBlockFileStore>>refreshEntryPositionsByLocalNameStartingAt:since: in Block: [ :readStream | self refreshNewBlocksFrom: readStr...etc... [ ^ aBlockClosure value: readStream ascii ] in [ :readStream | [ ^ aBlockClosure value: readStream ascii ] on: Error do: [ :error | (OmFileStoreReadingError readingError: error on: self fileReference position: readStream position) signal ] ] in OmBlockFileStore(OmFileStore)>>readEntriesWith: in Block: [ ^ aBlockClosure value: readStream ascii ] BlockClosure>>on:do: [ :readStream | [ ^ aBlockClosure value: readStream ascii ] on: Error do: [ :error | (OmFileStoreReadingError readingError: error on: self fileReference position: readStream position) signal ] ] in OmBlockFileStore(OmFileStore)>>readEntriesWith: in Block: [ :readStream | ... [ aBlock value: stream ] in FileReference(AbstractFileReference)>>readStreamDo: in Block: [ aBlock value: stream ] BlockClosure>>ensure: FileReference(AbstractFileReference)>>readStreamDo: OmBlockFileStore(OmFileStore)>>readEntriesWith: OmBlockFileStore>>refreshEntryPositionsByLocalNameStartingAt:since: [ | initialPosition initialLocalName | self entryBuffer isEmpty ifTrue: [ ^ self ]. fileReference writeStreamDo: [ :fileStream | fileStream setToEnd. initialPosition := fileStream position. initialLocalName := self entryBuffer first value. ZnBufferedWriteStream on: fileStream do: [ :aWriteStream | | anEntryWriter | anEntryWriter := self newEntryWriter. [ self entryBuffer isEmpty ] whileFalse: [ | next entry | next := self entryBuffer removeFirst. entry := next key. "Write entry to file" anEntryWriter on: aWriteStream nextEntryPut: entry ] ]. "In Linux it was necessary to explicitely flush the file stream" fileStream flush. lastStreamPosition := fileStream size ]. self refreshEntryPositionsByLocalNameStartingAt: initialPosition since: initialLocalName ] in OmBlockFileStore(OmFileStore)>>flushEntryBuffer in Block: [ | initialPosition initialLocalName |... [ caught := true. self wait. blockValue := mutuallyExcludedBlock value ] in Semaphore>>critical: in Block: [ caught := true.... BlockClosure>>ensure: Semaphore>>critical: OmBlockFileStore(OmFileStore)>>critical: OmBlockFileStore(OmFileStore)>>flushEntryBuffer OmDeferrer>>sendMessage [ self sendMessage ] in OmDeferrer>>flush in Block: [ self sendMessage ] -- Mariano http://marianopeck.wordpress.com

4 5