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

Re: [Pharo-dev] Using TreeModel>>selectAll

by Martin Dias

ouch! thanks Ben. Another related question: is there any way of selecting an arbitrary item? I tried (among others) with: TreeModel new roots: #(1 2 3); multiSelection: true; openWithSpec; selection: 3 without success. Cheers, MartÃn On Thu, Dec 5, 2013 at 4:17 PM, Benjamin <Benjamin.VanRyseghem.Pharo(a)gmail.com> wrote: > your tree here is single selection so it will not work > > TreeModel new > roots: #(1 2 3); > multiSelection: true; > openWithSpec; > selectAll > > Ben > > On 05 Dec 2013, at 15:38, Martin Dias <tinchodias(a)gmail.com> wrote: > > Hi, > > I'm not sure how this method should be used. I tried in different > ways, for example: > > TreeModel new > roots: #(1 2 3); > selectAll; > openWithSpec > > But always the items are unselected. Is it a bug? or I didn't find the > way to use it? > > Thanks, > MartÃn > >

Dec. 7, 2013

Smalltalk in a C World

by askoh

http://www.cl.cam.ac.uk/~dc552/papers/SmalltalkInACWorld.pdf The paper talks about Smalltalk and Objective C coexisting equally in a software development environment. And by virtual of ObjC compatibility with C/C++, the whole C world is open to Smalltalk. Isn't this very exciting? Anyone else noticing this? Can Pragmatic Smalltalk be used to develop a CAD system using the OpenCascade and Visualization Toolkit (VTK) open source libraries? Can this work help us enter the Apple ecosystem? All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/Smalltalk-in-a-C-World-tp4728217.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Dec. 7, 2013

Re: [Pharo-dev] 12259: FileSystem memory reads writesusing a binary stream by default

by Nicolas Cellier

Hem, switching #ascii <-> #binary does only make sense in... ASCII With every other encoding, it's not something that makes sense at all, or maybe #latin1 <-> #binary, #utf8 <-> #binary, #utf16 <-> #binary 2013/12/5 Max Leske <maxleske(a)gmail.com> > There are several different approaches in different places: > > - FileStream reads strings by default. #binary and #ascii switch between > formats. File streams use an internal buffer which is either a String > (default) or a ByteArray. Itâs even possible to switch between binary and > ascii midstream without losing information (if done right) because it only > affects the buffer. > - ReadStream and WriteStream cannot change their format. Their behavior is > determined by the underlying collection. Forcing conversions (e.g. by > #asString) can lead to loss of information > - RWBinaryOrTextStream (and other subclasses of ReadWriteStream) also > support the #binary #ascii method of switching format. Default is #ascii > - SocketStream uses the same #binary / #ascii mechanism. Default is #ascii > - ZnLimitedReadStream uses the same #binary / #ascii mechanism. Default is > #binary (implicit); depends on the underlying stream > > I think the pattern to follow is clear: ReadStream and WriteStream should > allow switching format with #ascii and #binary, default should be #ascii. > However, I suspect thereâs a reason that these classes donât support > switching, namely that switching makes the implementation more complicated > and also slower because more checks need to be made. > > The easiest solution I see would be to implement something like this: > > ReadStream>>next > ^ self isBinary > ifTrue: [ self basicNext asCharacter ] > ifFalse: [ self basicNext ] > > However, #next et al. are implemented in a plugin and the primitive method > looks like this: > > ReadStream>>next > <primitive: 65> > position >= readLimit > ifTrue: [^nil] > ifFalse: [^collection at: (position := position + 1)] > > This means the collection instance variable has to hold either a binary or > a string collection. > > Iâve found a solution which would work and Iâve whipped up a working way > (thereâs space for improvementâ¦): > > ReadStream>>binary > collection isString ifFalse: [ ^ self ]. > collection := (ByteArray new: collection size) copyReplaceFrom: 1 to: > collection size with: collection > > ReadStrem>>ascii > collection isString ifTrue: [ ^ self ]. > collection := (String new: collection size) copyReplaceFrom: 1 to: > collection size with: collection > > @Damien > opposed to what I wrote earlier, #asString does *not* destroy > non-printable characters. Instead, every byte (from 0 to 255) is encoded as > a character and thus the string can be converted back to a ByteArray > *without* loss of information. Sorry about that. > > With this change in place the 12259 would become obsolete. > > Please let me know what you think. This is a pretty big change that might > have a lot of consequences in the image. > > Cheers, > Max > > On 04.12.2013, at 13:14, Max Leske <maxleske(a)gmail.com> wrote: > > Let me see what I can come up with. > > > On 03.12.2013, at 19:36, Damien Cassou <damien.cassou(a)gmail.com> wrote: > > Thanks Max for the report. Do you have an idea on how we could solve the > problem ? The previous behaviour was not acceptable either because the > streams that came out of a memory filesystem were the only ones with binary > content > On Dec 3, 2013 5:35 PM, "Max Leske" <maxleske(a)gmail.com> wrote: > >> Damien, Marcus >> >> this change breaks a lot of things in FileSystem-Git. I donât disagree >> with the idea that reading characters should be default (one could argue >> about itâ¦) but your change makes it IMPOSSIBLE to read bytes because >> unprintable characters are discarded! So if my ByteArray is a NULL >> terminated string, for instance, I can not check for the NULL termination >> anymore. >> >> Cheers, >> Max >> > > >

