March 2016 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Call about Numerical Methods in Pharo :)

by Nicolai Hess

Thank you StÃ©phane Ducasse, thank you Eliot Miranda, and all other people of this community. I appreciate what all you are doing (as a teacher / developer / user / supporter) for <enter your favourite name for this great exceptional computing environment> and it is a pleasure for me to work with you. (this is all I have to say to this topic) Thanks ! And go one :-) nicolai

March 6, 2016

Re: [Pharo-dev] For future version of Spotter

by Yuriy Tymchuk

I want to have the same thing for > On 06 Mar 2016, at 14:44, stepharo <stepharo(a)free.fr> wrote: > > > > Le 6/3/16 11:39, Tudor Girba a Ã©crit : >> Hi, >> >> This is on the todo list, but I would rather want to have that in settings with a button. > > sure > >> I did not check if this is possible yet. Does anyone know if it is? I want to have the same thing for my stuff. Let me know if you find out how to do that. (Juraj was working with settings. Maybe he knows something) Cheers. Uko > > it could be also in the help. > Normally you do not shoot videos every day or need to get to a clean state. >> >> Cheers, >> Doru >> >> >>> On Mar 6, 2016, at 10:53 AM, stepharo <stepharo(a)free.fr> wrote: >>> >>> Add a menu doing >>> >>> GTSpotter cleanUp. >>> GTSpotter dontShowPreview >>> >>> Stef >>> >> -- >> www.tudorgirba.com >> www.feenk.com >> >> "Every thing should have the right to be different." >> >> >> >> >> >> > >

March 6, 2016

Re: [Pharo-dev] [Bloc] ing versus er

by stepharo

Thanks for doing it ;) Stef Le 6/3/16 10:27, Aliaksei Syrel a Ã©crit : > > Thanks for looking into bloc! :) > > On Mar 6, 2016 10:20 AM, "stepharo" <stepharo(a)free.fr > <mailto:stepharo@free.fr>> wrote: > > wrapContent > self resizing: BlLayoutWrapContentResizing new > > I will rename such code to be > > wrapContent > self resizer: BlLayoutWrapContentResizer new > > > BlLayoutWrapContentResizer is a strategy (and object responsible > of doing something) > and as such it is much better to use er and ing. > > Comment if needed. > Stef >

March 6, 2016

Re: [Pharo-dev] For future version of Spotter

by stepharo

Le 6/3/16 11:39, Tudor Girba a Ã©crit : > Hi, > > This is on the todo list, but I would rather want to have that in settings with a button. sure > I did not check if this is possible yet. Does anyone know if it is? it could be also in the help. Normally you do not shoot videos every day or need to get to a clean state. > > Cheers, > Doru > > >> On Mar 6, 2016, at 10:53 AM, stepharo <stepharo(a)free.fr> wrote: >> >> Add a menu doing >> >> GTSpotter cleanUp. >> GTSpotter dontShowPreview >> >> Stef >> > -- > www.tudorgirba.com > www.feenk.com > > "Every thing should have the right to be different." > > > > > >

March 6, 2016

Re: [Pharo-dev] [ANN][Bloc] February report

by stepharo

Hi Alex How can I "compile" the doc and read it? Clement in his tutorial on VM use pillar and download an image and extract from the image the examples so may be we could do the same. Should I run the examples when I do a change to make sure that I'm not breaking something. How do you get green tests? Stef Le 6/3/16 12:34, Aliaksei Syrel a Ã©crit : > Hi all > > Today is sunday meaning that we should make a monthly report on what > happened in Bloc in February. > > - BlLinearLayout (stack layout + proportional layout) > > * Uses gtExample for examples and tests: BlLinearLayoutExamples > * Has extensive class docs and method docs. Still some methods are > missing docs. > * Has "book" chapter (more info below) > > - Integration with OS-Window > > * Finally works, really fast. > * Events do not work as expected because of > https://pharo.fogbugz.com/f/cases/17757 > > - Unified shape scaling behaviour. > > * By default shape scales to fill BlElement's extent. > * Supports different resizing strategies. > * Started "book" chapter > > - Added documentation to various parts of Bloc > > * Still there are a lot of places not covered with docs. > * Also we auto-generate "book" chapters from bloc example classes. > In attachment you can find linear-layout and not finished shape > chapter. > > _Future_ > > - Bloc presentation on PharoDays2016 <http://pharodays2016.pharo.org> > > * 01 April 2016 > * 11:05â11:25 Bloc: Towards a vector-based GUI > > - Working on > > * Grid layout (all rules above apply, docs + tests + chapter) > * Bloc tests > * Documentation > > > Cheers, > Alex >

