- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Write (rubric) text changes back to the object in GTInspector

by Andrei Chis

Cool example. I slightly modified it and added it to the glamour examples :) | browser morph | morph := StringMorph new. morph font:(LogicalFont familyName: 'Source Code Pro' pointSize: 30). browser := GLMTabulator new. browser row: #main; row: #preview. browser transmit to: #main; andShow: [ :a | a text onChangeOfPort: #text act: [ :text | morph contents:text text] ]. browser transmit to: #preview; andShow: [ :a | a morph title: 'Preview'; display: [ morph ] ]. ^ browser openOn: 'some text' On Fri, Oct 30, 2015 at 11:47 AM, Nicolai Hess <nicolaihess(a)gmail.com> wrote: > > > 2015-10-30 16:32 GMT+01:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > >> Hi, >> >> You can try this: >> >> composite := GLMCompositePresentation new. >> composite pharoPlayground >> title: 'Script'; >> variableBindings: [ { #x -> 1. #y -> 2 } ]. >> composite >> openOn: 'x+y'. >> >> For the moment only script presentations can have variables. >> >> Btw #pharoPlayground and #rubricText will be deprecated in the latest >> version in favour of #pharoScript and #text >> >> Cheers, >> Andrei >> >> On Fri, Oct 30, 2015 at 11:14 AM, Torsten Bergmann <astares(a)gmx.de> >> wrote: >> >>> Hi, >>> >>> if one has an inspector extension that shows a textual iVar of an object >>> representing code (using #rubricText, #pharoMethod or #pharoPlayground) >>> as in this example: >>> >>> gtInspectorSourceIn: composite >>> <gtInspectorPresentationOrder: 30> >>> ^ composite pharoMethod >>> title: 'Source'; >>> smalltalkClass: [ self methodClass ]; >>> display: [ self getSource ]; >>> act: [ self browse ] icon: GLMUIThemeExtraIcons >>> glamorousBrowse entitled: 'Browse' >>> >>> What is the best/correct way to set the iVar when the text is typed so >>> the >>> state of the iVar represents the lively editing in the inspector >>> extension? >>> >>> Or is there a way to realize this somehow with Glamour ports using the >>> #text port? >>> >> > > you can define an action on a port change: > onChangeOfPort:act: > > | browser morph | > morph := StringMorph new openInWorld. > morph font:(LogicalFont familyName: 'Source Code Pro' pointSize: 30). > browser := GLMTabulator new. > browser > row: #main. > (browser transmit) > to: #main; > andShow: [ :a | a rubricText > onChangeOfPort: #text act: [ :text | > morph contents:text text] ]. > > ^ browser openOn:'type some text' > > This will open a StringMorph and a GlamourBrowser. > If you change the text in the browser, it will change the contents of the > string morph. > > > >>> Thanks >>> T. >>> >> >> >

Oct. 30, 2015

Does anyone remember details of a "pro-Smalltalk" merger circa 2013?

by Richard Sargent

I heard an anecdote of a recent merger between two companies in which one had over 200 people supporting a Java application and the other had ~25 people supporting a Smalltalk application. The surprising result was that the Smalltalk application was selected for the merged company rather than the Java one. I would like to know which companies were involved, when this occurred, and what the precise details were. Thank you! -- View this message in context: http://forum.world.st/Does-anyone-remember-details-of-a-pro-Smalltalk-merge… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 30, 2015

Re: [Pharo-dev] Write (rubric) text changes back to the object in GTInspector

by Andrei Chis

On Fri, Oct 30, 2015 at 12:07 PM, Torsten Bergmann <astares(a)gmx.de> wrote: > #onChangeOfPort:act: solved the problem. Thanks a lot! > > BTW: would be cool if you both could join Pharo on Slack. > This and next week I'm travelling but afterwards I'll join

Oct. 30, 2015

Re: [Pharo-dev] GTInspector extension menues with line separators and submenu items

by Andrei Chis

