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

Re: [Pharo-dev] Changing class template

by Thierry Goubier

Le 09/11/2015 01:33, Yuriy Tymchuk a Ã©crit : > >> On 08 Nov 2015, at 20:14, Thierry Goubier >> <thierry.goubier(a)gmail.com> wrote: >> >> Stef, >> >> I don't understand. I have never set a category in a class creation >> template for the last three years. >> >> When I teach using Pharo, I allways tell students to create a >> package, select the package in the browser and add a class there. >> >> Changing #category: for #package: (which is what the fix will be, I >> bet) is useless. > > Because what written there is not a package, itâs a package + tag. So > it would make sense to have > > â¦ package: âPacakgeNameâ tag: âTagNameâ Trying to make it simpler for new students, I see :( > > But what Iâd really enjoy is to have a dedicated UI there. Because we > really use class templates as templates. 90% of a time I just change > the Superclass, Class and instance variables. As I said. > And 9% more I also add > a tag to the package. What? You don't do a 'add a tag to a package' operation? You create tags by side effect of a new class creation? (Your numbers don't add up to 100%. What is the one percent left for then? ;)) > So why we cannot have a UI with text fields for > this values? Later it can be fancier e.g. classVariables are hidden > by default and can be expanded on demand or if the are defined (I > donât like explaining class vars to people and I donât like them from > design point of view). Then also superclass field can have > autocompletion only from the defined classes prioritizing the ones > from the same package. Instance variables can be converted to slots > really fast by lookup, etcâ¦ Look, you're making even more complex everytime. But you're welcome to try; such a GUI can be added, yes, especially behind the add Class menu item instead of reusing the full template. A wizard for class creation :) Note that on current Nautilus, if you use add Class in the menu, opening the menu will auto-select what is behind the mouse click. And the template is prefilled, which makes it a bit more complex to create a new clas on Object. > I mean, itâs nice that we can subclass by sending a message, but we > donât develop methods in a template like: > > compile: âmethodCodeâ classified: âprotocolNameâ I do. When the browser is broken, it's sometime the only way left :) Or editing Smalltalk code directly on github :) > So maybe we make use of special UI for classes instead of plain > code. Note that with smart suggestions, you can have both in the same apparently plain code. But think of your usage, and also of the other usage: just beginner, new student. And the last one will show you that our toolset is geared towards the power user. And this is not going to change anytime soon, to the contrary. Thierry

Nov. 9, 2015

Re: [Pharo-dev] Kind of RBRenameMethodRefactoring but for closures?

by Thierry Goubier

Hi Mariano, Le 09/11/2015 01:13, Mariano Martinez Peck a Ã©crit : > > > On Fri, Nov 6, 2015 at 1:59 PM, Mariano Martinez Peck > <marianopeck(a)gmail.com <mailto:marianopeck@gmail.com>> wrote: > ... > > Hi Thierry, > > I am trying to achieve a similar case like the one I commented in this > post but I am unable to find the way. > Previously I wanted to replace say the literal #oldSelector to > #newSelector. Now, I need to use regular expressions. I mean, I would > need to find matches of '*oldSelector*' and do the replace with > 'newSelector'. For example, the search may find > '*pre*oldSelector*post*' and I want it to be replaced by > '*pre*newSelector*post'. *And of course, I don't know in advance what > pre and post strings there could be. What you need to do there is to use a match block after the @selector `{:node | node selector matches: '.*oldSelector.*'} Which would mean that your patterns become: rewriter replace: '``@object `oldSelector {:node | node selector matches: '.*oldSelector.*'}' with: '``@object `newSelector {:node | node selector }'. Wait, not entirely sure. I think you need to add a dictionary in the block to give the with: argument the pre and post string. And I'm not sure about the regular expression above as well. I need to have access to the SmaCC code source, so I'll answer to you a bit later. > > Also..do you know where can I find some more info about RB? For example, > if I read this: > > rewriter > replace: '``@object ' , oldSeletor > with: '``@object ' , newSelector. > > Where can I read that ``@object means XXX .. ? There is a first level of explanation in the Pharo for the Enterprise book; but, yes the pattern language is fairly complex. Are you going to Smalltalks? John Brant is there and will give a talk on RB and SmaCC (two talks, I believe). Thierry > Thanks in advance! > > > > Or a cascade: a RBParseTreeSearcher which matches blocks; on > each block node you activate a rewriter. > > However, there is an issue in rewriting blocks contents, because > it supposes that the method defining the block is recompiled; > it's significantly harder to make changes to the code of live > blocks (change the bytescode itself? What if the block has > multiples instances?). > > Thierry > > > If not, I think my easiest path is to automatically compile > dummy/temporal classes/methods from the rules, perform the > refactor, then move source from methods to block closures, > and finally remove created classes. > > Any pointer is appreciated. > > best, > > -- > Mariano > http://marianopeck.wordpress.com > > > > > > -- > Mariano > http://marianopeck.wordpress.com > > > > > -- > Mariano > http://marianopeck.wordpress.com

