June 2015 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Stack

by stepharo

+1 Thierry we are talking API substituability here. Le 30/6/15 11:30, Tudor Girba a Ã©crit : > What he means is that just because subclassing is available as a > technical mechanism, we should only use it for modeling subtyping and > not implementation reuse (only in very few cases this is actually > useful in the long run). > > For reference, this goes under the name of Liskov substitution > principle and one nice article that explains it is this one: > http://www.objectmentor.com/resources/articles/lsp.pdf > > Cheers, > Doru > > > On Tue, Jun 30, 2015 at 11:21 AM, Thierry Goubier > <thierry.goubier(a)gmail.com <mailto:thierry.goubier@gmail.com>> wrote: > > > > 2015-06-30 11:00 GMT+02:00 stepharo <stepharo(a)free.fr > <mailto:stepharo@free.fr>>: > > > > What I mean is that this is not good to have subclassing when > we can use subclassing. > > > Are you sure you mean that? *confused* > > Thierry > > > > > -- > www.tudorgirba.com <http://www.tudorgirba.com> > > "Every thing has its own flow"

June 30, 2015

Re: [Pharo-dev] Stack

by stepharo

Le 30/6/15 11:20, Marcus Denker a Ã©crit : > >> On 30 Jun 2015, at 11:16, Guillermo Polito <guillermopolito(a)gmail.com >> <mailto:guillermopolito@gmail.com>> wrote: >> >> Another /detail/ is that LinkedList's design is heavily tied to the >> VM. Our linked list implementation can contain any object that *looks >> like a link*, meaning >> - in the higher level they have to understand the message nextLink >> and nextLink: >> - in the lower level, if it is a linked list used by the VM, the >> nextLink should be the first inst var of the object. >> >> What I mean with this is that we should be careful when changing >> linked list. Changing its internal representation may crash your >> image ^^. >> > > We should really rename it to âProcessListâ and put a comment âdo not > touch!!!â, then make a copy and have a Linked List that we can changeâ¦ > there are many issue tracker entries related to the linked list, as > people try to use it but nobody dares to change it. I reimplemented it once. Now I was just consider Stack implementation. > > Marcus >

June 30, 2015

does anybody use the AST navigation?

by stepharo

Hi guys does any of you use the AST code navigation? Because we could remove it. Stef

June 30, 2015

Modern Events Touch and Gestures in Pharo.

by stepharo

Thanks Thales for the sponsoring. https://youtu.be/eNrbH8A5nyY Stef and the rmod team

June 30, 2015

Re: [Pharo-dev] Stack

by Richard Sargent

Sean P. DeNigris wrote > > Thierry Goubier wrote >> I consider that subclassing should be used for implementation reuse and >> not for subtyping. > That is the GoF position and it makes a lot of sense to me. In fact, I > think we Smalltalkers suffer from McLuhan's "people become their tools" > syndrome in that, because the browser makes it easy to view inheritance > trees, we confuse inheritance with subtyping, creating unnecessary > coupling. This also adds to the "Smalltalk has no APIs" problem; when only > subclasses are considered subtypes, one never has to define what is and is > not the public API; protocols could help here, but have never really been > fleshed out for this purpose and are a mess right now due to overloading > with extension method duties. Definitely +1 to that. One of the things I really like about ENVY (as in VA Smalltalk) is the fact that applications/packages have formally modelled prerequisites and the in-image representation of a class also models the contribution of each extending application. (As opposed to "by convention") I'm not claiming ENVY is the be all to end all. It has room for improvement. But it does formally model this particular aspect quite well. -- View this message in context: http://forum.world.st/Stack-tp4834494p4834964.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

June 30, 2015

[pharo-project/pharo-core]

by GitHub

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

June 30, 2015

