March 2017 - Pharo-users - lists.pharo.org

Re: [Pharo-users] looking for tools to manually select ast nodes for metalinks

by Guillermo Polito

Hi Steven, Yes there is! It's called "Suggestions". Suggestions is a project started some years ago by Gisela Decuzzi as an intern of RMoD. The main idea is to propose actions based on the AST corresponding to the cursor. This means that given the position of the cursor, suggestions already: - parses the code - selects the corresponding node - provides possible actions for the node. E.g., - refactorings - code navigation - breakpoints and watchpoints (through Metalinks) Check the SmartSuggestions package. Guille On Mon, Mar 20, 2017 at 1:12 AM, Ben Coman <btc(a)openinworld.com> wrote: > On Mon, Mar 20, 2017 at 4:06 AM, Steven Costiou <steven.costiou(a)kloum.io> > wrote: > > Hi, > > > > i would like a way to define metalinks at debug time, by "visually" > > selecting ast nodes in the debugger. For example i would like to see a > > method that i am debugging and by a clic on the source code it would > select > > the associated ast node and allow me to put a metalink right there. > > > > - does that exist ? > > This might get you close... > > Debug into... > 1 printString > > In Variables tab, select "thisContext" > > In Raw tab, select method > > In AST tab, select your node. > > From there on, I don't know. Please report back if you get something to > work. > > > > > > - if not, does a tool to display or to navigate through metalinks already > > exists ? > > I don't think so. Pharo 6 has only the first step of having the basic > underlying system implemented. > > cheers -ben > > > > > - if not any, can somebody point me to documentation and/or ressources to > > extend the debugger so i can try to build it ? (i've already seen the > spec > > book to build ui but i want to see what is possible with the debugger) > >

March 20, 2017

Re: Magritte extension

by Asbath Sama biyalou