Nov. 9, 2015

Re: [Pharo-dev] Changing class template

by Yuriy Tymchuk

> On 08 Nov 2015, at 20:14, Thierry Goubier <thierry.goubier(a)gmail.com> wrote: > > Stef, > > I don't understand. I have never set a category in a class creation template for the last three years. > > When I teach using Pharo, I allways tell students to create a package, select the package in the browser and add a class there. > > Changing #category: for #package: (which is what the fix will be, I bet) is useless. Because what written there is not a package, itâs a package + tag. So it would make sense to have â¦ package: âPacakgeNameâ tag: âTagNameâ But what Iâd really enjoy is to have a dedicated UI there. Because we really use class templates as templates. 90% of a time I just change the Superclass, Class and instance variables. And 9% more I also add a tag to the package. So why we cannot have a UI with text fields for this values? Later it can be fancier e.g. classVariables are hidden by default and can be expanded on demand or if the are defined (I donât like explaining class vars to people and I donât like them from design point of view). Then also superclass field can have autocompletion only from the defined classes prioritizing the ones from the same package. Instance variables can be converted to slots really fast by lookup, etcâ¦ I mean, itâs nice that we can subclass by sending a message, but we donât develop methods in a template like: compile: âmethodCodeâ classified: âprotocolNameâ So maybe we make use of special UI for classes instead of plain code. Uko > > Thierry > > Le 08/11/2015 19:55, stepharo a Ã©crit : >> https://pharo.fogbugz.com/f/cases/16952/Change-class-template-creation >> >> Stef >> >> Hi guys >> >> I think that not enough of us are teaching... we are so used to jump around >> "DETAILS" that we do not have a clue how newcomers see our system. >> >> For example I hate that I have to explain that we should enter a package >> name as argument of a category???? >> >> Object subclass: #NameOfSubclass >> instanceVariableNames: ââ >> classVariableNames: ââ >> category: âPackageNameâ >> >> >> I will change the template because I do not want to have to explain that >> and that our Mooc refers to such crap. And you will have the right to >> complain but in that case >> I will tell you: "give a lecture and come back to" >> >> We are trapped in our way of thinking and we are trapped in the glitches >> of our system >> >> We should not accept glitches and we should kill them. >> >> Stef > > >

Nov. 9, 2015

Re: [Pharo-dev] Kind of RBRenameMethodRefactoring but for closures?

by Mariano Martinez Peck