March 6, 2016

Re: [Pharo-dev] [ANN][Bloc] February report

by stepharo

***Thanks*** for this report! Stef Le 6/3/16 12:34, Aliaksei Syrel a Ã©crit : > Hi all > > Today is sunday meaning that we should make a monthly report on what > happened in Bloc in February. > > - BlLinearLayout (stack layout + proportional layout) > > * Uses gtExample for examples and tests: BlLinearLayoutExamples > * Has extensive class docs and method docs. Still some methods are > missing docs. > * Has "book" chapter (more info below) > > - Integration with OS-Window > > * Finally works, really fast. > * Events do not work as expected because of > https://pharo.fogbugz.com/f/cases/17757 > > - Unified shape scaling behaviour. > > * By default shape scales to fill BlElement's extent. > * Supports different resizing strategies. > * Started "book" chapter > > - Added documentation to various parts of Bloc > > * Still there are a lot of places not covered with docs. > * Also we auto-generate "book" chapters from bloc example classes. > In attachment you can find linear-layout and not finished shape > chapter. > > _Future_ > > - Bloc presentation on PharoDays2016 <http://pharodays2016.pharo.org> > > * 01 April 2016 > * 11:05â11:25 Bloc: Towards a vector-based GUI > > - Working on > > * Grid layout (all rules above apply, docs + tests + chapter) > * Bloc tests > * Documentation > > > Cheers, > Alex >

March 6, 2016

Re: [Pharo-dev] Call about Numerical Methods in Pharo :)

by Benoit St-Jean