Thanks Mariano for the ideas. I will put them into practice. Then All I have to do is to extends magritte classes to customize them. On 18/03/2017 18:40, Mariano Martinez Peck wrote: > Hi Asbath, > > Some answers below. But a general comment is that the typical case to > customize magritte is by subclassing and then somehow use your own > subclasses instead of magritte ones. > > On Fri, Mar 17, 2017 at 3:54 AM, Asbath Sama biyalou > <asamabiyalou(a)yahoo.com <mailto:asamabiyalou@yahoo.com>> wrote: > > Hello. > > I am using Magritte to generate reports for a pharo class. I want to > customize generated components in order to have a better design. > > My class is Match > > Object subclass: #Match > instanceVariableNames: 'date_match hour_match status actions > stadium > comments teams goals1 goals2 competition' > classVariableNames: '' > category: MyProject-Entity' > > > Descriptions for some variables. > > Stadium is also a Class. > > Match>>descriptionStadium > <magritteDescription> > ^ MASingleOptionDescription new > label: 'Stadium'; > priority: 305; > accessor: #stadium; > options: Team allStadiumsName; > componentClass: TBSMagritteSelectListComponent; > beRequired; > yourself > > > Match>>descriptionTeams > <magritteDescription> > ^ MAMultipleOptionDescription new > label: 'Teams'; > priority: 805; > accessor: #teams; > options: Team allTeamsName; > componentClass: MAMultiselectListComponent; > yourself > > > The generated component in the form is not very pretty. I want to have > multiple checkbox. > > > > In my case, I have customized ALL the components I use for Magritte. > That is, I have my own Fa version (Fa is my package prefix). So I have > FaMAMultiselectListComponent subclass of MAMultiselectListComponent. > I have FaTBSMagritteSelectListComponent, subclass of > TBSMagritteSelectListComponent , etc... so basically, you subclass and > override the parent methods you want. Most common methods you need to > override are renderEditorOn: html or renderViewerOn: html etc...but > that depends on WHAT you want to change and in WHICH component. Note > they are all subclasses of MADescriptionComponent. > > You can also set your own properties in the magritte so that you can > read them at your component level. For example, above I could say: > > Match>>descriptionTeams > <magritteDescription> > ^ MAMultipleOptionDescription new > label: 'Teams'; > priority: 805; > accessor: #teams; > options: Team allTeamsName; > propertyAt: 'showInMultipleCheckboxs' put: true; > componentClass: FaMAMultiselectListComponent; > yourself > > > Then in the rendering code of your subclass > FaMAMultiselectListComponent you can do: > > (self magritteDescription propertyAt: 'showInMultipleCheckboxs') ifTrue: [ > self renderAsMultiCheckboxsOn: html... > ] ifFalse: [ > ... > ] > > Of course, you can even define the accessors for > #showInMultipleCheckboxs as extension methods in MADescription > > > To avoid having to define FaMAMultiselectListComponent for each > MAMultipleOptionDescription .. well, there are many ways. But I guess > that is for a later topic. Ask me if you want this. > > > > > Match>>descriptionStatus > <magritteDescription> > ^ MASingleOptionDescription new > label: 'Status'; > priority: 505; > accessor: #status; > options: #('Pas en cours' 'En Cours' 'Mi-temps' 'TerminÃ©'); > componentClass: TBSMagritteSelectListComponent; > yourself > > > For the report I use the class SEMatchReport > > TBSMagritteReport subclass: #SEMatchReport > instanceVariableNames: 'report' > classVariableNames: '' > category: 'MyProject-Components' > > > SEMatchReport class>>from > | report matchs commandColumn | > matchs := Match selectAll. > report:= self rows: matchs description: (self > filteredDescriptionsFrom: matchs anyOne). > > commandColumn := MACommandColumn new. > > (SEMatchReport new session isSimpleAdmin) > ifTrue: [ > report addColumn: (commandColumn > addCommandOn: report selector: #editMatch: text: > 'Modifier'; > yourself; > addCommandOn: report selector: #addAction: text: 'Ajouter > une action'; yourself ) ] > ifFalse: [ > report addColumn: (commandColumn > addCommandOn: report selector: #editMatch: text: > 'Modifier'; > yourself; > addCommandOn: report selector: #deleteMatch: text: > 'Supprimer'; yourself; > addCommandOn: report selector: #addAction: text: 'Ajouter > une action'; yourself ) ]. > > ^ report > > I want to put some bootstrapp icons near commandColumn actions. like > pencil or delete on 'Supprimer'. > > > > To do this, again, subclass MACommandColumn, > override renderCellContent:on: and use your particular subclass. > > > > > SEMatchReport class>>filteredDescriptionsFrom: aMatch > ^ aMatch magritteDescription select: [ :each | #(date_match > hour_match stadium goals1 goals2 teams) > includes: each accessor selector ] > > I notice that on the generated report on column stadium we have > aStadium. We don't have the value (the name). I don't know how to > mention it in the filtered descriptions. > > > > That's weird. I don't know. > > > > Change the color of lines in the report, etc. All that things. > > > In this case I don't use the magritte row/even css classes. > > In my case, I have a subclass of MAReport (I guess you can subclass > from the Bootstrap one) and changed the table rendering to use: > > table > beHover; > beBordered; > beCondensed; > beStriped; > > etc... so I let colors to Bootstrap / CSS. > Cheers, > > > > Sorry for the bad english. > > Thanks. > > Asbath > > > > > -- > Mariano > http://marianopeck.wordpress.com Cheers, Asbath

March 20, 2017

OSProcess or OSSubprocess?

by HernÃ¡n Morales Durand

Hi guys, I need to monitor Unix command execution inside the image. The commands use heavy computation so they usually report progress in the terminal. Are OSProcess or OSSubprocess ready to do in-image monitoring so I can watch the same terminal output in the Transcript updating for example every 10 seconds? Particularly for OSProcess I couldn't find any method to fetch partial output. Cheers, HernÃ¡n

March 20, 2017

TextInspectIt missing in Pharo 6

by Alistair Grant

