- Pharo-dev - lists.pharo.org

[pharo-project/pharo-core]

by GitHub

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

Oct. 4, 2014

[pharo-project/pharo-core] 1c3c75: 40282

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 1c3c757366ba2cad8f367ee957a228d54414fd74 https://github.com/pharo-project/pharo-core/commit/1c3c757366ba2cad8f367ee9… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-10-04 (Sat, 04 Oct 2014) Changed paths: M Morphic-Base.package/MenuMorph.class/definition.st R Morphic-Base.package/MenuMorph.class/instance/accessing/activatedFromDockingBar_.st A Morphic-Base.package/MenuMorph.class/instance/accessing/color_.st M Morphic-Base.package/MenuMorph.class/instance/accessing/items.st A Morphic-Base.package/MenuMorph.class/instance/accessing/menuItems.st R Morphic-Base.package/MenuMorph.class/instance/accessing/wasActivatedFromDockingBar.st A Morphic-Base.package/MenuMorph.class/instance/actions/adoptPaneColor_.st A Morphic-Base.package/MenuMorph.class/instance/actions/themeChanged.st A Morphic-Base.package/MenuMorph.class/instance/construction/addMenuItem_.st A Morphic-Base.package/MenuMorph.class/instance/construction/addToggle_selector_.st A Morphic-Base.package/MenuMorph.class/instance/construction/addToggle_target_selector_.st A Morphic-Base.package/MenuMorph.class/instance/construction/addToggle_target_selector_getStateSelector_.st A Morphic-Base.package/MenuMorph.class/instance/construction/addToggle_target_selector_getStateSelector_argumentList_.st A Morphic-Base.package/MenuMorph.class/instance/construction/addToggle_target_selector_getStateSelector_enablementSelector_.st A Morphic-Base.package/MenuMorph.class/instance/construction/addToggle_target_selector_getStateSelector_enablementSelector_argumentList_.st R Morphic-Base.package/MenuMorph.class/instance/construction/addUpdating_target_action_.st R Morphic-Base.package/MenuMorph.class/instance/construction/addWithLabel_enablementSelector_target_selector_argumentList_.st M Morphic-Base.package/MenuMorph.class/instance/construction/addWithLabel_enablement_action_.st R Morphic-Base.package/MenuMorph.class/instance/construction/add_target_action_.st R Morphic-Base.package/MenuMorph.class/instance/construction/title_.st M Morphic-Base.package/MenuMorph.class/instance/control/activeSubmenu_.st M Morphic-Base.package/MenuMorph.class/instance/copying/veryDeepInner_.st A Morphic-Base.package/MenuMorph.class/instance/deprecated/addUpdating_target_action_.st A Morphic-Base.package/MenuMorph.class/instance/deprecated/add_target_action_.st A Morphic-Base.package/MenuMorph.class/instance/deprecated/title_.st A Morphic-Base.package/MenuMorph.class/instance/dropping%2Fgrabbing/mouseDownInTitle_.st A Morphic-Base.package/MenuMorph.class/instance/events/takesKeyboardFocus.st R Morphic-Base.package/MenuMorph.class/instance/rounding/roundedCorners.st M Morphic-Examples.package/WidgetExamples.class/class/examples/exampleTextEntryWithCompletionDialog.st A Morphic-Widgets-Extra.package/DockingBarMenuMorph.class/README.md A Morphic-Widgets-Extra.package/DockingBarMenuMorph.class/definition.st A Morphic-Widgets-Extra.package/DockingBarMenuMorph.class/instance/accessing/activatedFromDockingBar_.st A Morphic-Widgets-Extra.package/DockingBarMenuMorph.class/instance/accessing/wasActivatedFromDockingBar.st A Morphic-Widgets-Extra.package/DockingBarMenuMorph.class/instance/as yet unclassified/activeSubmenu_.st A Morphic-Widgets-Extra.package/DockingBarMenuMorph.class/instance/as yet unclassified/roundedCorners.st A Morphic-Widgets-Extra.package/DockingBarMenuMorph.class/instance/as yet unclassified/veryDeepInner_.st A Polymorph-Widgets.package/EntryCompletion.class/class/examples/exampleTextEntryWithCompletionDialog.st M Polymorph-Widgets.package/EntryCompletion.class/instance/accessing/setChooserWith_labels_.st A Polymorph-Widgets.package/IdentifierChooserMorph.class/class/instance creation/example.st R Polymorph-Widgets.package/extension/MenuMorph/instance/addMenuItem_.st R Polymorph-Widgets.package/extension/MenuMorph/instance/addToggle_selector_.st R Polymorph-Widgets.package/extension/MenuMorph/instance/addToggle_target_selector_.st R Polymorph-Widgets.package/extension/MenuMorph/instance/addToggle_target_selector_getStateSelector_.st R Polymorph-Widgets.package/extension/MenuMorph/instance/addToggle_target_selector_getStateSelector_argumentList_.st R Polymorph-Widgets.package/extension/MenuMorph/instance/addToggle_target_selector_getStateSelector_enablementSelector_.st R Polymorph-Widgets.package/extension/MenuMorph/instance/addToggle_target_selector_getStateSelector_enablementSelector_argumentList_.st R Polymorph-Widgets.package/extension/MenuMorph/instance/adoptPaneColor_.st R Polymorph-Widgets.package/extension/MenuMorph/instance/color_.st R Polymorph-Widgets.package/extension/MenuMorph/instance/menuItems.st R Polymorph-Widgets.package/extension/MenuMorph/instance/mouseDownInTitle_.st R Polymorph-Widgets.package/extension/MenuMorph/instance/takesKeyboardFocus.st R Polymorph-Widgets.package/extension/MenuMorph/instance/themeChanged.st M SUnit-UI.package/TestRunner.class/instance/accessing-categories/categoryMenu_.st M SUnit-UI.package/TestRunner.class/instance/accessing-classes/classMenu_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script282.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40282.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st M Spec-Core.package/NewListModel.class/class/examples/exampleWithMenu.st M Spec-Core.package/NewListModel.class/instance/protocol/getMenu_.st M Spec-Tools.package/ChangeSorterApplication.class/instance/menu/changeSetMenu_shifted_.st M Spec-Tools.package/ChangeSorterApplication.class/instance/menu/classMenu_shifted_.st M Spec-Tools.package/ChangeSorterApplication.class/instance/menu/messageMenu_shifted_.st M Spec-Tools.package/DualChangeSorterApplication.class/instance/menu/changesMenu_shifted_from_to_.st M Tool-ConfigurationBrowser.package/MetacelloConfigurationBrowserPane.class/instance/menu/configurationListMenu_.st M Tool-SystemReporter.package/SystemReporter.class/instance/accessing-categories/categoryMenu_.st M Tool-SystemReporter.package/SystemReporter.class/instance/accessing-report/reportMenu_.st Log Message: ----------- 40282 14119 Cleaning left over of docking bar in menu https://pharo.fogbugz.com/f/cases/14119 http://files.pharo.org/image/40/40282.zip