On Fri, Nov 6, 2015 at 1:59 PM, Mariano Martinez Peck <marianopeck(a)gmail.com > wrote: > > > On Fri, Nov 6, 2015 at 12:33 PM, Thierry Goubier < > thierry.goubier(a)gmail.com> wrote: > >> >> >> 2015-11-06 16:17 GMT+01:00 Mariano Martinez Peck <marianopeck(a)gmail.com>: >> >>> Hi guys, >>> >>> I have a very large kind of "rule engine" in which rules are written in >>> smalltalk. These rules are saved as domain objects (imagine a rule kind of >>> object) which end up having a closure. The code of those closure most of >>> the time receives an argument and send messages to it. >>> I want to add automatic method rename for rules. Let's say i have plenty >>> of rules sending the message (rule) #price and now I want to refactor all >>> senders to actually send #lastPrice. >>> >>> I am taking a look to RBRenameMethodRefactoring and friends. But I >>> wonder if there is something specifically for managing blocks rather than >>> methods/classes? >>> >> >> Just write a RBParseTreeRewriter rule with specific elements to only >> activate inside blocks. >> >> > Thanks Thierry, that helped me to get started. Note that all my closures > are clean (#isClean answering true, that is, they are all self contained), > and I also have the 'string' of them. So I have no problem to just re > generate them :) > > So this kind of worked: > > *| rewriter tree oldSeletor newSelector |* > *"next: build the method-like string out of our closure strings"* > *tree := RBParser parseMethod: 'DoIt ^ [:proxy | * > * proxy at: #oldSelector.* > * proxy oldSelector. * > * proxy oldSelectorAnotherMethod.* > * proxy do: ''oldSelectorAndSomething''.* > * "a comment with #oldSelector "* > * ]'.* > *oldSeletor := #oldSelector. * > *newSelector := #newSelector.* > > *oldSeletor numArgs > 0 ifTrue: [ self error: 'For the moment we only > support renaming selectors without arguments'].* > *rewriter := RBParseTreeRewriter replaceLiteral: oldSeletor with: > newSelector. * > *rewriter * > * replace: '``@object ' , oldSeletor* > * with: '``@object ' , newSelector.* > > *rewriter executeTree: tree. * > *tree newSource* > > > And that answers: > > *'DoIt ^ [:proxy | * > * proxy at: #newSelector.* > * proxy newSelector. * > * proxy oldSelectorAnotherMethod.* > * proxy do: ''oldSelectorAndSomething''.* > * "a comment with #oldSelector "* > * ]'* > > > Hi Thierry, I am trying to achieve a similar case like the one I commented in this post but I am unable to find the way. Previously I wanted to replace say the literal #oldSelector to #newSelector. Now, I need to use regular expressions. I mean, I would need to find matches of '*oldSelector*' and do the replace with 'newSelector'. For example, the search may find '*pre*oldSelector*post*' and I want it to be replaced by '*pre*newSelector*post'. *And of course, I don't know in advance what pre and post strings there could be. Also..do you know where can I find some more info about RB? For example, if I read this: rewriter replace: '``@object ' , oldSeletor with: '``@object ' , newSelector. Where can I read that ``@object means XXX .. ? Thanks in advance! > Or a cascade: a RBParseTreeSearcher which matches blocks; on each block >> node you activate a rewriter. >> >> However, there is an issue in rewriting blocks contents, because it >> supposes that the method defining the block is recompiled; it's >> significantly harder to make changes to the code of live blocks (change the >> bytescode itself? What if the block has multiples instances?). >> >> Thierry >> >> >> >>> >>> If not, I think my easiest path is to automatically compile >>> dummy/temporal classes/methods from the rules, perform the refactor, then >>> move source from methods to block closures, and finally remove created >>> classes. >>> >>> Any pointer is appreciated. >>> >>> best, >>> >>> -- >>> Mariano >>> http://marianopeck.wordpress.com >>> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > -- Mariano http://marianopeck.wordpress.com

Nov. 9, 2015

Re: [Pharo-dev] Ubuntu fullscreen problems

by Nicolai Hess

2015-10-28 20:14 GMT+01:00 J.F. Rick <self(a)je77.com>: > Cool. I guess if there is a bug report on squeak then there is no reason > to create one on pharo. If you need someone to test a solution on Ubuntu > 15.10, let me know. > Hi Jeff, can you check this version, it works for me on DISTRIB_ID="elementary OS" DISTRIB_RELEASE=0.3.1 DISTRIB_CODENAME=freya DISTRIB_DESCRIPTION="elementary OS Freya" https://drive.google.com/file/d/0B8yEahnuIem2VGJlejJpUjZfZHc/view?usp=shari… it should work on Ubuntu, but I don|t have Ubuntu 15 installed. > > On Wed, Oct 28, 2015 at 11:21 AM Nicolai Hess <nicolaihess(a)gmail.com> > wrote: > >> 2015-10-28 15:35 GMT+01:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: >> >>> I think there must be some incompatibility between Pharo and the host >>> window manager/desktop environment. >>> >>> On Debian/dwm (I am using Ubuntu VM) I can reproduce (1), but not (2). >>> >>> There is however interesting behavior... if I try to switch desktop >>> while in fullscreen it doesn't switch, however once I switch back to >>> non-fullscreen, suddenly I jump to the other desktop, as if the keyboard >>> shortcut for the switch got buffered somewhere... >>> >>> Opening a issue in FogzBugz is a good idea so it doesn't get forgotten. >>> >>> Peter >>> >>> On Wed, Oct 28, 2015 at 3:15 PM, J.F. Rick <self(a)je77.com> wrote: >>> >>>> Hi everybody, >>>> >>>> I just upgraded to Ubuntu 15.10 and am using Unity User Interface. I >>>> want Pharo to use the full screen (i.e., above the menu bar and launcher). >>>> Inside Pharo, I can choose "Toggle full screen mode". This works to some >>>> extent but has some problems: >>>> >>>> (1) I can no longer switch applications or desktops (i.e., pager). So >>>> it stops me doing work where I move between Pharo and a browser. This may >>>> be expected functionality. >>>> >>>> (2) More problematically, when I try to switch out of full screen mode >>>> by choosing "Toggle full screen mode", the Pharo interface completely >>>> disappears (just a giant gray area) and no mouse or keyboard events seem to >>>> register. I have to use command line to kill it. In good news, I can use >>>> "save and quit" instead and relaunching it just has it in maximum mode >>>> (full screen but launcher and menu bar are visible). I can then toggle full >>>> screen mode twice to get back to full screen. >>>> >>>> I searched for this on FogBugz but found nothing. Is there a >>>> workaround? This seems like a VM issue. Is there a newer VM that fixes >>>> this? I just used the most recent one on the Pharo 4.0 download page. >>>> >>>> If nobody has a fix, I'll open a case on FogBugz. This isn't a large >>>> problem but it would be nice to have this >>>> >>> >> It is a know problem (with possible fixes) >> (http://bugs.squeak.org/view.php?id=7812) >> You can not switch back from fullscreen on a linux 64-bit system ( >> http://bugs.squeak.org/view.php?id=7833) (maybe not only 32bit issue, >> but just the more recent windowmanager) >> >> >> >>> >>>> Cheers, >>>> >>>> Jeff >>>> >>> >>> >>

Nov. 8, 2015

Re: [Pharo-dev] Cannot use command-P in inspector in the debugger

by Nicolai Hess

2015-11-08 22:33 GMT+01:00 Alain Plantec via Pharo-dev < pharo-dev(a)lists.pharo.org>: > > > ---------- Weitergeleitete Nachricht ---------- > From: Alain Plantec <alain.plantec(a)yahoo.com> > To: Pharo Development List <pharo-dev(a)lists.pharo.org> > Cc: > Date: Sun, 8 Nov 2015 22:32:17 +0100 > Subject: Re: [Pharo-dev] Cannot use command-P in inspector in the debugger > I guess it is because of the default text mode. The smalltalk code mode > should be set for these text areas. > Alain > AFAIK this was done on purpose https://pharo.fogbugz.com/f/cases/16333/no-syntax-highlighting-in-TextModel… "... I also put newText for the two bottom boxes in debugger since now newCode is fixed for highlighting, we do not want to have highlighted text for these text areas..." > > > On 08 Nov 2015, at 19:54, stepharo <stepharo(a)free.fr> wrote: > > > > Hi guys > > > > I would like to know if I'm the only one to do not have anymore the > command-P in inspector in the debugger. > > > > Stef > > > > > >

Nov. 8, 2015

Re: [Pharo-dev] Changing class template

by Thierry Goubier

Le 08/11/2015 20:59, stepharo a Ã©crit : > So this is good your super students will not have to worry and my super > stupid will be happy. No, this is that you need to change deeper, no just complain about the template, to help your and my students. But it's good to see you notice :) Thierry

Nov. 8, 2015

Re: [Pharo-dev] Cannot use command-P in inspector in the debugger

by Alain Plantec

I guess it is because of the default text mode. The smalltalk code mode should be set for these text areas. Alain > On 08 Nov 2015, at 19:54, stepharo <stepharo(a)free.fr> wrote: > > Hi guys > > I would like to know if I'm the only one to do not have anymore the command-P in inspector in the debugger. > > Stef >

Nov. 8, 2015

Re: [Pharo-dev] How to integrate change on class Point

by stepharo

There is a trick Tx henrik DangerousClassNotifier disable :) Le 8/11/15 21:32, stepharo a Ã©crit : > Hi > > I would like to remove some dusts in the class Point. > No decent class comments, cleaning typo in organisation and cleaning > some method comments. > In fact I should do a real pass. Now I published > https://pharo.fogbugz.com/f/cases/16953/Clean-Point-Reciprocal-comment-and-… > > When I merged the slice I get a classBuilder warning and it means that > my changes cannot be loaded and it fails of course. > I do not like this classBuilder warning in fact. I can break Pharo in > one line of code even with it. So may be in pharo dev mode we should > not get it. > So what is the way to do it properly. > > Stef > >

Nov. 8, 2015

How to integrate change on class Point

by stepharo

Hi I would like to remove some dusts in the class Point. No decent class comments, cleaning typo in organisation and cleaning some method comments. In fact I should do a real pass. Now I published https://pharo.fogbugz.com/f/cases/16953/Clean-Point-Reciprocal-comment-and-… When I merged the slice I get a classBuilder warning and it means that my changes cannot be loaded and it fails of course. I do not like this classBuilder warning in fact. I can break Pharo in one line of code even with it. So may be in pharo dev mode we should not get it. So what is the way to do it properly. Stef

Nov. 8, 2015