Hi All, TextInspectit and TextDoIt>>rubActOnClick:for:in:editor:, which are part of the Text-Core package, are present in Pharo 5 but not in Pharo 6 (60442). All the other classes in Text-Core appear to be present (I haven't checked every method). Is this intentional, and if so, what is the replacement? Thanks very much, Alistair

March 20, 2017

Re: [Pharo-users] looking for tools to manually select ast nodes for metalinks

by Ben Coman

On Mon, Mar 20, 2017 at 4:06 AM, Steven Costiou <steven.costiou(a)kloum.io> wrote: > Hi, > > i would like a way to define metalinks at debug time, by "visually" > selecting ast nodes in the debugger. For example i would like to see a > method that i am debugging and by a clic on the source code it would select > the associated ast node and allow me to put a metalink right there. > > - does that exist ? This might get you close... Debug into... 1 printString In Variables tab, select "thisContext" In Raw tab, select method In AST tab, select your node. >From there on, I don't know. Please report back if you get something to work. > > - if not, does a tool to display or to navigate through metalinks already > exists ? I don't think so. Pharo 6 has only the first step of having the basic underlying system implemented. cheers -ben > > - if not any, can somebody point me to documentation and/or ressources to > extend the debugger so i can try to build it ? (i've already seen the spec > book to build ui but i want to see what is possible with the debugger)

March 20, 2017

looking for tools to manually select ast nodes for metalinks

by Steven Costiou

Hi, i would like a way to define metalinks at debug time, by "visually" selecting ast nodes in the debugger. For example i would like to see a method that i am debugging and by a clic on the source code it would select the associated ast node and allow me to put a metalink right there. - does that exist ? - if not, does a tool to display or to navigate through metalinks already exists ? - if not any, can somebody point me to documentation and/or ressources to extend the debugger so i can try to build it ? (i've already seen the spec book to build ui but i want to see what is possible with the debugger) Thanks, Steven.

March 19, 2017

Class versions

by Norbert Hartl

How far are we to support multiple versions of the same class in an image? Are there existing approaches? Norbert Von meinem iPad gesendet

March 19, 2017

Re: [Pharo-users] Magritte extension

by Norbert Hartl

I never managed to take a look at QCMagritte but it sounds as an extension. Why was it never integrated? Norbert Von meinem iPad gesendet > Am 19.03.2017 um 10:06 schrieb Stephan Eggermont <stephan(a)stack.nl>: > >> On 18/03/17 18:40, Mariano Martinez Peck wrote: >> Some answers below. But a general comment is that the typical case to >> customize magritte is by subclassing and then somehow use your own >> subclasses instead of magritte ones. > > Well, there are lots of ways to customize magritte. So many actually, that it is definitely non-trivial to decide where to extend what. For your first experiments with extending magritte, just subclassing is definitely the way to go. You need a way to understand how the different parts in magritte interact, and the easiest way is to change something and see what it does. > > In QCMagritte we've gone much farther. Some problems (access control, translation) are much easier solved by modifying the visitor used to render the html. By chaining multiple visitors, it becomes easy to translate all labels and help-texts without polluting the magritte descriptions or the domain objects. The same goes for access control. > > Stephan > > > >

March 19, 2017

Re: [Pharo-users] Magritte extension

by Stephan Eggermont

On 18/03/17 18:40, Mariano Martinez Peck wrote: > Some answers below. But a general comment is that the typical case to > customize magritte is by subclassing and then somehow use your own > subclasses instead of magritte ones. Well, there are lots of ways to customize magritte. So many actually, that it is definitely non-trivial to decide where to extend what. For your first experiments with extending magritte, just subclassing is definitely the way to go. You need a way to understand how the different parts in magritte interact, and the easiest way is to change something and see what it does. In QCMagritte we've gone much farther. Some problems (access control, translation) are much easier solved by modifying the visitor used to render the html. By chaining multiple visitors, it becomes easy to translate all labels and help-texts without polluting the magritte descriptions or the domain objects. The same goes for access control. Stephan

March 19, 2017

Re: [Pharo-users] Magritte extension

by Mariano Martinez Peck

Hi Asbath, Some answers below. But a general comment is that the typical case to customize magritte is by subclassing and then somehow use your own subclasses instead of magritte ones. On Fri, Mar 17, 2017 at 3:54 AM, Asbath Sama biyalou <asamabiyalou(a)yahoo.com > wrote: > Hello. > > I am using Magritte to generate reports for a pharo class. I want to > customize generated components in order to have a better design. > > My class is Match > > Object subclass: #Match > instanceVariableNames: 'date_match hour_match status actions stadium > comments teams goals1 goals2 competition' > classVariableNames: '' > category: MyProject-Entity' > > > Descriptions for some variables. > > Stadium is also a Class. > > Match>>descriptionStadium > <magritteDescription> > ^ MASingleOptionDescription new > label: 'Stadium'; > priority: 305; > accessor: #stadium; > options: Team allStadiumsName; > componentClass: TBSMagritteSelectListComponent; > beRequired; > yourself > > > Match>>descriptionTeams > <magritteDescription> > ^ MAMultipleOptionDescription new > label: 'Teams'; > priority: 805; > accessor: #teams; > options: Team allTeamsName; > componentClass: MAMultiselectListComponent; > yourself > > > The generated component in the form is not very pretty. I want to have > multiple checkbox. > In my case, I have customized ALL the components I use for Magritte. That is, I have my own Fa version (Fa is my package prefix). So I have FaMAMultiselectListComponent subclass of MAMultiselectListComponent. I have FaTBSMagritteSelectListComponent, subclass of TBSMagritteSelectListComponent , etc... so basically, you subclass and override the parent methods you want. Most common methods you need to override are renderEditorOn: html or renderViewerOn: html etc...but that depends on WHAT you want to change and in WHICH component. Note they are all subclasses of MADescriptionComponent. You can also set your own properties in the magritte so that you can read them at your component level. For example, above I could say: Match>>descriptionTeams <magritteDescription> ^ MAMultipleOptionDescription new label: 'Teams'; priority: 805; accessor: #teams; options: Team allTeamsName; propertyAt: 'showInMultipleCheckboxs' put: true; componentClass: FaMAMultiselectListComponent; yourself Then in the rendering code of your subclass FaMAMultiselectListComponent you can do: (self magritteDescription propertyAt: 'showInMultipleCheckboxs') ifTrue: [ self renderAsMultiCheckboxsOn: html... ] ifFalse: [ ... ] Of course, you can even define the accessors for #showInMultipleCheckboxs as extension methods in MADescription To avoid having to define FaMAMultiselectListComponent for each MAMultipleOptionDescription .. well, there are many ways. But I guess that is for a later topic. Ask me if you want this. > > Match>>descriptionStatus > <magritteDescription> > ^ MASingleOptionDescription new > label: 'Status'; > priority: 505; > accessor: #status; > options: #('Pas en cours' 'En Cours' 'Mi-temps' 'TerminÃ©'); > componentClass: TBSMagritteSelectListComponent; > yourself > > > For the report I use the class SEMatchReport > > TBSMagritteReport subclass: #SEMatchReport > instanceVariableNames: 'report' > classVariableNames: '' > category: 'MyProject-Components' > > > SEMatchReport class>>from > | report matchs commandColumn | > matchs := Match selectAll. > report:= self rows: matchs description: (self > filteredDescriptionsFrom: matchs anyOne). > > commandColumn := MACommandColumn new. > > (SEMatchReport new session isSimpleAdmin) > ifTrue: [ > report addColumn: (commandColumn > addCommandOn: report selector: #editMatch: text: 'Modifier'; > yourself; > addCommandOn: report selector: #addAction: text: 'Ajouter > une action'; yourself ) ] > ifFalse: [ > report addColumn: (commandColumn > addCommandOn: report selector: #editMatch: text: 'Modifier'; > yourself; > addCommandOn: report selector: #deleteMatch: text: > 'Supprimer'; yourself; > addCommandOn: report selector: #addAction: text: 'Ajouter > une action'; yourself ) ]. > > ^ report > > I want to put some bootstrapp icons near commandColumn actions. like > pencil or delete on 'Supprimer'. > > To do this, again, subclass MACommandColumn, override renderCellContent:on: and use your particular subclass. > > SEMatchReport class>>filteredDescriptionsFrom: aMatch > ^ aMatch magritteDescription select: [ :each | #(date_match > hour_match stadium goals1 goals2 teams) > includes: each accessor selector ] > > I notice that on the generated report on column stadium we have > aStadium. We don't have the value (the name). I don't know how to > mention it in the filtered descriptions. > That's weird. I don't know. > > Change the color of lines in the report, etc. All that things. > > In this case I don't use the magritte row/even css classes. In my case, I have a subclass of MAReport (I guess you can subclass from the Bootstrap one) and changed the table rendering to use: table beHover; beBordered; beCondensed; beStriped; etc... so I let colors to Bootstrap / CSS. Cheers, > Sorry for the bad english. > > Thanks. > > Asbath > > -- Mariano http://marianopeck.wordpress.com

March 18, 2017