Dec. 6, 2013

Re: [Pharo-dev] Pharo magic

by Nicolai Hess

This seems to be a good place to introduce myself. My Name is Nicolai Hess, I follow the squeak (and pharo) community for some years (~10). (Not as an *active* member in that time, but a little bit more the last days:-) I am a software developer, most time working with c++ and java. Every time I start to dive into smalltalk world (again), even if all i have done are bugreports or small bugfixes, it impressed me how much more fun it makes. Looking at smalltalks history I was always deeply impressed about all its development and *inventions*. (And a bit sad, it is not as recognized as it could be, and seeing how others again reinventing these things.) It is great to see how pharo and the community moves on. Thank you all. Nicolai 2013/12/6 Torsten Bergmann <astares(a)gmx.de> > Maybe others noticed the same: > > - the numbers of closed issues is amazing(see the news on the homepage) > - Pharo3.0 is already really usable and a pleasure to work with > - more and more nice projects appear on STHub and elsewhere > - more and more Pharo projects use continuous integration > - most projects and packages are loadable from the config browser and > other places without > conflicting with each other > - there is so much activity regarding Pharo these days on mailinglists, > bug-tracker, > twitter, conferences, blogs, stackoverflow, github ... it becomes hard > to follow > but this is a good sign > - I see more and more fixes and improvements already as an update coming > in before > I really realize that an own bug is needed because it improves the > situation > - more and more new names appear on the dev and user mailinglist which is > a good > sign that there is growing interest > - Pharo is on the right track and I like to be on the train > > Step by step it goes... > > Bye > T. > > > > >

Dec. 6, 2013

Re: [Pharo-dev] Pharo magic

by Sebastian Sastre

