- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] [ANN] MatchTool

by Mark Rizun

> > BTW our experience with anne and JC when they tried to document how the > patterns were working is that there are some situations > > that are not clear, and this is why Camille and Mark started to work on > another solution. > > I hope to get to know more soom. > There will be a presentation during ESUG. So, see you there :)

Aug. 4, 2016

Re: [Pharo-dev] [ANN] MatchTool

by Yuriy Tymchuk

> On 04 Aug 2016, at 13:34, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > > This is very cool Uko. Thank you. > I suggest to have a list of small examples, one click away from the main UI. Good point, Iâll add this to my TODO list. Uko > > Alexandre > > >> On Aug 4, 2016, at 4:23 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> >> Hi everyone! >> >> Iâm happy to announce a new tool that can help you to understand to the pattern code is working in match & rewrite rules. >> You can read more on my blogpost: http://blog.yuriy.tymch.uk/2016/08/matchtool.html >> The tool is available for Pharo 6 from the catalog. >> >> <Screen Shot 2016-08-01 at 13.40.49.png> >> >> Cheers! >> Uko > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >

Aug. 4, 2016

Re: [Pharo-dev] [ANN] MatchTool

by Yuriy Tymchuk

Yes, I have fixed that, but forgot to merge the development branch :). The latest version should work. Uko > On 04 Aug 2016, at 11:56, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-08-04 11:38 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com <mailto:nicolaihess@gmail.com>>: > Hey Uko, > > this pattern for a message sent: > > `@msg:`@args > > can match message sends with or without arguments, so it matches both > > 1 squared. > and > 1 raisedTo:2 > > The problem is that the first match "1 squared" will give a DNU on the right pane, as the argument var '@args is empty. > > > And if you match a method, it can happen that the keys <-> values in the map are actually strings or text and not a pattern variable > (-source--, -pragma-, and the pattern method selector). > > > > > 2016-08-04 10:23 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: > Hi everyone! > > Iâm happy to announce a new tool that can help you to understand to the pattern code is working in match & rewrite rules. > You can read more on my blogpost: http://blog.yuriy.tymch.uk/2016/08/matchtool.html <http://blog.yuriy.tymch.uk/2016/08/matchtool.html> > The tool is available for Pharo 6 from the catalog. > > <Screen Shot 2016-08-01 at 13.40.49.png> > > Cheers! > Uko > >

Aug. 4, 2016

Re: [Pharo-dev] [ANN] MatchTool

by stepharo

BTW our experience with anne and JC when they tried to document how the patterns were working is that there are some situations that are not clear, and this is why Camille and Mark started to work on another solution. I hope to get to know more soom. Stef Le 4/8/16 Ã 10:23, Yuriy Tymchuk a Ã©crit : > Hi everyone! > > Iâm happy to announce a new tool that can help you to understand to > the pattern code is working in match & rewrite rules. > You can read more on my blogpost: > http://blog.yuriy.tymch.uk/2016/08/matchtool.html > The tool is available for Pharo 6 from the catalog. > > > Cheers! > Uko

Aug. 4, 2016

Re: [Pharo-dev] [ANN] MatchTool

by stepharo

really nice. Stef Le 4/8/16 Ã 10:23, Yuriy Tymchuk a Ã©crit : > Hi everyone! > > Iâm happy to announce a new tool that can help you to understand to > the pattern code is working in match & rewrite rules. > You can read more on my blogpost: > http://blog.yuriy.tymch.uk/2016/08/matchtool.html > The tool is available for Pharo 6 from the catalog. > > > Cheers! > Uko

Aug. 4, 2016

Re: [Pharo-dev] [ANN] MatchTool

by Alexandre Bergel

This is very cool Uko. I suggest to have a list of small examples, one click away from the main UI. Alexandre > On Aug 4, 2016, at 4:23 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > > Hi everyone! > > Iâm happy to announce a new tool that can help you to understand to the pattern code is working in match & rewrite rules. > You can read more on my blogpost: http://blog.yuriy.tymch.uk/2016/08/matchtool.html > The tool is available for Pharo 6 from the catalog. > > <Screen Shot 2016-08-01 at 13.40.49.png> > > Cheers! > Uko -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 4, 2016

Re: [Pharo-dev] [ANN] MatchTool

by Yuriy Tymchuk

Thank you for the feedback Nicolai! I will take a look as soon as I get back home :) Cheers. Uko Sent from my iPhone > On 04 Aug 2016, at 11:56, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > > 2016-08-04 11:38 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: >> Hey Uko, >> >> this pattern for a message sent: >> >> `@msg:`@args >> >> can match message sends with or without arguments, so it matches both >> >> 1 squared. >> and >> 1 raisedTo:2 >> >> The problem is that the first match "1 squared" will give a DNU on the right pane, as the argument var '@args is empty. > > And if you match a method, it can happen that the keys <-> values in the map are actually strings or text and not a pattern variable > (-source--, -pragma-, and the pattern method selector). > > >> >> >> 2016-08-04 10:23 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: >>> Hi everyone! >>> >>> Iâm happy to announce a new tool that can help you to understand to the pattern code is working in match & rewrite rules. >>> You can read more on my blogpost: http://blog.yuriy.tymch.uk/2016/08/matchtool.html >>> The tool is available for Pharo 6 from the catalog. >>> >>> <Screen Shot 2016-08-01 at 13.40.49.png> >>> >>> Cheers! >>> Uko >

