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

Question about GLORP class models

by Alejandro Infante

Hi guys! Iâm trying to use GLORP and Iâm having problems defining the class model for a class which has an instance variable which is a collection of instances of two different classes: I have 3 classes named: { Section . Question . QuestionGroup } and I have problems for specifying the glorp class model for Section. Object subclass: #Section instanceVariableNames: âquestions ...' classVariableNames: '' The thing is that #questions instance variable is a collection of Question AND QuestionGroup. They have polymorphic behavior, but they have not a common superclass (besides Object). How does my class model should look like? classModelForSection: aClassModel ... aClassModel newAttributeNamed: #questions collectionOf: ****?. Thanks for the help! Cheers, Alejandro

March 29, 2018

Re: [Pharo-users] Zoom x-axis in RTGrapher?

by Alistair Grant

Hi Alexandre, On 29 March 2018 at 15:07, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Easy. > > You can add a reset button: > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > v := RTView new. > b := [ :someClasses | > g := RTGrapher new. > g view: v. > ds := RTData new. > ds points: someClasses. > ds y: [ :cls | cls numberOfMethods ]. > ds x: [ :cls | cls numberOfLinesOfCode ]. > g add: ds. > > g addDecorator: (RTRangeSelector new callback: [ :es | > | classesToZoomIn | > > classesToZoomIn := es collect: #model. > v cleanAll. > b value: classesToZoomIn > ]). > g build. > v addMenu: 'Reset' callback: [ v cleanAll. b value: RTShape withAllSubclasses ]. > ]. > > b value: RTShape withAllSubclasses. > v > -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Thanks! All working now... Cheers, Alistair

March 29, 2018

Re: [Pharo-users] RTDoubleScrollBar is not rendered properly in html

by Alexandre Bergel

Exactly Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 29, 2018, at 11:24 AM, Andrei Stebakov <lispercat(a)gmail.com> wrote: > > Thanks, Alexandre > Looks like RTResizeableViewContextInteraction has no effect for the tree that goes beyond the page. > On the other hand RTEmptyViewContextInteraction makes the tree that used to be shrunk to fit in the page go beyond the page, as expected I guess. > So the RTResizeableViewContextInteraction doesn't work as expected (since the expectation is to fit in the page as I understand) > > On Wed, Mar 28, 2018, 13:56 Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >> I also stumbled upon RTHorizontalTreeLayout that works much better in terms of having more compact representation. >> What I found out though is that when I inspect the view sometimes it displays all the ellipses with their specified sizes and sometimes it shrinks the view to fit in the viewable area. Can't put my finger on what triggers the view be rendered with normal sized (doesn't fit the page) vs zoomed out (fits the page) > > Yes, you can have a look at Roassal2GT-Glamour-Roassal-Interaction > > Here are some examples. The default behavior is obtained by: > -=-=-=-=-=-=-=-=-= > b := RTMondrian new. > b nodes: (1 to: 100). > b layout grid. > b view @ RTResizeableViewContextInteraction. > b > -=-=-=-=-=-=-=-=-= > > If you wish to not have any resize, then you can do: > -=-=-=-=-=-=-=-=-= > b := RTMondrian new. > b nodes: (1 to: 100). > b layout grid. > b view @ RTEmptyViewContextInteraction. > b > -=-=-=-=-=-=-=-=-= > > The code is not clean at all. This is due to the limitation of GTInspector. > Help is welcome on that front! > > Alexandre > >> >> On Tue, Mar 27, 2018, 23:21 Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>> Alexandre, is there a way to display RTTreeLayout so that it would try to fit elements in a more vertical fashion. >>> Let's say even if the parent node has 8 children it would try to arrange them not in one long horizontal line (which depending on the width of elements can be really wide), >>> but spread them more vertically, so they would be viewable on one page. >>> Or maybe I need to try another layout to reach that goal? >> >> There is the horizontal tree layout that you may want to try. >> >> -=-=-=-=-=-=-=-= >> b := RTMondrian new. >> b shape circle. >> b nodes: Collection withAllSubclasses. >> b edges connectFrom: #superclass. >> b normalizer normalizeSize: #numberOfMethods; normalizeColor: #numberOfLinesOfCode. >> b layout horizontalTree. >> b >> -=-=-=-=-=-=-=-= >> >> >> >> Does it help? >> >> Cheers, >> Alexandre >> >>> On Fri, Mar 23, 2018 at 8:15 PM, Alexandre Bergel <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>> > Thanks, Alexandre, it works! >>> > Also since I use RTView and RTEdgeBuilder I can use >>> > view @ RTDraggableView to achieve the âdraggability" >>> >>> Yes! Glad to hear the problem is solved! >>> >>> Alexandre >>> >>> > >>> > On Mar 22, 2018 14:01, "Alexandre Bergel" <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>> > I see. >>> > Do you know you can drag and drop the background to scroll? >>> > >>> > You can also make the view zoomable, using the mouse wheel. >>> > >>> > Try this: >>> > -=-=-=-=-=-=-=-=-= >>> > b := RTMondrian new. >>> > b nodes: (RTObject withAllSubclasses). >>> > b edges connectFrom: #superclass. >>> > b layout radial. >>> > b build. >>> > >>> > b view @ RTZoomableView. >>> > RTHTML5Exporter new >>> > directoryPathname: '/tmp'; >>> > export: b view. >>> > >>> > b view >>> > -=-=-=-=-=-=-=-=-= >>> > >>> > Alexandre >>> > -- >>> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> > Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >>> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> > >>> > >>> > >>> >> On Mar 22, 2018, at 1:40 PM, Andrei Stebakov <lispercat(a)gmail.com <mailto:lispercat@gmail.com>> wrote: >>> >> >>> >> Hi Alexandre >>> >> >>> >> I don't see how I can do without the scroll bars in HTML since the node tree that I tender using RTTreeLayout has a big width and only 1/4 of it fits in one page view. >>> >> Since I am building a web service I rely on rendering and serving the view in HTML and without the scroll bars there is no way for me to view all elements of the model in Chrome. >>> >> >>> >> On Mar 22, 2018 11:50, "Alexandre Bergel" <alexandre.bergel(a)me.com <mailto:alexandre.bergel@me.com>> wrote: >>> >> Hi! >>> >> >>> >> Scroll bar are not exportable to HTML, as benefits in doing so are not really apparent. >>> >> What would be the ideal behavior? Will removing scrollbars when exporting to HTML sufficient for your need? >>> >> >>> >> Cheers, >>> >> Alexandre >>> >> -- >>> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> >> Alexandre Bergel http://www.bergel.eu <http://www.bergel.eu/> >>> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >> >>> >> >>> >> >>> >>> On Mar 22, 2018, at 11:20 AM, Andrei Stebakov <lispercat(a)gmail.com <mailto:lispercat@gmail.com>> wrote: >>> >>> >>> >>> When I do >>> >>> v @ RTDoubleScrollBar. >>> >>> and then export to HTML >>> >>> the bars are rendered in the middle of HTML page and they don't actually scroll. >>> >>> I checked in in Chrome and IE on windows. Could you guys take a look? >>> >> >>> > >>> >>> >>> >> >> <Screenshot 2018-03-28 00.19.54.png> >

March 29, 2018

Re: [Pharo-users] RTDoubleScrollBar is not rendered properly in html

by Andrei Stebakov

Thanks, Alexandre Looks like RTResizeableViewContextInteraction has no effect for the tree that goes beyond the page. On the other hand RTEmptyViewContextInteraction makes the tree that used to be shrunk to fit in the page go beyond the page, as expected I guess. So the RTResizeableViewContextInteraction doesn't work as expected (since the expectation is to fit in the page as I understand) On Wed, Mar 28, 2018, 13:56 Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > I also stumbled upon RTHorizontalTreeLayout that works much better in > terms of having more compact representation. > What I found out though is that when I inspect the view sometimes it > displays all the ellipses with their specified sizes and sometimes it > shrinks the view to fit in the viewable area. Can't put my finger on what > triggers the view be rendered with normal sized (doesn't fit the page) vs > zoomed out (fits the page) > > > Yes, you can have a look at Roassal2GT-Glamour-Roassal-Interaction > > Here are some examples. The default behavior is obtained by: > -=-=-=-=-=-=-=-=-= > b := RTMondrian new. > b nodes: (1 to: 100). > b layout grid. > b view @ RTResizeableViewContextInteraction. > b > -=-=-=-=-=-=-=-=-= > > If you wish to not have any resize, then you can do: > -=-=-=-=-=-=-=-=-= > b := RTMondrian new. > b nodes: (1 to: 100). > b layout grid. > b view @ RTEmptyViewContextInteraction. > b > -=-=-=-=-=-=-=-=-= > > The code is not clean at all. This is due to the limitation of > GTInspector. > Help is welcome on that front! > > Alexandre > > > On Tue, Mar 27, 2018, 23:21 Alexandre Bergel <alexandre.bergel(a)me.com> > wrote: > >> Alexandre, is there a way to display RTTreeLayout so that it would try to >> fit elements in a more vertical fashion. >> Let's say even if the parent node has 8 children it would try to arrange >> them not in one long horizontal line (which depending on the width >> of elements can be really wide), >> but spread them more vertically, so they would be viewable on one page. >> Or maybe I need to try another layout to reach that goal? >> >> >> There is the horizontal tree layout that you may want to try. >> >> -=-=-=-=-=-=-=-= >> b := RTMondrian new. >> b shape circle. >> b nodes: Collection withAllSubclasses. >> b edges connectFrom: #superclass. >> b normalizer normalizeSize: #numberOfMethods; normalizeColor: >> #numberOfLinesOfCode. >> b layout horizontalTree. >> b >> -=-=-=-=-=-=-=-= >> >> >> Does it help? >> >> Cheers, >> Alexandre >> >> On Fri, Mar 23, 2018 at 8:15 PM, Alexandre Bergel < >> alexandre.bergel(a)me.com> wrote: >> >> > Thanks, Alexandre, it works! >> > Also since I use RTView and RTEdgeBuilder I can use >> > view @ RTDraggableView to achieve the âdraggability" >> >> Yes! Glad to hear the problem is solved! >> >> Alexandre >> >> > >> > On Mar 22, 2018 14:01, "Alexandre Bergel" <alexandre.bergel(a)me.com> >> wrote: >> > I see. >> > Do you know you can drag and drop the background to scroll? >> > >> > You can also make the view zoomable, using the mouse wheel. >> > >> > Try this: >> > -=-=-=-=-=-=-=-=-= >> > b := RTMondrian new. >> > b nodes: (RTObject withAllSubclasses). >> > b edges connectFrom: #superclass. >> > b layout radial. >> > b build. >> > >> > b view @ RTZoomableView. >> > RTHTML5Exporter new >> > directoryPathname: '/tmp'; >> > export: b view. >> > >> > b view >> > -=-=-=-=-=-=-=-=-= >> > >> > Alexandre >> > -- >> > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> > Alexandre Bergel http://www.bergel.eu >> > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> > >> > >> > >> >> On Mar 22, 2018, at 1:40 PM, Andrei Stebakov <lispercat(a)gmail.com> >> wrote: >> >> >> >> Hi Alexandre >> >> >> >> I don't see how I can do without the scroll bars in HTML since the >> node tree that I tender using RTTreeLayout has a big width and only 1/4 of >> it fits in one page view. >> >> Since I am building a web service I rely on rendering and serving the >> view in HTML and without the scroll bars there is no way for me to view all >> elements of the model in Chrome. >> >> >> >> On Mar 22, 2018 11:50, "Alexandre Bergel" <alexandre.bergel(a)me.com> >> wrote: >> >> Hi! >> >> >> >> Scroll bar are not exportable to HTML, as benefits in doing so are not >> really apparent. >> >> What would be the ideal behavior? Will removing scrollbars when >> exporting to HTML sufficient for your need? >> >> >> >> Cheers, >> >> Alexandre >> >> -- >> >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> >> Alexandre Bergel http://www.bergel.eu >> >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> >> >> >>> On Mar 22, 2018, at 11:20 AM, Andrei Stebakov <lispercat(a)gmail.com> >> wrote: >> >>> >> >>> When I do >> >>> v @ RTDoubleScrollBar. >> >>> and then export to HTML >> >>> the bars are rendered in the middle of HTML page and they don't >> actually scroll. >> >>> I checked in in Chrome and IE on windows. Could you guys take a look? >> >> >> > >> >> >> >> >> <Screenshot 2018-03-28 00.19.54.png> > > >

March 29, 2018

Re: [Pharo-users] Zoom x-axis in RTGrapher?

by Alexandre Bergel

Easy. You can add a reset button: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= v := RTView new. b := [ :someClasses | g := RTGrapher new. g view: v. ds := RTData new. ds points: someClasses. ds y: [ :cls | cls numberOfMethods ]. ds x: [ :cls | cls numberOfLinesOfCode ]. g add: ds. g addDecorator: (RTRangeSelector new callback: [ :es | | classesToZoomIn | classesToZoomIn := es collect: #model. v cleanAll. b value: classesToZoomIn ]). g build. v addMenu: 'Reset' callback: [ v cleanAll. b value: RTShape withAllSubclasses ]. ]. b value: RTShape withAllSubclasses. v -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= If you wish to have a right click, you can do: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= v := RTView new. b := [ :someClasses | g := RTGrapher new. g view: v. ds := RTData new. ds points: someClasses. ds y: [ :cls | cls numberOfMethods ]. ds x: [ :cls | cls numberOfLinesOfCode ]. g add: ds. g addDecorator: (RTRangeSelector new callback: [ :es | | classesToZoomIn | classesToZoomIn := es collect: #model. v cleanAll. b value: classesToZoomIn ]). g build. v when: TRMouseRightClick do: [ v cleanAll. b value: RTShape withAllSubclasses. v signalUpdate ]. ]. b value: RTShape withAllSubclasses. v -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > On Mar 29, 2018, at 5:45 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: > > Hi Alexandre, > > Thanks! (more below) > > > On 28 March 2018 at 14:56, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: >> Hi Alistair! >> >> Yes, this is something we thought about some times ago. >> >> After updating Roassal, try this: >> -=-=-=-=-=-=-=-=-=-=-=-= >> v := RTView new. >> b := [ :someClasses | >> g := RTGrapher new. >> g view: v. >> ds := RTData new. >> ds points: someClasses. >> ds y: [ :cls | cls numberOfMethods ]. >> ds x: [ :cls | cls numberOfLinesOfCode ]. >> g add: ds. >> >> g addDecorator: (RTRangeSelector new callback: [:es | >> | classesToZoomIn | >> classesToZoomIn := es collect: #model. >> v cleanAll. >> b value: classesToZoomIn >> ]). >> g build. >> ]. >> >> b value: RTShape withAllSubclasses. >> v >> -=-=-=-=-=-=-=-=-=-=-=-= >> >> Let me know how it goes. > > Great, it's working fine! > > If you select an empty portion of the graph an error is raised - > "Error: No dataset has been added?". > > I solved this with the following change, which simply ignores empty > areas and notifies the user: > > > RTRangeSelector>>callbackWithSelectedElements > | selectedElements | > selectedElements := self elementsWithinTheSelection. > selectedElements ifEmpty: [ > UIManager default inform: 'Empty region selected, ignoring'. > ^self ]. > self evaluateCallBackWithElements: selectedElements > > > That was a quick hack, so there could well be a better solution. > > From what I can see, there isn't a way to zoom back out or scroll left > and right. > > I might modify RTRangeSelector so that a right click zooms out. I'll > have to think about scrolling a bit more. > > > Thanks again! > Alistair > > >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >>> On Mar 28, 2018, at 4:02 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >>> >>> Hi Everyone, >>> >>> I'm using RTGrapher to display a simple line graph where the x-axis >>> has values from roughly 0 to 500,000 and the y-axis from 0 to 20. >>> >>> What I'd like to be able to do is to zoom in just the x-axis, i.e. >>> instead of displaying the entire 0 to 500,000 range, be able to narrow >>> it down in stages, to, e.g. 430,000 to 431,000. The y-axis would be >>> unchanged, i.e. still 0 to 20. Ideally I could then scroll left and >>> right along the x-axis. >>> >>> I can create a Spec widget with buttons to redraw the graph, but was >>> wondering if there was a better way. >>> >>> Thanks, >>> Alistair >>> >> >> >

March 29, 2018

[TechTalk] Report 2017 Pharo Consortium and Association.

by Marcus Denker

Hi, We have a (small) techtalk today: Report 2017 Pharo Consortium and Association. https://association.pharo.org/event-2797067 - 29 Mar 2018 - 5:00 PM - 7:00 PM

March 29, 2018

Re: [Pharo-users] Zoom x-axis in RTGrapher?

by Alistair Grant

Hi Alexandre, Thanks! (more below) On 28 March 2018 at 14:56, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > Hi Alistair! > > Yes, this is something we thought about some times ago. > > After updating Roassal, try this: > -=-=-=-=-=-=-=-=-=-=-=-= > v := RTView new. > b := [ :someClasses | > g := RTGrapher new. > g view: v. > ds := RTData new. > ds points: someClasses. > ds y: [ :cls | cls numberOfMethods ]. > ds x: [ :cls | cls numberOfLinesOfCode ]. > g add: ds. > > g addDecorator: (RTRangeSelector new callback: [:es | > | classesToZoomIn | > classesToZoomIn := es collect: #model. > v cleanAll. > b value: classesToZoomIn > ]). > g build. > ]. > > b value: RTShape withAllSubclasses. > v > -=-=-=-=-=-=-=-=-=-=-=-= > > Let me know how it goes. Great, it's working fine! If you select an empty portion of the graph an error is raised - "Error: No dataset has been added?". I solved this with the following change, which simply ignores empty areas and notifies the user: RTRangeSelector>>callbackWithSelectedElements | selectedElements | selectedElements := self elementsWithinTheSelection. selectedElements ifEmpty: [ UIManager default inform: 'Empty region selected, ignoring'. ^self ]. self evaluateCallBackWithElements: selectedElements That was a quick hack, so there could well be a better solution. >From what I can see, there isn't a way to zoom back out or scroll left and right. I might modify RTRangeSelector so that a right click zooms out. I'll have to think about scrolling a bit more. Thanks again! Alistair > Cheers, > Alexandre > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >> On Mar 28, 2018, at 4:02 AM, Alistair Grant <akgrant0710(a)gmail.com> wrote: >> >> Hi Everyone, >> >> I'm using RTGrapher to display a simple line graph where the x-axis >> has values from roughly 0 to 500,000 and the y-axis from 0 to 20. >> >> What I'd like to be able to do is to zoom in just the x-axis, i.e. >> instead of displaying the entire 0 to 500,000 range, be able to narrow >> it down in stages, to, e.g. 430,000 to 431,000. The y-axis would be >> unchanged, i.e. still 0 to 20. Ideally I could then scroll left and >> right along the x-axis. >> >> I can create a Spec widget with buttons to redraw the graph, but was >> wondering if there was a better way. >> >> Thanks, >> Alistair >> > >

March 29, 2018

Re: [Pharo-users] Launcher User Templates

by Christophe Demarey

> Le 28 mars 2018 Ã 21:55, Sean P. DeNigris <sean(a)clipperadams.com> a Ã©crit : > > demarey wrote >> If you mean "How would I make my own templates available via Launcher? > > Yes, that's it. Sorry about the wrong terminology! No problem! Does the doc answer your needs?

March 29, 2018

[ANN] HighchartsSt and ba-st Web Stack new versions available

by Gabriel Cotelli

Hi, We're happy to announce a new version of the Highcharts JS Wrapper and the Web Stack hosted at https://github.com/ba-st/. This is a multi-release announcement of the following related project versions: - HighchartsSt <https://github.com/ba-st/HighchartsSt> v6.0.0 - Updated Highcharts and Highstock JS libraries to version 6.0.3 - Improved Importing Tools - Improved Travis CI integration - Willow <https://github.com/ba-st/Willow> v7.0.0. Changes since latest announcement: - Added composition of table row commands - Refactored a bunch of common utilities into it's own project - Improved JSScript extensions - Willow-Bootstrap <https://github.com/ba-st/Willow-Bootstrap> v7.0.0 - Updated Willow base support to v7.0.0 - Improved Radio Web Views - Willow-JQueryUI <https://github.com/ba-st/Willow-JQueryUI> v6.0.0 - Updated Willow base support to v7.0.0 - Improved Radio Web Views - Willow-SpinKit <https://github.com/ba-st/Willow-SpinKit> v4.0.0 - Updated Willow base support to v7.0.0 - Willow-Playground <https://github.com/ba-st/Willow-Playground/> v3.0.0 - Updated dependencies to the latest versions - You can now grab a ready to use image from the releases page - RenoirSt <https://github.com/ba-st/RenoirSt> v4.1.0 - Add another way of creating descendant combinators for cases when the right part of the expression needs parenthesis - Updated dependencies SemanticUI <https://github.com/ba-st/Willow-SemanticUI> and Materialize CSS <https://github.com/fortizpenaloza/Willow-Materialize> integration are still a work in progress. Find a more detailed changelog and migration instructions on the release pages of each repository. Special thanks to Ignacio Martinez <https://github.com/nachomf> and Juan Escalada <https://github.com/JuanEscalada> for contributing some of the new features. Also to Maxi Tabacman and Mariano Martinez Peck for the Highcharts update. Anyone interested in joining our ba-st projects <https://github.com/ba-st/> is welcomed, and you can also get some interesting ideas in crafting lint rules to support team coding standards <https://medium.com/mercap-tech-blog/supporting-team-coding-standards-af2701…> . Regards, Gabriel Cotelli, Maxi Tabacman and all the contributors.

March 28, 2018

Re: [Pharo-users] Launcher User Templates

by Sean P. DeNigris

demarey wrote > If you mean "How would I make my own templates available via Launcher? Yes, that's it. Sorry about the wrong terminology! ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

March 28, 2018