Amen! My lastname is St-Jean, like it or not I'm closer to Ducasse than Hollansworth! I discovered Smalltalk with ObjectWorks on AIX : I'm closer to Pharo than Python, C, C++, C#, Ruby, Snobol, Dart, Go or any other language... Like it or not, I'm closer to Smalltalk than Java, COBOL or any other retarded programming language... I've been working as a consultant in Smalltalk since the 90s.Â I don't care : VW, VAST, VSE as long as it's Smalltalk!Â I'm closer to Pharo than I am to anything else (except Modula-2). This stupid war is sooooooo stupid! If you know what the DNU acronym means, you're a Smalltalker. Period. Pharo can go its own way (whether I like it nor not), but it's still Smalltalk! These guys (the Pharoers, and StÃ©phane Ducasse) have made *tremendous* steps forward. Like "how come nobody ever did that for Smalltalk except James Robertson" ? I like Pharo.Â I fell in love with VW 2.5.Â Vous Ãªtes si belles, vous toutes! I love Smalltalk! Â ----------------- BenoÃ®t St-Jean Yahoo! Messenger: bstjean Twitter: @BenLeChialeux Pinterest: benoitstjean IRC: lamneth Blogue: endormitoire.wordpress.com "A standpoint is an intellectual horizon of radius zero".Â (A. Einstein) From: Dimitris Chloupis <kilon.alios(a)gmail.com> To: Pharo Development List <pharo-dev(a)lists.pharo.org> Sent: Sunday, March 6, 2016 7:00 AM Subject: Re: [Pharo-dev] Call about Numerical Methods in Pharo :) Sorry guys but I dont think this is non sense because you may be coding in Pharo and Smalltalk for a long time, but as a beginner I was confused by this, and to this day I am still confused why Pharo is not calling itself a modern implementation of Smalltalk. Even in Pharo by Example there was no mention at all the Pharo is a Squeak fork, nothing, now there is (few week before) , guess who added it. No mention about Squeak in our website whatsoever.Â Why ? Do we just fork and forget about them ? Also this whole guilt about the so called "failure" or "death" of smalltalk is hilarious. Smalltalk was never popular and we certainly wont be with Pharo, because in the end its very unfamiliar and most coders dont like going outside their comfort zone. PersonallyÂ I am fine with that but this is why I use Pharo to get outside my comfort zone and think outside the box, but I dont kid myself, I belong to a tiny minority. I am sorry if you feel that we derail the thread, but some of us feel very uncomfortable by some people trying to mislead newcomers that Pharo will at some point brake away from Smalltalk heritage when we all know that wont happen for the following reasons 1) Smalltalk is an awesome language and its failure to become popular has nothing to do with the IDE and the language and more to do with lack of libraries, documentation and third party tool support plus of course the all important familiarity b) Most likely a ton of Squeak and older Smalltalk code will remain in Pharo because none sane enough would removed code that has stood the test of time, is well designed and works c) Even if you have a tiny sense or realism you will realize that the reason why people use Pharo is because is a modern implementation of smalltalk, trying to connect with modern technologies but at same time remaining a smalltalk in the core. And finally lets take into account that all languages are evolving. I was coding C++ till 1996 and was very frustrated with the language, manual memory management, inflexible type system, horrible GUI libraries (MFC). Now I learn C++ 11 which means an almost fully dynamic type systems (see auto , templates etc) , automatic memory management (smart pointers), vast array of greatly design GUI and graphics libraries (QT, Unreal, GTK etc). In 20 years C++ has become night and day, sure still much more ugly than Pharo but far, far better . Did we stop calling it C++ ? I totally agree, that this discussion arises few time per year and in the end we dont agree. But I dont post here to make you change your mind, I know people rarely do that, I post here because I want to make crystal to begineers viewing this mailing that for me and many others: Pharo IS Smalltalk, Pharo IS a Squeak fork, Pharo is a modern implementation that tries to push forward but respects its heritage and pays credit to it.Â Â Â Saying that if this numpy variant library intends to target only Pharo then it makes more sense to call it SciPharo. On Sun, Mar 6, 2016 at 12:30 PM Volkert <volkert(a)komponentenwerkstatt.de> wrote: +100 On 06.03.2016 09:48, stepharo wrote: Why Pharo is not smalltalk and will not be Smalltalk Â Â Â - First because we make it to free us from the past. Â Â Â - In the future we want that people that learned smalltalk in the 90 do not discard Pharo because Â Â Â Â Â Â Â Â Â Â Â Â - "what killed smalltalk was that we could not work well in team" Â Â Â Â Â Â Â Â Â Â Â Â - "smalltalk oh it does not scale" Â Â Â Â Â Â Â Â Â Â Â Â - "I cannot edit my code with emacs" Â Â Â Â Â Â Â Â Â Â Â Â - "oh back in 1993 I got lecture and the system took 10 min to boot on our sparc (I got this story yesterday)" Â Â Â Â Â Â Â Â Â Â Â Â - I did not get how you work in team Â Â Â Â Â Â Â Â Â Â Â Â - "with Smalltalk you cannot save your code in svn" Â Â Â Â Â Â Â Â Â Â Â Â - "Smalltalk is monolithic" Â Â Â Â Â Â Â Â Â Â Â Â - "you are in a cage you cannot interact with the outside world" a guy organising OOPSLA Â Â Â Â Â Â Â Â Â Â Â Â - "Smalltalk what a dated name! bavardage: tu programmes en bavardage, donc les resultats ne doivent pas Â Â Â Â Â Â Â Â Â Â Â Â etre si super que cela...." I do not care that these statements are right or wrong. I do not care that people are ignorant. And yes with some education we can show that they are wrong. There are in the mind of people that got in touch with Smalltalk. No more no less. So may be Smalltalkers should read book about marketing in general. So you are stuck in your history and I'm dreaming about the future: and the future is Pharo not Smalltalk. Face it. There will be no renewal of Smalltalk. Pharo is the chance for Smalltalk to exist in 2050. The future is much more important that the history. You do not make people dreaming telling them that back in the 1940 you add to cross the street to fetch water. left blank on purpose Le 5/3/16 18:22, Eliot Miranda a Ã©critÂ : Stef, On Mar 5, 2016, at 12:10 AM, stepharo <stepharo(a)free.fr> wrote: You probably leave in a protected environment but I do not live in the same. Did you check numPy recently or R? momemtum? Do you think that people do not know how to count? In 1980 my students were not even born, so how can it be better than Â Â Â python, java, c#, lua, ... Do you think that it makes me happy to see my old friends leaving our language and do node.js. Seriously. Why do you blame me? Frankly tell to leave Pharo and I will leave. I can tell you. I think that I need a break in my life in this moment so it would be a good opportunity. Because if each time I do something to improve the wealth and visibility of our system I get such kind of feedback then may be this is the time to do something. Afterall I may be wrong. Seriously if you think that I'm not doing a good job and you want to stay with old friends just let me know. but if I stay then do not tell me that I'm an asshole that does not want to promote smalltalk. I do not blame you.Â I am offended by Pharo disavowing the Smalltalk name.Â I am offended when people state Pharo is notÂ Smalltalk. Â I want to refute false assumptions about the nameÂ Smalltalk, such as the equating it with cobol.Â Instead of taking it personally why don't you address my points about older programming languages whose namesÂ (AFAICT)Â are not perceived negatively? I support this community and am excited to participate in it.Â I admire and respect your efforts, StÃ©phane, in developing, organizing and supporting this community.Â But that does not mean I will keep quiet about something I profoundly disagree with and think is wrong.Â And that thing is to deny Pharo is Smalltalk. And I do this not because I am a zealot, but because words meaning are important, because to understand each other we should call a spade a spade, and because I am grateful for and delighted by this thing called Smalltalk, and I will not support taking credit away from it.Â Ruby is inspired by Smalltalk.Â Pharo is the real thing. Stef Le 5/3/16 02:18, Eliot Miranda a Ã©critÂ : On Fri, Mar 4, 2016 at 12:08 PM, stepharo <stepharo(a)free.fr> wrote: SciPharo? Not so great news from my POV. What is so much pharo specific in this library? Is Smalltalk scientific community large enough for yet another split? Split of what? Let us be tagged with a name of 1980 and die in peace. Yes this looks like a smart move. There are just Python and R and Javascript around (not talking about ruby and swift) so this is a great move. We are not the cobol of object-oriented programming!! When I read sentiments like this it makes me want to leave the community.Â I find it so offensive that the Pharo community uses Smalltalk but wants to distance itself.Â It feels like theft or massive disrespect for the inventors of the language, or a complete lack of gratitude. C is older than Smalltalk and no one says "C is the cobol of low-level imperative languages".Â List is much older than C but no one wants to rename Lisp because it is perceived as old. Smalltalk is a beautiful name, carefully chosen to differentiate and identify the system as different, not arrogant, not hieroglyphic.Â Further, Smalltalkl /is/ different and distinctive materially.Â Why anyone would be ashamed of that incredible heritage and pervasive influence is beyond me. Offended, Eliot