Aug. 4, 2016

Re: [Pharo-dev] let's talk about themes (and GLMBrickThemer)

by Tudor Girba

Hi Esteban, Sorry for the delayed response. There are two parts in your mail: 1. the decomposition of theme to have one themer per widget 2. a centralized catalog of values I certainly agree with 2. In fact, when I refactored the theme colors a long time ago, I introduced a rudimentary reuse mechanism on the class side of the Theme class. So, now, we should extract those separately. About 1., I have a different opinion. The hierarchy you mention already exists in the Theme class as well, only it is hidden, and it is very hard to see what each methods impacts. Here is how I reached this conclusion. Take a look at this picture I produced before we started with Brick (the one from Morphic). The gray circles are methods in UITheme, and the red circles are typical Morphs (like TextMorph, ListMorph). The gray lines show self calls inside the UITheme, and the red lines shod calls from the morph to the UITheme methods. What you see here is a very strong clustering of the methods around the widgets, and this indicates that having a theme object per widget is appropriate. A further constrain is that we want to be able to change the appearance of a widget on an instance basis (that is, overriding the default theme setting), and having a per-widget themer object, we can achieve that as well. A similar design appears in Bloc as well, and I think it is actually more scalable then the current UITheme, provided that you indeed have a way to either centralize the definitions of colors (and other properties), or inject those properties from the outside. All in all, letâs go ahead and extract the palette :). Cheers, Doru > On Aug 1, 2016, at 11:13 AM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > For one of my side-projects, I made a new theme for Pharo (still no name, I was planing to call it âDark Metalâ or something like that. Is a variation on the Dark Theme but âourâ dark theme is more brown and this one is more blue (see attached)â¦ I wanted to publish it to push it but then I arrived to an unexpected problem: For Spotter and GTTools in general, theming is not done following current theming approach. Instead, they made a full hierarchy of objects. > > IMO this is plain bad. I understand the attempt to decouple, but now that means if I want to create a new theme, I need to create my theme object with colors I want and then also I need to create an undetermined number of classes (at least one for each tool, but there is also a hierarchy of things there)â¦ anyway, this DOES NOT scale. Because each tool will have to have a âtheme classâ for each existing themeâ¦ > How themes (skins, bah) work in all word is to have a color palette and then tools takes them (they can âplayâ a bit with this palette, but need to always respect the palette). > > Then, I will commit a SLICE modifying the âthemerâ classes to take colors from the current theme (instead of have them hardcoded). > But of course, how theme work now is not good because they mix âthemeâ (how they display) and âskinâ (color palette). I will also extract the palette to where should have always been (some kind of a style sheet object)â¦ who also should have been editable in settings so people can tweak their configuration. > > I didnât wanted to touch this before, because this will supposedly change with brick, but honestly this will not be ready for Pharo 6 and this is annoying (also, I want to publish my theme and I do not want to add overrides all around :P) > > cheers, > Esteban > > > <Screen Shot 2016-08-01 at 11.00.15.png> -- www.tudorgirba.com www.feenk.com "Innovation comes in the least expected form. That is, if it is expected, it already happened."

Aug. 4, 2016

Re: [Pharo-dev] [ANN] MatchTool

by Nicolai Hess

2016-08-04 11:38 GMT+02:00 Nicolai Hess <nicolaihess(a)gmail.com>: > Hey Uko, > > this pattern for a message sent: > > `@msg:`@args > > can match message sends with or without arguments, so it matches both > > 1 squared. > and > 1 raisedTo:2 > > The problem is that the first match "1 squared" will give a DNU on the > right pane, as the argument var '@args is empty. > > And if you match a method, it can happen that the keys <-> values in the map are actually strings or text and not a pattern variable (-source--, -pragma-, and the pattern method selector). > > > 2016-08-04 10:23 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > >> Hi everyone! >> >> Iâm happy to announce a new tool that can help you to understand to the >> pattern code is working in match & rewrite rules. >> You can read more on my blogpost: http://blog.yuriy.ty >> mch.uk/2016/08/matchtool.html >> The tool is available for Pharo 6 from the catalog. >> >> >> Cheers! >> Uko >> > >

Aug. 4, 2016

Re: [Pharo-dev] [ANN] MatchTool

by Nicolai Hess

Hey Uko, this pattern for a message sent: `@msg:`@args can match message sends with or without arguments, so it matches both 1 squared. and 1 raisedTo:2 The problem is that the first match "1 squared" will give a DNU on the right pane, as the argument var '@args is empty. 2016-08-04 10:23 GMT+02:00 Yuriy Tymchuk <yuriy.tymchuk(a)me.com>: > Hi everyone! > > Iâm happy to announce a new tool that can help you to understand to the > pattern code is working in match & rewrite rules. > You can read more on my blogpost: http://blog.yuriy. > tymch.uk/2016/08/matchtool.html > The tool is available for Pharo 6 from the catalog. > > > Cheers! > Uko >

Aug. 4, 2016