Thanks for sharing that Kilon On Dec 6, 2013, at 6:49 PM, kilon alios <kilon.alios(a)gmail.com> wrote: > Well I tried pharo just for fun , I knew it would not last. Pharo is unpopular, not enough libraries, small community , not nearly enough documentation. Pharo was nothing more than a little break from python. After all we all know smalltalk is dead , right ? The plan was simple, have fun with Pharo , steal some ideas, go back to python where you can get things done. Little did I know. Several months later here I am. I still have not found the reason to give up on Pharo, my questions have been answered , found many great libraries to work with and the documentation is getting better and better. > > Overall my experience is way better than I predicted. Pharo is turning into the environment I always wanted to have. Its so unique that I just cant compare it with anything else, and the uniqueness is not just in details, its almost everywhere. I am so addicted to live coding that I cant see myself going back to the old way. This is the future of coding. > > I only wish the best for Pharo , not for me but for you guys, you work hard for it and you deserve it. Thank you :) > > > > On Fri, Dec 6, 2013 at 10:33 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks for your warm words (because sometimes I would like so much to improve pharo even more that I'm down). > We have a great team (I do not want to list names because I do not want to forget someone). > > Stef > > > Maybe others noticed the same: > > > > - the numbers of closed issues is amazing(see the news on the homepage) > > - Pharo3.0 is already really usable and a pleasure to work with > > - more and more nice projects appear on STHub and elsewhere > > - more and more Pharo projects use continuous integration > > - most projects and packages are loadable from the config browser and other places without > > conflicting with each other > > - there is so much activity regarding Pharo these days on mailinglists, bug-tracker, > > twitter, conferences, blogs, stackoverflow, github ... it becomes hard to follow > > but this is a good sign > > - I see more and more fixes and improvements already as an update coming in before > > I really realize that an own bug is needed because it improves the situation > > - more and more new names appear on the dev and user mailinglist which is a good > > sign that there is growing interest > > - Pharo is on the right track and I like to be on the train > > > > Step by step it goes... > > > > Bye > > T. > > > > > > > > > > >

Dec. 6, 2013

Re: [Pharo-dev] Pharo magic

by kilon alios

Well I think the secret of success of Pharo with newcomers like me is 3 things a) Documentation b) Documentation c) yes you guessed it Documentation Coming from python I can tell you that the success of python and its a very successful language popularity wise , is the fact that it has simply designed libs and the community highly values documentation. Of course they have a huge community to help out. In python new features that go inside the library are not just libraries that people offer. They make first a pep which is a document that documents the library even before the library is implemented, or the library modified, depending on whether its a modification or a new feature. So documentation exists even before code is written. But of course that applies only for the core development of python standard library and is not binding for external libraries. If the library is external and is to be submitted to the python standard library again a Pep need to be made by the author of the library or another developer carefully documenting the library and its implication usefulness for cpython standard distribution. So nothing goes in if its not documented first. At least as far as I know. all Peps are collected here -> http://www.python.org/dev/peps/. Of course after implementation has finished peps are transformed to official documentation submitted here -> http://www.python.org/doc/ So If I would have something to recommend Pharo to copy from Python would be this. I cant think of a more important feature to have. On Fri, Dec 6, 2013 at 11:58 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Thanks indeed. > > Kilon, your experience is valuable for those of us that basically live in > Pharo. So, your input matters more than you think because you can help us > make Pharo more appealing for newcomers. So, if you could change one thing > that would have made the transition to Pharo even smoother, what would it > be? > > Doru > > > On Fri, Dec 6, 2013 at 10:36 PM, Luc Fabresse <luc.fabresse(a)gmail.com>wrote: > >> Hi, >> >> thanks kilon for sharing your Python experience ;-) >> I really enjoy listening to people that discover Pharo "recently". >> >> Thank you all! >> >> >> >> #Luc >> >> >> 2013/12/6 kilon alios <kilon.alios(a)gmail.com> >> >>> Well I tried pharo just for fun , I knew it would not last. Pharo is >>> unpopular, not enough libraries, small community , not nearly enough >>> documentation. Pharo was nothing more than a little break from python. >>> After all we all know smalltalk is dead , right ? The plan was simple, >>> have fun with Pharo , steal some ideas, go back to python where you can get >>> things done. Little did I know. Several months later here I am. I still >>> have not found the reason to give up on Pharo, my questions have been >>> answered , found many great libraries to work with and the documentation is >>> getting better and better. >>> >>> Overall my experience is way better than I predicted. Pharo is turning >>> into the environment I always wanted to have. Its so unique that I just >>> cant compare it with anything else, and the uniqueness is not just in >>> details, its almost everywhere. I am so addicted to live coding that I cant >>> see myself going back to the old way. This is the future of coding. >>> >>> I only wish the best for Pharo , not for me but for you guys, you work >>> hard for it and you deserve it. Thank you :) >>> >>> >>> >>> On Fri, Dec 6, 2013 at 10:33 PM, StÃ©phane Ducasse < >>> stephane.ducasse(a)inria.fr> wrote: >>> >>>> Thanks for your warm words (because sometimes I would like so much to >>>> improve pharo even more that I'm down). >>>> We have a great team (I do not want to list names because I do not want >>>> to forget someone). >>>> >>>> Stef >>>> >>>> > Maybe others noticed the same: >>>> > >>>> > - the numbers of closed issues is amazing(see the news on the >>>> homepage) >>>> > - Pharo3.0 is already really usable and a pleasure to work with >>>> > - more and more nice projects appear on STHub and elsewhere >>>> > - more and more Pharo projects use continuous integration >>>> > - most projects and packages are loadable from the config browser and >>>> other places without >>>> > conflicting with each other >>>> > - there is so much activity regarding Pharo these days on >>>> mailinglists, bug-tracker, >>>> > twitter, conferences, blogs, stackoverflow, github ... it becomes >>>> hard to follow >>>> > but this is a good sign >>>> > - I see more and more fixes and improvements already as an update >>>> coming in before >>>> > I really realize that an own bug is needed because it improves the >>>> situation >>>> > - more and more new names appear on the dev and user mailinglist >>>> which is a good >>>> > sign that there is growing interest >>>> > - Pharo is on the right track and I like to be on the train >>>> > >>>> > Step by step it goes... >>>> > >>>> > Bye >>>> > T. >>>> > >>>> > >>>> > >>>> > >>>> >>>> >>>> >>> >> > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Dec. 6, 2013