March 6, 2016

Re: [Pharo-dev] [Bloc] content vs contents

by stepharo

This is for bloc so may be contents is better. I will check when it is used and if it returns a collection then we will rename it to contents. I would prefer contents if the majority of implementors use contents over content like that I have a smaller probability of mistakes. Stef Le 6/3/16 12:03, Ben Coman a Ã©crit : > On Sun, Mar 6, 2016 at 5:20 PM, stepharo <stepharo(a)free.fr> wrote: >> Hi native english speaker >> >> what is the best content or contents? > Actually I couldn't say off hand. It depends on the context and I > can't think of a specific rule. I can only present a few examples. > > The contents of the box. > The content of the book - but the book has a Table Of Contents. > > Probably just best to refer to the experts: "grammar content versus contents" > > http://dictionary.cambridge.org/grammar/british-grammar/content-or-contents > > http://english.stackexchange.com/questions/13556/content-or-contents > > http://blogg.lnu.se/english-language-blog/blog/maria/content-and-contents/ > > cheers -ben > >

March 6, 2016

Re: [Pharo-dev] [ANN][Bloc] February report

by Dimitris Chloupis

Thanks Doru :) On Sun, Mar 6, 2016 at 2:14 PM Tudor Girba <tudor(a)tudorgirba.com> wrote: > Hi, > > The goal is to get to an alpha state until PharoDays. > > Cheers, > Doru > > > > On Mar 6, 2016, at 1:11 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> > wrote: > > > > I heard that you made several braking backward compatibility changes to > Bloc, is there a timeline or roadmap when the specification of the API will > stabilize so we can use it without the fear of our GUIs stop working > because Bloc brakes backward compatibility ? > > > > On Sun, Mar 6, 2016 at 1:36 PM Aliaksei Syrel <alex.syrel(a)gmail.com> > wrote: > > Hi all > > > > Today is sunday meaning that we should make a monthly report on what > happened in Bloc in February. > > > > - BlLinearLayout (stack layout + proportional layout) > > â¢ Uses gtExample for examples and tests: BlLinearLayoutExamples > > â¢ Has extensive class docs and method docs. Still some methods are > missing docs. > > â¢ Has "book" chapter (more info below) > > - Integration with OS-Window > > â¢ Finally works, really fast. > > â¢ Events do not work as expected because of > https://pharo.fogbugz.com/f/cases/17757 > > - Unified shape scaling behaviour. > > â¢ By default shape scales to fill BlElement's extent. > > â¢ Supports different resizing strategies. > > â¢ Started "book" chapter > > - Added documentation to various parts of Bloc > > â¢ Still there are a lot of places not covered with docs. > > â¢ Also we auto-generate "book" chapters from bloc example classes. > In attachment you can find linear-layout and not finished shape chapter. > > > > Future > > > > - Bloc presentation on PharoDays2016 > > â¢ 01 April 2016 > > â¢ 11:05â11:25 Bloc: Towards a vector-based GUI > > - Working on > > â¢ Grid layout (all rules above apply, docs + tests + chapter) > > â¢ Bloc tests > > â¢ Documentation > > > > Cheers, > > Alex > > > > -- > www.tudorgirba.com > www.feenk.com > > "To utilize feedback, you first have to acquire it." > > >