[pharo-project/pharo-core] 88b32d: 40617

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 88b32d40acc3e2e99708146bccaa90f172c69f9d https://github.com/pharo-project/pharo-core/commit/88b32d40acc3e2e99708146b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-06-30 (Tue, 30 Jun 2015) Changed paths: A AST-Core.package/RBConfigurableFormatter.class/class/-- all --/formatOnAccept.st A AST-Core.package/RBConfigurableFormatter.class/class/-- all --/formatOnAccept_.st A AST-Core.package/RBConfigurableFormatter.class/class/-- all --/formatOnDisplay.st A AST-Core.package/RBConfigurableFormatter.class/class/-- all --/formatOnDisplay_.st M AST-Core.package/RBConfigurableFormatter.class/class/-- all --/initialize.st M AST-Core.package/RBConfigurableFormatter.class/class/-- all --/settingsOn_.st A AST-Core.package/RBConfigurableFormatter.class/class/accessing/formatOnAccept.st A AST-Core.package/RBConfigurableFormatter.class/class/accessing/formatOnAccept_.st A AST-Core.package/RBConfigurableFormatter.class/class/accessing/formatOnDisplay.st A AST-Core.package/RBConfigurableFormatter.class/class/accessing/formatOnDisplay_.st M AST-Core.package/RBConfigurableFormatter.class/class/initialization/initialize.st M AST-Core.package/RBConfigurableFormatter.class/class/settings/settingsOn_.st M AST-Core.package/RBConfigurableFormatter.class/definition.st M Nautilus.package/MethodDefinitionAcceptor.class/instance/-- all --/accept_notifying_.st M Nautilus.package/MethodDefinitionAcceptor.class/instance/protocol/accept_notifying_.st A Rubric.package/RubSHTextStylerST80.class/instance/-- all --/format_.st A Rubric.package/RubSHTextStylerST80.class/instance/private/format_.st M ScriptLoader40.package/ScriptLoader.class/instance/-- all --/commentForCurrentUpdate.st R ScriptLoader40.package/ScriptLoader.class/instance/-- all --/script616.st A ScriptLoader40.package/ScriptLoader.class/instance/-- all --/script617.st R ScriptLoader40.package/ScriptLoader.class/instance/-- all --/update40616.st A ScriptLoader40.package/ScriptLoader.class/instance/-- all --/update40617.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script616.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script617.st R ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40616.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40617.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Shout.package/SHTextStyler.class/instance/-- all --/format_.st M Shout.package/SHTextStyler.class/instance/formatting/format_.st Log Message: ----------- 40617 14387 ressurrect format on accept and format on display https://pharo.fogbugz.com/f/cases/14387 http://files.pharo.org/image/40/40617.zip

June 30, 2015

spec TreeNodeModel displayString

by Christophe Demarey

Hi, I have a TreeModel with different kinds of TreeNodeModel and I would like to get a customizable display string depending on the node type. It looks like it is not possible to dispatch on nodes in a display block because it only takes the item (node content) and the tree as parameter. It is strange as I expect that to be a standard feature. Do I miss something? Thanks, Christophe

June 30, 2015

Re: [Pharo-dev] Stack

by Thierry Goubier

2015-06-30 15:30 GMT+02:00 Ben Coman <btc(a)openinworld.com>: > On Tue, Jun 30, 2015 at 5:21 PM, Thierry Goubier > <thierry.goubier(a)gmail.com> wrote: > > > > > > 2015-06-30 11:00 GMT+02:00 stepharo <stepharo(a)free.fr>: > >>> > >>> > >> > >> What I mean is that this is not good to have subclassing when we can use > >> subclassing. > > > > > > Are you sure you mean that? *confused* > > > > Thierry > > Was it meant to be... > "not good to have subclassing when we can use composition" ? > That sounds like it :) Thierry > > cheers -ben > >

June 30, 2015

Re: [Pharo-dev] Stack

by Ben Coman

On Tue, Jun 30, 2015 at 5:21 PM, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > > 2015-06-30 11:00 GMT+02:00 stepharo <stepharo(a)free.fr>: >>> >>> >> >> What I mean is that this is not good to have subclassing when we can use >> subclassing. > > > Are you sure you mean that? *confused* > > Thierry Was it meant to be... "not good to have subclassing when we can use composition" ? cheers -ben

June 30, 2015