Oct. 4, 2014

[pharo-project/pharo-core]

by GitHub

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

Oct. 4, 2014

Re: [Pharo-dev] History of the .image

by David T. Lewis

On Sat, Oct 04, 2014 at 04:00:15PM +0200, Hilaire wrote: > Hello, > > I am curious. What is the history of the Pharo image? I know it is > forked from Squeak, but then from where does come the Squeak image? > How and when was it build from its source code definition? > When did it became an "evolving organism" as it is today? > > Thanks > > Hilaire http://lists.squeakfoundation.org/pipermail/squeak-dev/2014-September/17995…

Oct. 4, 2014

History of the .image

by Hilaire

Hello, I am curious. What is the history of the Pharo image? I know it is forked from Squeak, but then from where does come the Squeak image? How and when was it build from its source code definition? When did it became an "evolving organism" as it is today? Thanks Hilaire -- Dr. Geo - http://drgeo.eu iStoa - http://istoa.drgeo.eu

Oct. 4, 2014

Re: [Pharo-dev] "Browser" on a single class

by Esteban Lorenzano

and this is same with glamour: browser := GLMTabulator new row: [ :row | row column: #protocols; column: #methods ]; row: #code; yourself. browser transmit to: #protocols; andShow: [ :a| a list display: [ :class | class organization protocols ]; format: #name ]. browser transmit from: #protocols; to: #methods; andShow: [ :a| a list display: [ :protocol | protocol methods ] ]. browser transmit from: #methods; to: #code; andShow: [ :a | a smalltalkCode smalltalkClass: [ browser entity ]; display: [ :method | (browser entity>>method) sourceCode ] ]. browser openOn: Morph. Of course spec is capable of doing that. But glamour is designed with transitions and scripting in mind (thinking specially on browsers), while spec is designed for components and composition. Esteban > On 04 Oct 2014, at 15:35, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > 2014-10-03 13:26 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com <mailto:estebanlm@gmail.com>>: > >> On 03 Oct 2014, at 13:14, Nicolai Hess <nicolaihess(a)web.de <mailto:nicolaihess@web.de>> wrote: >> >> >> Am 03.10.2014 12:34 schrieb "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com <mailto:yuriy.tymchuk@me.com>>: >> > >> > Hi. >> > >> > I want to make something like a browser on a single class. I.e. just use 2 last lists out if 4 in standard browser. >> > >> > Is there already something like that? If not, should I use existing widgets, or implement my own using spec? >> > >> > Cheers! >> > Uko >> > >> > Sent from my iPhone >> >> I think that is pretty easy with some spec models. >> Maybe there is already an example >> > yes, but a few models means a few classes :) > in a single class, it will e a lot easier glamour (which btw, is specially designed for that: to make browsers). > > You can work with ready made models like ListModel/TextModel and just need one class for sticking them > together. Here some code, evaluateable from workspace, that shows how we > can build a "simple browser" with spec models: > This is just the simple skeleton, for more details it would be a bit confusing doing all this > in one workspace "script" :) > > class:=Morph. > method:=class>>#openInWorld. > > composed:= DynamicComposableModel new. > composed instantiateModels: #(code TextModel protocols ListModel methods ListModel). > composed code text:method sourceCode. > composed protocols items: class protocols. > composed methods items: class selectors. > composed code aboutToStyle:true. > composed code behavior:class. > composed title: class asString. > composed code acceptBlock:[:text | > class compile:text notifying:nil. > ]. > composed protocols whenSelectedItemChanged:[:item | > composed methods items:( class selectorsInProtocol: item) > ]. > composed methods whenSelectedItemChanged:[:item | > item ifNotNil:[ > method:=class methodDict at:item. > composed code text:method sourceCode] > ]. > composed openWithSpecLayout:( > SpecLayout composed > newColumn:[:c | c > newRow:[:r | r > add: #protocols; > add: #methods > ]; > add: #code]; > yourself). > > > Esteban >> Hilaire asked for a simple Method editor and >> i wrote a simple example build with DynamicComposableModel, search the Mailingliste. >>

Oct. 4, 2014

Re: [Pharo-dev] "Browser" on a single class

by Nicolai Hess

2014-10-03 13:26 GMT+02:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > > On 03 Oct 2014, at 13:14, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > Am 03.10.2014 12:34 schrieb "Yuriy Tymchuk" <yuriy.tymchuk(a)me.com>: > > > > Hi. > > > > I want to make something like a browser on a single class. I.e. just use > 2 last lists out if 4 in standard browser. > > > > Is there already something like that? If not, should I use existing > widgets, or implement my own using spec? > > > > Cheers! > > Uko > > > > Sent from my iPhone > > I think that is pretty easy with some spec models. > Maybe there is already an example > > yes, but a few models means a few classes :) > in a single class, it will e a lot easier glamour (which btw, is specially > designed for that: to make browsers). > You can work with ready made models like ListModel/TextModel and just need one class for sticking them together. Here some code, evaluateable from workspace, that shows how we can build a "simple browser" with spec models: This is just the simple skeleton, for more details it would be a bit confusing doing all this in one workspace "script" :) class:=Morph. method:=class>>#openInWorld. composed:= DynamicComposableModel new. composed instantiateModels: #(code TextModel protocols ListModel methods ListModel). composed code text:method sourceCode. composed protocols items: class protocols. composed methods items: class selectors. composed code aboutToStyle:true. composed code behavior:class. composed title: class asString. composed code acceptBlock:[:text | class compile:text notifying:nil. ]. composed protocols whenSelectedItemChanged:[:item | composed methods items:( class selectorsInProtocol: item) ]. composed methods whenSelectedItemChanged:[:item | item ifNotNil:[ method:=class methodDict at:item. composed code text:method sourceCode] ]. composed openWithSpecLayout:( SpecLayout composed newColumn:[:c | c newRow:[:r | r add: #protocols; add: #methods ]; add: #code]; yourself). > > Esteban > > Hilaire asked for a simple Method editor and > i wrote a simple example build with DynamicComposableModel, search the > Mailingliste. > > >

