- Pharo-dev - lists.pharo.org

Re: [Pharo-project] keymappings question

by Sean P. DeNigris

Sean P. DeNigris wrote: > > What are the minimum things one has to do to have shortcuts working for a > morph class? > Nevermind, I got so excited about shortcuts that I forgot to grab keyboard focus on mouse over :) Sean -- View this message in context: http://forum.world.st/keymappings-question-tp3660905p3990226.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 4, 2011

Re: [Pharo-project] crash of the vm on ubuntu

by Lukas Renggli

What is still not clear to me is what you need to flush when replacing a method with an object. The selector, the old method, the new method, or the behavior? Last time I tried I got the best results flushing the behavior, but I would like to know what should be used for real. Lukas On Friday, 4 November 2011, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Ok > Thanks, we will try > > Alexandre > > > On 4 Nov 2011, at 11:01, Mariano Martinez Peck wrote: > >> >> >> On Fri, Nov 4, 2011 at 2:14 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Hi! >> >> My students are experiencing frequent crashes of the CogVM when playing with Spy (a profiling framework that instrument compile methods and replace them during the execution). My students use a MooseOneClick bundle. I am not sure which version of the CogVM they use actually. Is there a way to check this? >> >> Anyone has experienced frequent crashes with Ubuntu? >> >> There were some issues with #cannotInterpret: and #run:with:in with previous versions of Cog. However, with the last version Eliot' Cog all of them are fixed >> >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- Lukas Renggli www.lukas-renggli.ch

Nov. 4, 2011

Re: [Pharo-project] keymappings question

by Sean P. DeNigris

Guillermo Polito wrote: > > Look at the examples > (the ones defined by Camillo, Laurent or me) and tell me if they are > understandable, hehe. > Where are the examples? I found some methods with <keymap>, and wrote my own using them as a guide, but my ImageMorph subclass is not responding to them. What are the minimum things one has to do to have shortcuts working for a morph class? Thanks. Sean -- View this message in context: http://forum.world.st/keymappings-question-tp3660905p3990184.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Nov. 4, 2011

Re: [Pharo-project] crash of the vm on ubuntu

by Alexandre Bergel

Ok Thanks, we will try Alexandre On 4 Nov 2011, at 11:01, Mariano Martinez Peck wrote: > > > On Fri, Nov 4, 2011 at 2:14 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi! > > My students are experiencing frequent crashes of the CogVM when playing with Spy (a profiling framework that instrument compile methods and replace them during the execution). My students use a MooseOneClick bundle. I am not sure which version of the CogVM they use actually. Is there a way to check this? > > Anyone has experienced frequent crashes with Ubuntu? > > There were some issues with #cannotInterpret: and #run:with:in with previous versions of Cog. However, with the last version Eliot' Cog all of them are fixed > > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > -- > Mariano > http://marianopeck.wordpress.com > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 4, 2011

Re: [Pharo-project] crash of the vm on ubuntu

by Mariano Martinez Peck

On Fri, Nov 4, 2011 at 2:14 PM, Alexandre Bergel <alexandre.bergel(a)me.com>wrote: > Hi! > > My students are experiencing frequent crashes of the CogVM when playing > with Spy (a profiling framework that instrument compile methods and replace > them during the execution). My students use a MooseOneClick bundle. I am > not sure which version of the CogVM they use actually. Is there a way to > check this? > > Anyone has experienced frequent crashes with Ubuntu? > There were some issues with #cannotInterpret: and #run:with:in with previous versions of Cog. However, with the last version Eliot' Cog all of them are fixed > > Cheers, > Alexandre > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > -- Mariano http://marianopeck.wordpress.com

Nov. 4, 2011

Re: [Pharo-project] Simple vs. Easy

by Jimmie Houchin

