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

Re: [Pharo-dev] The Smalltalk Renaissance Program
by Ben Coman Jan. 1, 2015

Jan. 1, 2015

Repost (it was rejected as from the wrong account) On Wednesday, December 31, 2014, Ben Coman wrote: > Hi richard, I appreciate your goal. Smalltalk & Pharo do need more PR. I > can see how Pharo not being "a smalltalk" may affect it being your > poster-child for your new site, however you should review the archives > before launching into that argument as a newcomer :) > Although as a PR exercise, outside viewpoints are useful. > > Certainly Pharo does not want to be "constrained" by being "a small talk" > per smalltalk80. However some of the recent posted historical videos put > that in perspective with several PARC small talk versions being quite > different. Small talk continually evolves. > > Btw, can you drop the movie quotations. It comes across a bit high-handed > - like it's trying to teach something - but I can't work out your implied > meaning. Someone else's words can only ever be an approximation. You own > words are better. > > Good Luck with your venture. I'll look into it more when I have Better > net access. > > Ben > > > On Wednesday, December 31, 2014, horrido <horrido.hobbies(a)gmail.com > <javascript:_e(%7B%7D,'cvml','horrido.hobbies(a)gmail.com');>> wrote: > >> Which is why I've chosen Pharo as the public "face" of Smalltalk. It has >> the >> most active community, and the best chance of widespread adoption. >> >> Still, to call it a "new language", to say that "it's not Smalltalk", is a >> mistake. >> >> >> >> -- >> View this message in context: >> http://forum.world.st/The-Smalltalk-Renaissance-Program-tp4797112p4797374.h… >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >>

2 1

GLMGaussianBlurBrickRenderer
by Nicolai Hess Jan. 1, 2015

Jan. 1, 2015

I saw this GLMGaussianBlurBrickRenderer class #example nice! And once I did something similiar, a Morph that blurres the underlaying display. But instead of doing a convolution (convolve image with kernel) by hand, I convolve the kernel with the image by using copyBits from the BitBlt: | form temp dest from to | form := Display contentsOfArea: self bounds. temp := Form extent: self extent depth: 32. temp getCanvas fillColor: Color white darker. dest := Form extent: self extent depth: 32. dest getCanvas fillColor: Color white darker. to := kernel size // 2. from := -1 * to. (from to: to) do: [ :i | temp copyBits: form at: i @ 0 translucent: (kernel at: i + to + 1) ]. (from to: to) do: [ :i | dest copyBits: temp at: 0 @ i translucent: (kernel at: i + to + 1) ]. aCanvas drawImage: dest at: self bounds topLeft.

3 2

Smalltalk Reflections Podcast
by davidbuck Jan. 1, 2015

Jan. 1, 2015

Craig Latta and I have started up a new weekly podcast called Smalltalk Reflections. The web side is http://smalltalkreflections.blogspot.ca/ and it's available from iTunes. We would like to ask the Pharo community if anyone would be interested in participating to promote Smalltalk or Pharo. We'd love to be able to interview people from the Pharo community. Also if anyone would like to take on the task of recording a weekly Pharo insert we'd love to have that as well. If weekly is too frequent for you, we can also arrange monthly or whenever you have time. If you're interested in participating in any way, drop me a line at david(a)simberon.com. Thanks -- View this message in context: http://forum.world.st/Smalltalk-Reflections-Podcast-tp4797444.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

6 8

Question about Todd Blanchards HTML parser
by Chris Muller Dec. 31, 2014

Dec. 31, 2014

Does anyone know why HTMLParseNode's 'parent' is only weakly referenced (instead of strongly)?

1 0

Jun4Pharo so exciting :)
by stepharo Dec. 31, 2014

Dec. 31, 2014

https://www.youtube.com/watch?v=sH_P5otiWJM&feature=youtu.be

8 21

SO Pharo chat
by Yuriy Tymchuk Dec. 31, 2014

Dec. 31, 2014

Hi, as we have some members of the community on Stack Overflow, Iâve created a chat dedicated to Pharo http://chat.stackoverflow.com/rooms/68000/pharo (there are already chats dedicated to different other languages). I have no idea if it will work for the community, but it never hurts to try. For now, happy new year all! Uko P.S. yes, Iâm bored while waiting for a party :)