Oct. 4, 2014

Re: [Pharo-dev] gt issues

by kmo

Well, one man's intuitive is another man's completely obscure. In the pharo context, the dots are a completely new navigation widget - used nowhere else - and their function is unclear. I think part of the problem is that the dots do not appear on any kind of obvious toolbar - they are more or less just dots on the bottom of the window. There is no visual cue that they have any function at all. They could be mere decoration. Just my two cents. -- View this message in context: http://forum.world.st/gt-issues-tp4782476p4782557.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

Oct. 4, 2014

Re: [Pharo-dev] Setting the code highlighter for specific methods/classes

by stepharo

I know that when alain rewrote the integration of hilightler in paragraph he wrote some nice comments and examples. stef On 4/10/14 12:23, Stephan Eggermont wrote: > In Squeak there is a convenience method defined on Behavior to > set the highlighter for the code. There was a bug report/discussion > a few years ago with Lukas. It was noted that that change is mostly > needed at the same time as changing the compiler/parser and > the save behavior. At the time Lukas suggested to have an object > representing this whole compilation context. With Helvetica this > would be needed at a text range granularity, I assume. > > What is the current state of this in Pharo, and how do I make > Nautilus (and other browsers) use a different highlighter? > > Stephan > > > >

Oct. 4, 2014

Re: [Pharo-dev] gt issues

by Camille Teruel

On 4 oct. 2014, at 12:44, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 04 Oct 2014, at 11:55, kmo <voxkmp(a)gmail.com> wrote: > >> I've raised two issues on the GT playground: >> >> https://pharo.fogbugz.com/f/cases/14158/Navigation-buttons-icons-at-bottom-… >> >> https://pharo.fogbugz.com/f/cases/14157/Navigation-buttons-at-bottom-of-GT-… >> >> When I first tried the playground I never even noticed the dots at the >> bottom of the window - they do not show up well in the default theme. - >> (they seem OK in the dark theme screenshots I've seen). >> >> Also, I think little dots are not intuitive. It would be better if you had >> video controller buttons or perhaps little outlined squares with page >> numbers in them. Dots on their own mean nothing. > > Well, I agree that they might be a bit hard to find, but they are far from meaningless. There are many websites with carrousels that use the same metaphor. Yes I found it quite intuitive, and the miniatures are nice too. BTW is there shortcut to navigate between panes? Camille

Oct. 4, 2014