Forward with permission from Juan Vuletich Fri, 04 Nov 2011 08:42:03 -0300 Hi Folks, I'm answering you off-list because I'm not subscribed to the Pharo list. Feel free to forward this there, if you wish. I think it is great to put focus on simplicity (an objective value) over easyness (a subjective value). Rich also makes a good critic to usual practices, including the dichotomy between understanding and TDD (test driven development). However, the value of simplicity is not something new. The difference between essential complexity and accidental complexity is the heart of "No Silver Bullet â Essence and Accidents of Software Engineering" (by Fred Brooks, 1986) and "There Is a Silver Bullet" (by Brad Cox, 1990, http://drdobbs.com/184407534) It is also central to Smalltalk, see "Design Principles Behind Smalltalk" (by Dan Ingalls, 1981, http://classes.soe.ucsc.edu/cmps112/Spring03/readings/Ingalls81.html) These three articles might be the most important writings on software engineering ever. The problem with this discussion is that everybody will claim simplicity is a crucial objective of their project. However, Pharo and Squeak don't realize (or don't want to realize) that simplicity appears only by removing complexity, never by adding more of it. Cuis is a Squeak fork with the #1 objective of being simple and understandable. It is the result of more than 10 years suffering the accidental complexity in Squeak, comparing with other Smalltalks, together with a lot of reflection and work, by me and others. It is, I believe, the only Smalltalk in active development that pursues this objective of the original Smalltalk-80 project. You can get it from http://www.jvuletich.org/Cuis/Index.html . Browse it a bit. Take statistics (lines of code, etc). Compare. You might have a nice surprise. Jimmie, you asked "How can we move Pharo to be a better answer to Simple vs. Easy?". My answer is: start anew. Rebase on top of Cuis. Give up feature list as a priority, and focus on simplicity. Make a list of the features in Pharo that are really important, and not part of Cuis, and turn them into optional packages. Make that list as short as possible! Worry more about code quality and less about discarding potentially useful stuff, that is not good enough. Cheers, Juan Vuletich

Nov. 4, 2011

[Pharo-project] crash of the vm on ubuntu

by Alexandre Bergel

Hi! My students are experiencing frequent crashes of the CogVM when playing with Spy (a profiling framework that instrument compile methods and replace them during the execution). My students use a MooseOneClick bundle. I am not sure which version of the CogVM they use actually. Is there a way to check this? Anyone has experienced frequent crashes with Ubuntu? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Nov. 4, 2011

[Pharo-project] [update 1.4] #14215

by StÃ©phane Ducasse

14215 ----- - Issue 4957: Let asScaledDecimal use the right number of decimals Thanks nicolas cellier. http://code.google.com/p/pharo/issues/detail?id=4957 Change the policy for conversions to ScaledDecimal. Always honour the number of decimal places (scale) passed as argument to asScaledDecimal: When no scale is passed, uses strictly necessary number of decimal places if the number is exact (not Float) and if a finite decimal representation exists. Otherwise uses the default of 8 decimal places. This makes more sense IMO than previous implementation. Integer version was screwing the user by not fulfiling the requested number of decimal places, I can t believe it was the right interpretation of the ANSI standard.... Or someone gives me a good rationale. - Issue 4964: Number nthRoot: should be subclassResponsibility. Thanks nicolas cellier. http://code.google.com/p/pharo/issues/detail?id=4964 - Issue 4951: The version menu in the diff tool does not work. Thanks nicolas cellier. http://code.google.com/p/pharo/issues/detail?id=4951 - Issue 3197: Make Character class>>separators and Character class>>allByteCharacters return strings instead of Arrays. Thanks nicolas cellier, Andreas raab, and vonbecmann. http://code.google.com/p/pharo/issues/detail?id=3197 Stef

Nov. 4, 2011

Re: [Pharo-project] Someone bought Smalltalk?

by S Krish

I guess, this seems like a reference to the Cincom change in license format from: Non-Commercial to a Personal Use license that in effect bars any use of an organization rolling out Cincom VW / OS applications without paying the license. Personal license now dictates only an individual in his own personal single workstation having / using VW. Ofcouse the point about American co having bought Smalltalk seem out of synch as it occured a decade back. There is a long list of email chain on the VW list that allows lot of stuff despite the legalese, but I guess it is still muddy and does attract the legal notices on various organizations. ****************************** But I hope there is no real danger of Pharo / Squeak attracting any such provisions : "O*riginal Apple code, which is governed by the **Apache License*<http://en.wikipedia.org/wiki/Apache_License> *.* *Originally, Apple actually released Squeak under a license called the "Squeak License." While source code was available and modification permitted, the Squeak License contained an **indemnity clause*<http://en.wikipedia.org/wiki/Indemnity_clause> * that prevented it from qualifying as true **Free and Open Source Software*<http://en.wikipedia.org/wiki/Free_and_Open_Source_Software> *.* *In 2006, Apple relicensed Squeak twice. First, in May, Apple used its own * *Apple Public Source License*<http://en.wikipedia.org/wiki/Apple_Public_Source_License> *, which satisfies the **Free Software Foundation*<http://en.wikipedia.org/wiki/Free_Software_Foundation> *'s concept of a Free Software License [6]<http://en.wikipedia.org/wiki/Squeak#cite_note-5>and has attained official approval from the **Open Source Initiative*<http://en.wikipedia.org/wiki/Open_Source_Initiative> *[7]* <http://en.wikipedia.org/wiki/Squeak#cite_note-6>* as an Open Source License." * On Tue, Nov 1, 2011 at 6:43 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > Oh, my God! I will have to delete every piece of Smalltalk evidence! > > Ah, but I guess it will be a while until they get to Switzerland. I just > hope they do not catch me in Argentina. > > Doru > > > > On 1 Nov 2011, at 11:12, Damien Cassou wrote: > > > I just received this email: > > > > > > ---------- Forwarded message ---------- > > > > I heard some rumors about Smalltalk. Apparently, an american > > enterprise bought Smalltalk and is trying to make money by sueing > > users. Therefore, they changed the licence agreements (and maybe other > > stuff). In my company we have a strict interdiction to use Smalltalk. > > > > > > -- > > Damien Cassou > > http://damiencassou.seasidehosting.st > > > > "Lambdas are relegated to relative obscurity until Java makes them > > popular by not having them." James Iry > > > > -- > www.tudorgirba.com > > "Some battles are better lost than fought." > > > > >

Nov. 4, 2011

Re: [Pharo-project] relation to squeak

by Frank Shearar

On 4 November 2011 08:28, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > > > Frank > > When I write we usually talk about my team or myself. Yes, I know. I just wanted to indicate that the Pharo/Squeak split is not as severe, for want of a better word, as might seem at first. While Pharo and Squeak have different goals, they're not antithetical goals. > Now I have a question: did you sign the pharo license because else it would indicate that you are not really interested in contributing > to our vision but more taking from it. This is ok too. You can do that but this is less positive energy. Actually, I have, but I must still post it off to you. Thanks for the reminder! (And of course the libraries I put on SqueakSource (zippers, delimited continuations, and so on) are all MIT, and I would be most appreciative of bug reports, critiques etc., that members of the Pharo community might send my way. frank > Stef > >>> >>>> Hello! >>>> >>>> One thing is not clear to me. How is Pharo related to standard Squeak? I know Pharo is a fork with its own mission, but is the development related? Do fixes in Pharo propagate upstream to Squeak? Is Squeak even considered "upstream"? Do fixes in Squeak propagate into Pharo? Automatically or manually? Or have they started being developed completely independently from some point in time? >>> >>> We do not really look at squeak. No time for that. Now if people having time mentioned that we have an interesting fix then we will be inclined to include it in pharo. >> >> Well, I guess it depends on what you mean by "we" - "we" as an >> Official Pharo Official, sure, I can understand - rightly so - that >> you're concentrating on what Pharo needs. "We" as a vocal subcommunity >> of Pharo also work with Squeak, trying to pull the two codebases back >> together. >> >> And that's a good thing, that there are both forces. Pharo the >> Official Direction is cutting new ground in a particular direction, >> and the Pharo+Squeak folk try to make sure that there isn't too much >> duplication of effort. There are few enough Smalltalkers in the two >> communities: we ought to try leverage off each other as much as we >> can. >> >> frank >> >>> Let me restate our vision and why we decided to make Pharo. >>> Our goal and vision behind Pharo is to twofold: >>> Â Â Â Â - make sure that people can make money and create their own wealth in Smalltalk. Provide the best environment we can for that (and this is not easy) >>> Â Â Â Â This is really important for us. A part of the team here is working on setting up a company around tools build on top of Pharo. >>> Â Â Â Â We are really happy when we hear that people are using Pharo for making business (net style, nextPlan, b9, pinesoft)â¦. >>> Â Â Â Â This is really great. >>> >>> Â Â Â Â - bring Smalltalk to the next level: >>> Â Â Â Â Â Â Â Â - first class variables >>> Â Â Â Â Â Â Â Â - small core >>> Â Â Â Â Â Â Â Â - may be new mop >>> Â Â Â Â Â Â Â Â - powerful tools and abstractions >>> Â Â Â Â The idea is to have a solid infrastructure to be able to invent the next generation smalltalkish system because smalltalk lacks a lot and innovation stopped a while ago. >>> Â Â Â Â Â Â Â Â (real sandboxing, real minimal kernel with pluggable uiâ¦) >>> >>> It will take time but we will get there. >>> >>> Stef >>> >> > > >

Nov. 4, 2011