1 0

Morph to TakskbarMorph
by Roberto Minelli Dec. 31, 2014

Dec. 31, 2014

Hi, I am trying to understand some Morphic. It looks like the dark side. Anyway, I am trying to reconstruct the relationship between a Morph, say a SystemWindow and its PluggableButtonMorph contained in the TakskbarMorph. Any suggestion? Each PluggableButtonMorph in the TakskbarMorph has as #model the ârealâ window, but I cannot find the inverse relationship. Cheers, R

2 2

A toast
by Esteban Lorenzano Dec. 30, 2014

Dec. 30, 2014

Hello Pharoers, (sorry for the long post) I'm on holidays so I've been silent this latests days, but I didn't want to let the opportunity goes to propose a toast :) This year has been a great year (yeah, but not like those annoying facebook cards), one year where we have worked itensively in the patient consolidation of several lines of work. This has been possible thanks to the great improvement that we have made in the Pharo process itself, which required (and still requires) a massive amount of effort: Since I arrived here (but not necessarily *because* I arrived here: this is the work of everyone in Pharo community, I'm just pointing to what I've seen and collaborated :P), we have changed a lot of things: - we have deployed a solid CI infrastructure that can handle our integration cycle without too much complications. Even if we still find problems time to time, this has been an incredible step forward. - thanks to this we have been able to change our release cycle from "it happens when we believe is ready" to time-boxed releases, so we have created Pharo 1.4, 2.0 and this year what, for me, is one of the most complete and cool releases (up to now) that we have produced: Pharo 3.0. - We have increased massively the amount of tests in the system (no sure what is the percentage, but is high), so we have been able to change core parts in the system without causing too much pain to developers (yeah, we know there have been some errors some times, but well... "errare humanum est", and I think we have learned from the process and now we do not make same mistakes... in any case they are new mistakes :P). - We have made huge steps in the "Pharo modularisation project", thanks to the Pharo-minimal images and work we have started to move all into a repeatable configuration (thanks to metacello and tools developed for this). - We have also incorporated the VM building to this process and testing cycle, so is a lot easier for everyone to build their own VM (if needed), and for us we can be sure (as sure as possible at least) VM is in good shape. - We have improved documentation and release new books. People have working a lot in a lot of cool and instructive videos that have moved our "learning curve" several steps ahead. And this is just one part of the "invisible, ant work of everyday", in the visible part, I will not bore (more than needed :P) with details about previous releases, so I will just point some of the great things we have made for the upcoming release, Pharo 4: - Thanks to GTools, we are slowly going to a better set of tools, with new ways of see/handle old things. This is the most visible change this year (and it has caused the most flamed wars, but well... we are a passionate community). This release we have a new inspector, playground and spotter (god, spotter is sooooo cool!), next release we hope to integrate a new debugger and if planets align, a new Coder. - We introduced OSWindow as a preview, a tool which will allow us to do a lot of years waited features: start UI from image instead from VM (transmiting to the used the decision of having one or not), multi-windows, a vectorial UI instead the good-but-old bitblt we have now. - We enhanced Athens and introduced the new TxModel. We still do now achieve our objective of migrate our morphic drawing mechanism to athens, but this is a lot of work and will take some time. - We have improved a lot the development cycle with the introduction of smart suggestions, the upcoming smart breakpoins and reflectivity. - And of course, we have worked a lot in the cleaning of the system (an invisible and ungrateful work, believe me) And this is just a glimpse, what I wrote this morning before breakfast, wanting to thank all of you to let me be part of this super cool community, and wanting to have a toast with you: For a 2015 with more stories, more adventures, more Pharo! Esteban

7 8

Dec. 30, 2014

Hello Pharoers, I was wondering, is it a good practice to have negative hashes ? Based on the class comment of Object>>#hash *"Answer a SmallInteger whose value is related to the receiver's identity. [...]"* The hash is a smallInteger and therefore can be negative. Thanks for any answer. Clement

3 3

[pharo-project/pharo-core]
by GitHub Dec. 30, 2014

Dec. 30, 2014

Branch: refs/tags/40426 Home: https://github.com/pharo-project/pharo-core

1 0