Super. Thanks for the fix. Right now I'm in the middle of deprecating the text renderer based in PluggableTextMorph and moving everything in glamour to rubric. I'll probably be done today or tomorrow. If it takes me longer and you really need this in pharo feel free to make an issue with a slice :) On Fri, Oct 30, 2015 at 11:53 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Andrei, > > using the #with: aBlock variant initially seemed to have no effect > when using a tree representation. > > Looks like GLMTreeMorphNodeModel>>#menu:shifted: does not honor the > "separatorAfter" boolean flag during menu construction as it already > done in GLMMorphicModel>>menu: > > This is a bug as this was left out in this method. I added the missing > piece to GLMTreeMorphNodeModel>>#menu:shifted: to make it work. > Works like a charme. > > Packaged as for further review: > > --------------------------------------------------------------------------- > Name: Glamour-Morphic-Widgets-TorstenBergmann.183 > Author: TorstenBergmann > Time: 30 October 2015, 4:49:41.455057 pm > UUID: 9c2470db-73bc-2c43-b40d-1633b8de00eb > Ancestors: Glamour-Morphic-Widgets-MarcusDenker.182 > > The #separatorAfter flag of the action should have an effect > --------------------------------------------------------------------------- > > Can you integate it (or should I open an additional bug entry first)? > When is the next round for a Glamour update to have this quickly in recent > Pharo image? > > Thx > T. > > Gesendet: Freitag, 30. Oktober 2015 um 14:14 Uhr > Von: "Andrei Chis" <chisvasileandrei(a)gmail.com> > An: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: Re: [Pharo-dev] GTInspector extension menues with line separators > and submenu items > > Hi, > > Currently when creating methods using the scripting actions from glamour > you cannot directly specify #withSeparatorAfter. > Right now you can either add actions manually (for examples > #browsingSelectionActions) or use something like: > > with: [ :presentation | presentation selectionActions > last withSeparatorAfter] > > If you find a nice way to improve this API please do so :) > > > For submenus look in GLMBasiExamples>>#staticAndDynamicMenu > > Cheers, > Andrei > > On Fri, Oct 30, 2015 at 9:00 AM, Torsten Bergmann <astares(a)gmx.de> > wrote:Hi, > > Is it possible to separate the context menus (built with #selectionAct: > ...) > in GTInspector extension methods with lines similar to the regular menue > building > where #withSeparatorAfter is used. > > Is it possible to have submenues in the context menu items (cascading > menues as the world menu). > > Any examples?` > > Thx > T. > >

Oct. 30, 2015

Re: [Pharo-dev] #50409 regression

by Thierry Goubier

Le 30/10/2015 11:59, stepharo a Ã©crit : > I'm thorn because on one hand I would like to be able to express a >>> visitor for the complete compilation unit >>> and in particular package and extensions but may be we do not need to >>> have this nodes and just >>> have an object. I would be favor to have a nice and full AST >>> representation of the compilation unit. >> >> Well, you can unify Ring and RBMethodNode from the point of view of >> the visitor: you're not in Java where typing could be an issue. > If you have some cycle I would love to have that unification :) > Yes I know :) and thought about it. I'll have a look. >> Note that I have a structure + visitor for the above AST level >> implemented in the AltBrowser (covers groups of groups of packages, >> packages, package tags, classes, extensions, protocols, methods, >> comments). > Do you have a gofer expression :) Loading AltBrowser from the ConfigurationBrowser and looking at the Alt-Browser-Nodes package tag :) A bit unstable to use as Browser on Pharo5 at the moment, however. I'm in the middle of a browser rewrite. I looked and I don't have a Visitor on the structure. I know I did that on purpose, but can't remember what was my rationale. > so that I can load the code because I think that we should have this as > a clearly identifiable component. I tried to match to Ring at a point, but Ring coverage is partial. My approach is symbol-based (each node only contains a symbol on the underlying object and resolve the symbol when needed. resolution can be dependent on the environment: the node parent). > We may not have to load it always in Pharo but it should be there. It could simplify Nautilus code a bit. > Stef > > >

Oct. 30, 2015

Re: [Pharo-dev] Metacello and preparing a release?

by Eliot Miranda

