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

Re: [Pharo-dev] Roassal2 / Application Matrix

by Alexandre Bergel

Hi Volkert, There was a small problem when we generated the SVG file. Milton fixed it. Update Roassal and you will enjoy the expected behavior. By the way, will you be at esug? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 30, 2015, at 2:50 PM, volkert <volkert(a)komponentenwerkstatt.de> wrote: > > That is my plan ;-) Can you have look to the svg export? The inner boxes have no coloring. > > BW, > Volkert > > Am 30.06.2015 um 00:53 schrieb Alexandre Bergel: >> Volker, I started to do something called RTApplicationMatrix. >> But the Peterâs script seems to do a much better job. It would be great if you can structure it a bit. >> >> Alexandre >> >> >>> On Jun 28, 2015, at 8:56 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> >>> Well if you want super-crude procedural prototype, I've made this http://ws.stfx.eu/MSUIRBAZKN2O >>> >>> <2015-06-28_13:50:17.png> >>> âThe layouting is very, very ugly and could be probably be simplified with RTNest and RTCellLayout on the whole table, but I wanted to spend âas little time as possible (the whole code in ~30 minutes). >>> You can read more about RTNest here https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Roassal/010… (section 5) (and all chapters are here http://agilevisualization.com/#book ) >>> >>> Also in your original picture there are boxes with rounded corners; Roassal doesn't support this yet (afaik), but I can send you implementation for it as I have it in my project. >>> >>> Peter >>> >>> On Sun, Jun 28, 2015 at 1:30 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Hi ! >>> >>> Yes, this is trivial I would say. >>> This evening I will give a try >>> >>> Alexandre >>> >>> >>>> Le 28 juin 2015 Ã 04:49, Volkert <volkert(a)komponentenwerkstatt.de> a Ã©crit : >>>> >>>> Dear all, >>>> >>>> is such a visualization out of the box possible with Roassal2? >>>> >>>> BW, >>>> Volkert >>>> >>>> <Application Matrix> >>> > >

June 30, 2015

Re: [Pharo-dev] [Pharo-users] Modern Events Touch and Gestures in Pharo.

by J.F. Rick

Awesome! There's a reasonable chance that I can contribute to this (or at least utilize it), depending on what contracts I get. If I do get that in the near future, who do I contact about contributing? Cheers, Jeff On Tue, Jun 30, 2015 at 1:18 PM stepharo <stepharo(a)free.fr> wrote: > Thanks Thales for the sponsoring. > > https://youtu.be/eNrbH8A5nyY > > Stef and the rmod team > >

June 30, 2015

Re: [Pharo-dev] Roassal2 / Application Matrix

by Alexandre Bergel

Ok Having a look at it now... Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Jun 30, 2015, at 2:50 PM, volkert <volkert(a)komponentenwerkstatt.de> wrote: > > That is my plan ;-) Can you have look to the svg export? The inner boxes have no coloring. > > BW, > Volkert > > Am 30.06.2015 um 00:53 schrieb Alexandre Bergel: >> Volker, I started to do something called RTApplicationMatrix. >> But the Peterâs script seems to do a much better job. It would be great if you can structure it a bit. >> >> Alexandre >> >> >>> On Jun 28, 2015, at 8:56 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >>> >>> Well if you want super-crude procedural prototype, I've made this http://ws.stfx.eu/MSUIRBAZKN2O >>> >>> <2015-06-28_13:50:17.png> >>> âThe layouting is very, very ugly and could be probably be simplified with RTNest and RTCellLayout on the whole table, but I wanted to spend âas little time as possible (the whole code in ~30 minutes). >>> You can read more about RTNest here https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Roassal/010… (section 5) (and all chapters are here http://agilevisualization.com/#book ) >>> >>> Also in your original picture there are boxes with rounded corners; Roassal doesn't support this yet (afaik), but I can send you implementation for it as I have it in my project. >>> >>> Peter >>> >>> On Sun, Jun 28, 2015 at 1:30 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >>> Hi ! >>> >>> Yes, this is trivial I would say. >>> This evening I will give a try >>> >>> Alexandre >>> >>> >>>> Le 28 juin 2015 Ã 04:49, Volkert <volkert(a)komponentenwerkstatt.de> a Ã©crit : >>>> >>>> Dear all, >>>> >>>> is such a visualization out of the box possible with Roassal2? >>>> >>>> BW, >>>> Volkert >>>> >>>> <Application Matrix> >>> > >