March 6, 2016

Re: [Pharo-dev] [ANN][Bloc] February report

by Tudor Girba

Hi, The goal is to get to an alpha state until PharoDays. Cheers, Doru > On Mar 6, 2016, at 1:11 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > > I heard that you made several braking backward compatibility changes to Bloc, is there a timeline or roadmap when the specification of the API will stabilize so we can use it without the fear of our GUIs stop working because Bloc brakes backward compatibility ? > > On Sun, Mar 6, 2016 at 1:36 PM Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi all > > Today is sunday meaning that we should make a monthly report on what happened in Bloc in February. > > - BlLinearLayout (stack layout + proportional layout) > â¢ Uses gtExample for examples and tests: BlLinearLayoutExamples > â¢ Has extensive class docs and method docs. Still some methods are missing docs. > â¢ Has "book" chapter (more info below) > - Integration with OS-Window > â¢ Finally works, really fast. > â¢ Events do not work as expected because of https://pharo.fogbugz.com/f/cases/17757 > - Unified shape scaling behaviour. > â¢ By default shape scales to fill BlElement's extent. > â¢ Supports different resizing strategies. > â¢ Started "book" chapter > - Added documentation to various parts of Bloc > â¢ Still there are a lot of places not covered with docs. > â¢ Also we auto-generate "book" chapters from bloc example classes. In attachment you can find linear-layout and not finished shape chapter. > > Future > > - Bloc presentation on PharoDays2016 > â¢ 01 April 2016 > â¢ 11:05â11:25 Bloc: Towards a vector-based GUI > - Working on > â¢ Grid layout (all rules above apply, docs + tests + chapter) > â¢ Bloc tests > â¢ Documentation > > Cheers, > Alex > -- www.tudorgirba.com www.feenk.com "To utilize feedback, you first have to acquire it."

March 6, 2016