Re: [Pharo-dev] [Spy] How to inject code *inside* a method

by Tudor Girba

Me, too! :) Doru On Fri, Dec 6, 2013 at 9:38 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > > âget a copy of the IR tree" > > irMethod := (TestMy>>#test) ir copy. > > > > âget all instance variable access IR instructionsâ > > allIvarAccesses := irMethod allInstructionsMatching: [ :ir |ir > isInstVarAccess]. > > > > âinsert code for â1 haltâ before all of them" > > allIvarAccesses do: [ :each | each addInstructionsBefore: { > IRInstruction pushLiteral: 1. IRInstruction send: #halt. IRInstruction > popTop }]. > > > > âgenerate a new compiledMethod" > > cm := irMethod generate: (TestMy>>#test) trailer. > > > > âinstall in the class" > > TestMy addSelector: #test withMethod: cm. > > > > 17 <76> pushConstant: 1 > > 18 <D0> send: halt > > 19 <87> pop > > 20 <00> pushRcvr: 0 > > 21 <76> pushConstant: 1 > > 22 <B0> send: + > > 23 <76> pushConstant: 1 > > 24 <D0> send: halt > > 25 <87> pop > > 26 <00> pushRcvr: 0 > > 27 <B0> send: + > > 28 <7C> returnTop > > > > > > â> TestMy new test > > > > What is now yet wiring is quick return methods â> need to clear the > primitive in that case, should not be hard to do. > > I love this in 5 lines!!!! > > > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 6, 2013

Re: [Pharo-dev] Pharo magic

by Tudor Girba

Thanks indeed. Kilon, your experience is valuable for those of us that basically live in Pharo. So, your input matters more than you think because you can help us make Pharo more appealing for newcomers. So, if you could change one thing that would have made the transition to Pharo even smoother, what would it be? Doru On Fri, Dec 6, 2013 at 10:36 PM, Luc Fabresse <luc.fabresse(a)gmail.com>wrote: > Hi, > > thanks kilon for sharing your Python experience ;-) > I really enjoy listening to people that discover Pharo "recently". > > Thank you all! > > > > #Luc > > > 2013/12/6 kilon alios <kilon.alios(a)gmail.com> > >> Well I tried pharo just for fun , I knew it would not last. Pharo is >> unpopular, not enough libraries, small community , not nearly enough >> documentation. Pharo was nothing more than a little break from python. >> After all we all know smalltalk is dead , right ? The plan was simple, >> have fun with Pharo , steal some ideas, go back to python where you can get >> things done. Little did I know. Several months later here I am. I still >> have not found the reason to give up on Pharo, my questions have been >> answered , found many great libraries to work with and the documentation is >> getting better and better. >> >> Overall my experience is way better than I predicted. Pharo is turning >> into the environment I always wanted to have. Its so unique that I just >> cant compare it with anything else, and the uniqueness is not just in >> details, its almost everywhere. I am so addicted to live coding that I cant >> see myself going back to the old way. This is the future of coding. >> >> I only wish the best for Pharo , not for me but for you guys, you work >> hard for it and you deserve it. Thank you :) >> >> >> >> On Fri, Dec 6, 2013 at 10:33 PM, StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr> wrote: >> >>> Thanks for your warm words (because sometimes I would like so much to >>> improve pharo even more that I'm down). >>> We have a great team (I do not want to list names because I do not want >>> to forget someone). >>> >>> Stef >>> >>> > Maybe others noticed the same: >>> > >>> > - the numbers of closed issues is amazing(see the news on the homepage) >>> > - Pharo3.0 is already really usable and a pleasure to work with >>> > - more and more nice projects appear on STHub and elsewhere >>> > - more and more Pharo projects use continuous integration >>> > - most projects and packages are loadable from the config browser and >>> other places without >>> > conflicting with each other >>> > - there is so much activity regarding Pharo these days on >>> mailinglists, bug-tracker, >>> > twitter, conferences, blogs, stackoverflow, github ... it becomes >>> hard to follow >>> > but this is a good sign >>> > - I see more and more fixes and improvements already as an update >>> coming in before >>> > I really realize that an own bug is needed because it improves the >>> situation >>> > - more and more new names appear on the dev and user mailinglist which >>> is a good >>> > sign that there is growing interest >>> > - Pharo is on the right track and I like to be on the train >>> > >>> > Step by step it goes... >>> > >>> > Bye >>> > T. >>> > >>> > >>> > >>> > >>> >>> >>> >> > -- www.tudorgirba.com "Every thing has its own flow"

Dec. 6, 2013

Re: [Pharo-dev] Pharo magic

by Luc Fabresse

Hi, thanks kilon for sharing your Python experience ;-) I really enjoy listening to people that discover Pharo "recently". Thank you all! #Luc 2013/12/6 kilon alios <kilon.alios(a)gmail.com> > Well I tried pharo just for fun , I knew it would not last. Pharo is > unpopular, not enough libraries, small community , not nearly enough > documentation. Pharo was nothing more than a little break from python. > After all we all know smalltalk is dead , right ? The plan was simple, > have fun with Pharo , steal some ideas, go back to python where you can get > things done. Little did I know. Several months later here I am. I still > have not found the reason to give up on Pharo, my questions have been > answered , found many great libraries to work with and the documentation is > getting better and better. > > Overall my experience is way better than I predicted. Pharo is turning > into the environment I always wanted to have. Its so unique that I just > cant compare it with anything else, and the uniqueness is not just in > details, its almost everywhere. I am so addicted to live coding that I cant > see myself going back to the old way. This is the future of coding. > > I only wish the best for Pharo , not for me but for you guys, you work > hard for it and you deserve it. Thank you :) > > > > On Fri, Dec 6, 2013 at 10:33 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > >> Thanks for your warm words (because sometimes I would like so much to >> improve pharo even more that I'm down). >> We have a great team (I do not want to list names because I do not want >> to forget someone). >> >> Stef >> >> > Maybe others noticed the same: >> > >> > - the numbers of closed issues is amazing(see the news on the homepage) >> > - Pharo3.0 is already really usable and a pleasure to work with >> > - more and more nice projects appear on STHub and elsewhere >> > - more and more Pharo projects use continuous integration >> > - most projects and packages are loadable from the config browser and >> other places without >> > conflicting with each other >> > - there is so much activity regarding Pharo these days on mailinglists, >> bug-tracker, >> > twitter, conferences, blogs, stackoverflow, github ... it becomes >> hard to follow >> > but this is a good sign >> > - I see more and more fixes and improvements already as an update >> coming in before >> > I really realize that an own bug is needed because it improves the >> situation >> > - more and more new names appear on the dev and user mailinglist which >> is a good >> > sign that there is growing interest >> > - Pharo is on the right track and I like to be on the train >> > >> > Step by step it goes... >> > >> > Bye >> > T. >> > >> > >> > >> > >> >> >> >

