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

Write (rubric) text changes back to the object in GTInspector

by Torsten Bergmann

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? Thanks T.

Oct. 30, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50415 Home: https://github.com/pharo-project/pharo-core

Oct. 30, 2015

[pharo-project/pharo-core] d83c78: 50415

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: d83c78382b8f4f05794631ae31d116796c412a14 https://github.com/pharo-project/pharo-core/commit/d83c78382b8f4f05794631ae… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2015-10-30 (Fri, 30 Oct 2015) Changed paths: M Collections-Streams.package/Generator.class/README.md R Monticello.package/MCLazyVersionInfo.class/instance/private/loadAncestorsAndStepChildren.st A Monticello.package/MCLazyVersionInfo.class/instance/private/setAncestors_.st A Monticello.package/MCLazyVersionInfo.class/instance/private/setStepChildren_.st A Monticello.package/MCVersionInfo.class/instance/private/loadAncestorsAndStepChildren.st A Monticello.package/MCVersionInfo.class/instance/private/setAncestors_.st A Monticello.package/MCVersionInfo.class/instance/private/setStepChildren_.st M MonticelloGUI.package/MCTool.class/README.md A MonticelloGUI.package/MCTool.class/class/accessing/mcVersionCache.st A MonticelloGUI.package/MCTool.class/class/class initialization/flushMCVersionCache.st A MonticelloGUI.package/MCTool.class/class/class initialization/initMCVersionCache.st M MonticelloGUI.package/MCTool.class/definition.st A MonticelloGUI.package/extension/MCLazyVersionInfo/instance/loadAncestorsAndStepChildren.st M Nautilus.package/AbstractNautilusUI.class/definition.st M Nautilus.package/AbstractNautilusUI.class/instance/icon/classIconFor_.st M Nautilus.package/AbstractNautilusUI.class/instance/initialization/initialize.st R Nautilus.package/AbstractNautilusUI.class/instance/private/setCachedHierarchyClass_.st M Nautilus.package/Nautilus.class/definition.st M Nautilus.package/Nautilus.class/instance/accessing/uiClass.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50414.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50415.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50414.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50415.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 50415 16894 Better generator class comment https://pharo.fogbugz.com/f/cases/16894 16881 MCLazyVersion: avoid aggressive fetch of version info https://pharo.fogbugz.com/f/cases/16881 16900 Small Nautilus cleanup https://pharo.fogbugz.com/f/cases/16900 http://files.pharo.org/image/50/50415.zip

Oct. 30, 2015

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

by Andrei Chis

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] You can get a real impact on newbies!!!

by stepharo

I published that in https://pharo.fogbugz.com/f/cases/16902/Improve-Array-comment as a fix. Took me 5 min. You can really improve user experience with 5 min! Stef Array is a fixed-sized collection of elements accessed by integer indices. Contrary to the C convention, the first element of a Smalltalk array is at position 1 and not 0. The main protocol to access array elements is the method at: and at:put:. - at: anInteger returns the element at index anInteger. - at: anInteger put: anObject puts anObject at index anInteger. Arrays are fixed-size collections therefore we cannot add or remove elements at the end of an array. The following code creates an array of size 5, puts values in the first 3 locations and returns the first element. [[[ | anArray | anArray := Array new: 5. anArray at: 1 put: 4. anArray at: 2 put: 3/2. anArray at: 3 put: 'ssss'. anArray at: 1 > 4 ]]] #() creates literal arrays with static (or âliteralâ) elements that have to be known when the expression is compiled, and not when it is executed. The following code creates an array of size 2 where the first element is the (literal) number 1 and the second the (literal) string 'here'. [[[ #(1 'here') size > 2 ]]] { } is a way to create arrays in a more dynamic manner. [[[ | array | array := (Array new: 2). array at: 1 put: (Point x: 10 y: 20); at: 2 put: (Point x: 10 y: 20). array ]]] is equivalent to [[[ {(10@20) . (10@20)} {Point x: 10 y: 20 . Point x: 10 y: 20} ]]] Le 30/10/15 08:57, stepharo a Ã©crit : > Hi guys > > Array comment is > > "I present an ArrayedCollection whose elements are objects." > > Seriously this is inacceptable. > > I started to improve. Now we should port some text from PBE and add it > in the class comment. > > Please help this is simple super easy and this is a welcome for newbies. > > Stef > >

Oct. 30, 2015

GTInspector extension menues with line separators and submenu items

by Torsten Bergmann

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

You can get a real impact on newbies!!!

by stepharo

Hi guys Array comment is "I present an ArrayedCollection whose elements are objects." Seriously this is inacceptable. I started to improve. Now we should port some text from PBE and add it in the class comment. Please help this is simple super easy and this is a welcome for newbies. Stef

Oct. 30, 2015

Re: [Pharo-dev] what is this method?

by Nicolai Hess

2015-10-30 12:49 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > I saw this today: > > Class>>#private_subclass: t instanceVariableNames: f classVariableNames: d > poolDictionaries: s category: cat > > 1) method name is not according to conventions (should be > #privateSubclass:instanceVariableNames:classVariableNames: > poolDictionaries:category:) > 2) variable names are not good: t, f, d, s and cat do not means anything. > 3) if is private, needs to be in âprivateâ protocol. > 4) more than âprivateâ I think itâs function is âbasicââ¦ but thatâs not a > real problem :) > > please, a fix? > This is my fix for issue 16836 <https://pharo.fogbugz.com/f/cases/16836/Can-t-remove-an-instance-variable-a…> Can't remove an instance variable and a trait in one step to fix this issue, I had to add another method private_subclass ... between the two subclass:... variants, one with a uses-traits and one without the uses-traits name. If you find a better way, please let me know. About the variable naming, well I just copied the existing method arg names. It is not in the "private" category, because it is not private to the trait users that have to implement this. The method is just called "private_...." because I could not think of a better name. > > Esteban >

Oct. 30, 2015

what is this method?

by Esteban Lorenzano

I saw this today: Class>>#private_subclass: t instanceVariableNames: f classVariableNames: d poolDictionaries: s category: cat 1) method name is not according to conventions (should be #privateSubclass:instanceVariableNames:classVariableNames: poolDictionaries:category:) 2) variable names are not good: t, f, d, s and cat do not means anything. 3) if is private, needs to be in âprivateâ protocol. 4) more than âprivateâ I think itâs function is âbasicââ¦ but thatâs not a real problem :) please, a fix? Esteban

Oct. 30, 2015

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/50414 Home: https://github.com/pharo-project/pharo-core

Oct. 30, 2015