Hi Dale, but why can't Metacello provide something really simple that automatically generates a configuration with all the prerequisites fully defined as fixed specific versions? Then Holger can easily freeze his release using the new confit and continue his internal development using his current configuration. Why is is about the repository and not the versions? Seems like the tail wagging the dog to me. _,,,^..^,,,_ (phone) > On Oct 30, 2015, at 12:44 PM, Dale Henrichs <dale.henrichs(a)gemtalksystems.com> wrote: > > Holger ... > > Frankly this is one of the main reasons I have headed down the path of using "git" (or any other disk-based scm) for GsDevKit/GLASS .... > > If all of the applications that you use are managed under "git", then for production you make local clones for all of the projects including your own ... Use the Metacallo lock[1] command and lock each project to reference your local filtree/clone ... then when you use "Metacello new" to load projects, the "locked" versions have precedence and there is no need to modify all of the configurations/baselines or try the half a dozen other hacks ... > > With the approach you can have a development set of project clones, a sandbox set and a production set ... and all three subsystesm use the exact same load scripts ... you simply change which repositories are locked ... > > Managing locks can be tricky, but it's a problem that I've solved with tODE as well, use .ston files that contain a "project entry" specification object with a number of fields including whther or not the spec is locked... when an image (stone in the case of GemStone) comes up it looks for "project entries" on disk and it then registers those projects in the Metacello Project registry ... voila _if_ you load one of those locked projects your local clone will be used ... > > I will talking about these things at the upcoming Smalltalks in Buenos Aires ... > > Dale > > [1] https://github.com/dalehenrich/metacello-work/blob/master/docs/LockCommandR… > >> On 10/30/2015 03:10 AM, Holger Freyther wrote: >> Hi, >> >> I have an application that is about to be moved into production. Currently it is >> pulling "stable" or sometimes bleedingEdge of other configurations. After the >> system moves from testing into production I would like to have tight control of >> which packages are updated from one version to another. E.g. not have a >> Voyage "stable" upgrade just because there is a new stable version but probably >> at the same time still use a symbolic reference myapp-stable-5 to load the >> package? >> >> Is there a common/known to work approach. I could identify all used Metacello >> configs and move them to my own infrastructure and then copy the use packages >> as well. Is there tooling support for adding such a "freeze"? How do other handle >> a release of an application that needs to be updated in an "incremental" way? >> >> cheers >> holger > >

Oct. 30, 2015

Re: [Pharo-dev] Metacello and preparing a release?

by Dale Henrichs

Holger ... Frankly this is one of the main reasons I have headed down the path of using "git" (or any other disk-based scm) for GsDevKit/GLASS .... If all of the applications that you use are managed under "git", then for production you make local clones for all of the projects including your own ... Use the Metacallo lock[1] command and lock each project to reference your local filtree/clone ... then when you use "Metacello new" to load projects, the "locked" versions have precedence and there is no need to modify all of the configurations/baselines or try the half a dozen other hacks ... With the approach you can have a development set of project clones, a sandbox set and a production set ... and all three subsystesm use the exact same load scripts ... you simply change which repositories are locked ... Managing locks can be tricky, but it's a problem that I've solved with tODE as well, use .ston files that contain a "project entry" specification object with a number of fields including whther or not the spec is locked... when an image (stone in the case of GemStone) comes up it looks for "project entries" on disk and it then registers those projects in the Metacello Project registry ... voila _if_ you load one of those locked projects your local clone will be used ... I will talking about these things at the upcoming Smalltalks in Buenos Aires ... Dale [1] https://github.com/dalehenrich/metacello-work/blob/master/docs/LockCommandR… On 10/30/2015 03:10 AM, Holger Freyther wrote: > Hi, > > I have an application that is about to be moved into production. Currently it is > pulling "stable" or sometimes bleedingEdge of other configurations. After the > system moves from testing into production I would like to have tight control of > which packages are updated from one version to another. E.g. not have a > Voyage "stable" upgrade just because there is a new stable version but probably > at the same time still use a symbolic reference myapp-stable-5 to load the > package? > > Is there a common/known to work approach. I could identify all used Metacello > configs and move them to my own infrastructure and then copy the use packages > as well. Is there tooling support for adding such a "freeze"? How do other handle > a release of an application that needs to be updated in an "incremental" way? > > cheers > holger

Oct. 30, 2015

Re: [Pharo-dev] Write (rubric) text changes back to the object in GTInspector

by Torsten Bergmann

#onChangeOfPort:act: solved the problem. Thanks a lot! BTW: would be cool if you both could join Pharo on Slack.

Oct. 30, 2015

Re: [Pharo-dev] GTInspector extension menues with line separators and submenu items

by Torsten Bergmann