Dec. 6, 2013

Re: [Pharo-dev] Pharo magic

by kilon alios

Well I tried pharo just for fun , I knew it would not last. Pharo is unpopular, not enough libraries, small community , not nearly enough documentation. Pharo was nothing more than a little break from python. After all we all know smalltalk is dead , right ? The plan was simple, have fun with Pharo , steal some ideas, go back to python where you can get things done. Little did I know. Several months later here I am. I still have not found the reason to give up on Pharo, my questions have been answered , found many great libraries to work with and the documentation is getting better and better. Overall my experience is way better than I predicted. Pharo is turning into the environment I always wanted to have. Its so unique that I just cant compare it with anything else, and the uniqueness is not just in details, its almost everywhere. I am so addicted to live coding that I cant see myself going back to the old way. This is the future of coding. I only wish the best for Pharo , not for me but for you guys, you work hard for it and you deserve it. Thank you :) On Fri, Dec 6, 2013 at 10:33 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Thanks for your warm words (because sometimes I would like so much to > improve pharo even more that I'm down). > We have a great team (I do not want to list names because I do not want to > forget someone). > > Stef > > > Maybe others noticed the same: > > > > - the numbers of closed issues is amazing(see the news on the homepage) > > - Pharo3.0 is already really usable and a pleasure to work with > > - more and more nice projects appear on STHub and elsewhere > > - more and more Pharo projects use continuous integration > > - most projects and packages are loadable from the config browser and > other places without > > conflicting with each other > > - there is so much activity regarding Pharo these days on mailinglists, > bug-tracker, > > twitter, conferences, blogs, stackoverflow, github ... it becomes hard > to follow > > but this is a good sign > > - I see more and more fixes and improvements already as an update coming > in before > > I really realize that an own bug is needed because it improves the > situation > > - more and more new names appear on the dev and user mailinglist which > is a good > > sign that there is growing interest > > - Pharo is on the right track and I like to be on the train > > > > Step by step it goes... > > > > Bye > > T. > > > > > > > > > > >

Dec. 6, 2013