June 30, 2015

Re: [Pharo-dev] Stack

by Thierry Goubier

Le 30/06/2015 19:27, stepharo a Ã©crit : > alain fixed in place edit for string morph so we could even rename a > protocol simply by double clicking on it. I noticed years ago that I could get that for free in a MorphTreeMorph by using a text instead of a string in the node description: would give you many, many types of renames, not only protocols. > But this is another story Yes and no. There are complaints about the model, and when you see the state of the tools... you can't be impressed by the fact it wasn't improved a long time ago. But maybe like that it makes some tools look better. Thierry

June 30, 2015

Re: [Pharo-dev] Roassal2 / Application Matrix

by volkert

That is my plan ;-) Can you have look to the svg export? The inner boxes have no coloring. BW, Volkert Am 30.06.2015 um 00:53 schrieb Alexandre Bergel: > Volker, I started to do something called RTApplicationMatrix. > But the Peterâs script seems to do a much better job. It would be great if you can structure it a bit. > > Alexandre > > >> On Jun 28, 2015, at 8:56 AM, Peter UhnÃ¡k <i.uhnak(a)gmail.com> wrote: >> >> Well if you want super-crude procedural prototype, I've made this http://ws.stfx.eu/MSUIRBAZKN2O >> >> <2015-06-28_13:50:17.png> >> âThe layouting is very, very ugly and could be probably be simplified with RTNest and RTCellLayout on the whole table, but I wanted to spend âas little time as possible (the whole code in ~30 minutes). >> You can read more about RTNest here https://dl.dropboxusercontent.com/u/31543901/AgileVisualization/Roassal/010… (section 5) (and all chapters are here http://agilevisualization.com/#book ) >> >> Also in your original picture there are boxes with rounded corners; Roassal doesn't support this yet (afaik), but I can send you implementation for it as I have it in my project. >> >> Peter >> >> On Sun, Jun 28, 2015 at 1:30 PM, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Hi ! >> >> Yes, this is trivial I would say. >> This evening I will give a try >> >> Alexandre >> >> >>> Le 28 juin 2015 Ã 04:49, Volkert <volkert(a)komponentenwerkstatt.de> a Ã©crit : >>> >>> Dear all, >>> >>> is such a visualization out of the box possible with Roassal2? >>> >>> BW, >>> Volkert >>> >>> <Application Matrix> >>

June 30, 2015

Re: [Pharo-dev] Stack

by Thierry Goubier

Le 30/06/2015 19:26, stepharo a Ã©crit : > +1 > > Thierry we are talking API substituability here. Yes I know. Thierry > 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] pharo 50140 failing release test

by stepharo

Thanks Nicolai. Alain is head first in exam corrections :) I'm heading to paris for our award reception. Stef Le 29/6/15 22:55, Nicolai Hess a Ã©crit : > @alain @steph > can you check update pharo 50140 > somehow all TAbleToRotate methods (protocol t-rotating) were copied > to class StringMorph. > And now ReleaseTest > testLocalMethodsOfTheClassShouldNotBeRepeatedInItsTraits > fails > > > nicolai >

June 30, 2015

Re: [Pharo-dev] Stack

by stepharo

Le 30/6/15 15:30, Ben Coman a Ã©crit : > 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" ? and produce coherent API. A stack is not a LinkedList. He can be implemented using a linkedlist. The API of a stack is not the one of a linkedlist. > > cheers -ben > >

June 30, 2015

Re: [Pharo-dev] Stack

by stepharo

>>> 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. + 10 > 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 worked with Envy too and to me this is close to the package we have. And soon we will have package level dependencies. > > 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

Re: [Pharo-dev] Stack

by stepharo

alain fixed in place edit for string morph so we could even rename a protocol simply by double clicking on it. But this is another story Le 30/6/15 15:24, Thierry Goubier a Ã©crit : > > > 2015-06-30 14:05 GMT+02:00 Sean P. DeNigris <sean(a)clipperadams.com > <mailto:sean@clipperadams.com>>: > > 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. > > > I'll wonder what could be done with Traits about that. Traits may be > better at establishing an API. > > Tools could do more to hide the extension thing; I still can't > understand why, more than two years after I did it, all Pharo users > are still writing their * a-long-package-name by hand. I would hate > having to explain to Pharo beginners how to make a method an extension. > > (by the way, dropping a method on a package is a nice way to get a DNU > in Nautilus on Pharo 4...) > > Thierry

June 30, 2015