Hi Andrei, using the #with: aBlock variant initially seemed to have no effect when using a tree representation. Looks like Â GLMTreeMorphNodeModel>>#menu:shifted: does not honor the "separatorAfter" boolean flag during menu construction as it already done in GLMMorphicModel>>menu: This is a bug as this was left out in this method. I added the missing piece to GLMTreeMorphNodeModel>>#menu:shifted: to make it work. Works like a charme. Packaged as for further review: --------------------------------------------------------------------------- Name: Glamour-Morphic-Widgets-TorstenBergmann.183 Author: TorstenBergmann Time: 30 October 2015, 4:49:41.455057 pm UUID: 9c2470db-73bc-2c43-b40d-1633b8de00eb Ancestors: Glamour-Morphic-Widgets-MarcusDenker.182 The #separatorAfter flag of the action should have an effectÂ --------------------------------------------------------------------------- Can you integate it (or should I open an additional bug entry first)? When is the next round for a Glamour update to have this quickly in recent Pharo image? Thx T. Gesendet:Â Freitag, 30. Oktober 2015 um 14:14 Uhr Von:Â "Andrei Chis" <chisvasileandrei(a)gmail.com> An:Â "Pharo Development List" <pharo-dev(a)lists.pharo.org> Betreff:Â Re: [Pharo-dev] GTInspector extension menues with line separators and submenu items Hi, Â Currently when creating methods using the scripting actions from glamour you cannot directly specify #withSeparatorAfter. Right now you can either add actions manually (for examples #browsingSelectionActions) or use something like: Â Â Â with: [ :presentation | presentation selectionActions lastÂ withSeparatorAfter] Â If you find a nice way to improve this API please do so :) Â Â For submenus look in GLMBasiExamples>>#staticAndDynamicMenu Â Cheers, Andrei Â On Fri, Oct 30, 2015 at 9:00 AM, Torsten Bergmann <astares(a)gmx.de> wrote:Hi, Is it possible to separate the context menus (built with #selectionAct: ...) in GTInspector extension methods with lines similar to the regular menue building where #withSeparatorAfter is used. Is it possible to have submenues in the context menu items (cascading menues as the world menu). Any examples?` Thx T. Â

Oct. 30, 2015

Re: [Pharo-dev] Write (rubric) text changes back to the object in GTInspector

by Andrei Chis

Ahh. I think I misunderstood your question :) On Oct 30, 2015 11:48 AM, "Nicolai Hess" <nicolaihess(a)gmail.com> wrote: > > > 2015-10-30 16:32 GMT+01:00 Andrei Chis <chisvasileandrei(a)gmail.com>: > >> Hi, >> >> You can try this: >> >> composite := GLMCompositePresentation new. >> composite pharoPlayground >> title: 'Script'; >> variableBindings: [ { #x -> 1. #y -> 2 } ]. >> composite >> openOn: 'x+y'. >> >> For the moment only script presentations can have variables. >> >> Btw #pharoPlayground and #rubricText will be deprecated in the latest >> version in favour of #pharoScript and #text >> >> Cheers, >> Andrei >> >> On Fri, Oct 30, 2015 at 11:14 AM, Torsten Bergmann <astares(a)gmx.de> >> wrote: >> >>> Hi, >>> >>> if one has an inspector extension that shows a textual iVar of an object >>> representing code (using #rubricText, #pharoMethod or #pharoPlayground) >>> as in this example: >>> >>> gtInspectorSourceIn: composite >>> <gtInspectorPresentationOrder: 30> >>> ^ composite pharoMethod >>> title: 'Source'; >>> smalltalkClass: [ self methodClass ]; >>> display: [ self getSource ]; >>> act: [ self browse ] icon: GLMUIThemeExtraIcons >>> glamorousBrowse entitled: 'Browse' >>> >>> What is the best/correct way to set the iVar when the text is typed so >>> the >>> state of the iVar represents the lively editing in the inspector >>> extension? >>> >>> Or is there a way to realize this somehow with Glamour ports using the >>> #text port? >>> >> > > you can define an action on a port change: > onChangeOfPort:act: > > | browser morph | > morph := StringMorph new openInWorld. > morph font:(LogicalFont familyName: 'Source Code Pro' pointSize: 30). > browser := GLMTabulator new. > browser > row: #main. > (browser transmit) > to: #main; > andShow: [ :a | a rubricText > onChangeOfPort: #text act: [ :text | > morph contents:text text] ]. > > ^ browser openOn:'type some text' > > This will open a StringMorph and a GlamourBrowser. > If you change the text in the browser, it will change the contents of the > string morph. > > > >>> Thanks >>> T. >>> >> >> >

Oct. 30, 2015