- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] GTInspector and huge arrays issue

by kilon alios

I am very interested into Brick, because I am very interesting into anything GUI and graphic wise and I want to push pharo forward in that field with my own efforts as best I can. The scrolling of your examples is actually very smooth. Why the class you use is not available in Moose 5.0 ? Because a moose 5.0 image I have downloaded recently with pharolauncher that it contains GTSpotter yet it does not have the class you use here. On Wed, Dec 10, 2014 at 9:31 PM, Aliaksei Syrel <alex.syrel(a)gmail.com> wrote: > Hi, > > in case someone is still interested, a Glamour-Morphic-Brick (extension of > morph, that was used to build a Spotter) > supports a very large lists. You can try in the latest version: > > GLMScrollListBrick exampleCollection - to open a list of all classes in > the image (each element in the list is a morph). > GLMScrollListBrick example - list of 2000 elements > GLMScrollListBrick exampleInfinity - list of Float infinity number of > elements. > > if your pharo image is old: > >> Gofer new >> smalltalkhubUser: 'Moose' project: 'Glamour'; >> package: 'Glamour-Morphic-Brick'; load. > > > Maybe we will use it instead of default lists in Inspector. > > Cheers, > Alex > > > On Thu, Dec 4, 2014 at 4:04 PM, Ben Coman <btc(a)openinworld.com> wrote: > >> Sven Van Caekenberghe wrote: >> >>> On 04 Dec 2014, at 11:45, phil(a)highoctane.be wrote: >>>> >>>> But further than that I want to edit values in inspectors. >>>> >>> >>> Yes ! >>> >>> And auto refresh ! >>> >>> Both of these could be depending on presentation, so that heavy >>> presentations can opt out. >>> >>> >>> >>> >>> >> It would be good if there was some visual indication of which >> presentations auto-refreshed - like a drop pin looking like its "stuck-in" >> when not-auto-refreshing. A user might even be able to change the state of >> the pin, with the just the default dependent on type of presentation. >> cheers -ben >> >> >

Dec. 10, 2014

Ugly textrendering (vertical label)

by Nicolai Hess

Someone knows, why the text on the completion morph is so ugly? For example, this text Morph ne will open a completion window for "Morph class". This name is a vertical label on the left. The text looks ugly when we are using a FT font. Can we do anything to make this look better ? I know that (smooth) text rendering is difficult for arbitrary rotated forms, but this rotation around n*90 degree works with StrikeFont. nicolai

Dec. 10, 2014

Re: [Pharo-dev] GTInspector and huge arrays issue

by Aliaksei Syrel

Hi, in case someone is still interested, a Glamour-Morphic-Brick (extension of morph, that was used to build a Spotter) supports a very large lists. You can try in the latest version: GLMScrollListBrick exampleCollection - to open a list of all classes in the image (each element in the list is a morph). GLMScrollListBrick example - list of 2000 elements GLMScrollListBrick exampleInfinity - list of Float infinity number of elements. if your pharo image is old: > Gofer new > smalltalkhubUser: 'Moose' project: 'Glamour'; > package: 'Glamour-Morphic-Brick'; load. Maybe we will use it instead of default lists in Inspector. Cheers, Alex On Thu, Dec 4, 2014 at 4:04 PM, Ben Coman <btc(a)openinworld.com> wrote: > Sven Van Caekenberghe wrote: > >> On 04 Dec 2014, at 11:45, phil(a)highoctane.be wrote: >>> >>> But further than that I want to edit values in inspectors. >>> >> >> Yes ! >> >> And auto refresh ! >> >> Both of these could be depending on presentation, so that heavy >> presentations can opt out. >> >> >> >> >> > It would be good if there was some visual indication of which > presentations auto-refreshed - like a drop pin looking like its "stuck-in" > when not-auto-refreshing. A user might even be able to change the state of > the pin, with the just the default dependent on type of presentation. > cheers -ben > >

Dec. 10, 2014

Re: [Pharo-dev] About launching tools with Spotter

by Yuriy Tymchuk

I think this should be configurable :) > On 10 Dec 2014, at 19:13, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > well, I vote the contrary: I want âappsâ to show first :P > remember that is not just browsers what we openâ¦. > > Esteban > >> On 10 Dec 2014, at 19:01, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: >> >> >>> On 10 Dec 2014, at 17:52, Damien Cassou <damien.cassou(a)gmail.com> wrote: >>> >>> On Wed, Dec 10, 2014 at 5:09 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>>> But, indeed, it seems that people prefer to have the applications on top and >>>> the rest of the things below. So, a quick fix for this problem is to make >>>> the Menu category come before the classes. >>> >>> >>> but if you open a System Browser, the next step is to search for >>> something in the System Browser. Why would you do that if you can use >>> Spotter to directly search for the thing you want? >>> >>> Same thing for Monticello: spotter makes it apparently easy to commit >>> directly from spotter. So, the main activity is to search for a >>> package in spotter, not for Monticello. >>> >>> So, it looks like packages, classes and methods should come before >>> applications :-) >> >> Yes! +1 >> >>> -- >>> Damien Cassou >>> http://damiencassou.seasidehosting.st >>> >>> "Success is the ability to go from one failure to another without >>> losing enthusiasm." >>> Winston Churchill >>> >> >> > >

Dec. 10, 2014

[pharo-project/pharo-core]

by GitHub

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

Dec. 10, 2014

[pharo-project/pharo-core] 9a8d53: 40410

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: 9a8d53bc6754c8aa06519d2b3fc5d567a3b36a00 https://github.com/pharo-project/pharo-core/commit/9a8d53bc6754c8aa06519d2b… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-10 (Wed, 10 Dec 2014) Changed paths: M ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTInspectorCore.package/ConfigurationOfGTInspectorCore.class/instance/versions/version205_.st M ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGTPlaygroundCore.package/ConfigurationOfGTPlaygroundCore.class/instance/versions/version205_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/symbolic versions/stable_.st A ConfigurationOfGTSpotter.package/ConfigurationOfGTSpotter.class/instance/versions/version101_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/README.md R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/class/accessing/project.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/class/loading/loadDefault.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/class/loading/loadDevelopment.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/class/metacello tool support/isMetacelloConfig.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/class/private/ensureMetacello.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/definition.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/accessing/project.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline20beta1_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline20beta2_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline20beta3_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline20beta4_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline20beta5_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline20beta6_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline21_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline22_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline23_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline24_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline25_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline26_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline27_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline28_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline291_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline292_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/baselines/baseline29_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/snapshot versions/version25snapshot_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/snapshot versions/version26snapshot_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/snapshots/populateSpec_with_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/snapshots/snapshot1.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/snapshots/snapshot2.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/symbolic versions/development_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/symbolic versions/stable_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version206_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version20beta1_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version20beta2_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version20beta3_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version20beta4_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version20beta5_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version20beta6_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version20beta7_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version20beta8_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version21_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version22_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version23_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version24_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version271_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version272_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version273_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version274_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version275_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version276_.st R ConfigurationOfGlamour.package/ConfigurationOfGlamour.class/instance/versions/version27_.st M ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/symbolic versions/stable_.st A ConfigurationOfGlamourCore.package/ConfigurationOfGlamourCore.class/instance/versions/version305_.st M GT-Inspector.package/GTInspector.class/definition.st A GT-Inspector.package/GTInspector.class/instance/accessing/presentationFilter.st M GT-Inspector.package/GTInspector.class/instance/building/compose.st A GT-Inspector.package/GTInspector.class/instance/context/presentationsFilter_.st A GT-Inspector.package/GTInspector.class/instance/context/shouldDisplayPresentationCreateBy_.st A GT-Inspector.package/GTInspector.class/instance/initialization/initialize.st A GT-Inspector.package/GTInspectorMethodListFilterStrategy.class/README.md A GT-Inspector.package/GTInspectorMethodListFilterStrategy.class/definition.st A GT-Inspector.package/GTInspectorMethodListFilterStrategy.class/instance/as yet unclassified/addMethodSignatureFor_.st A GT-Inspector.package/GTInspectorMethodListFilterStrategy.class/instance/as yet unclassified/changeFilterRequestFor_.st A GT-Inspector.package/GTInspectorMethodListFilterStrategy.class/instance/as yet unclassified/initialize.st A GT-Inspector.package/GTInspectorMethodListFilterStrategy.class/instance/as yet unclassified/shouldDisplayPresentationCreateBy_.st A GT-Inspector.package/GTInspectorPragmaFilterStrategy.class/README.md A GT-Inspector.package/GTInspectorPragmaFilterStrategy.class/definition.st A GT-Inspector.package/GTInspectorPragmaFilterStrategy.class/instance/accessing/defaultInspectorPragmaKey_.st A GT-Inspector.package/GTInspectorPragmaFilterStrategy.class/instance/accessing/inspectorPragmasFrom_.st A GT-Inspector.package/GTInspectorPragmaFilterStrategy.class/instance/adding/addPragmaKey_.st A GT-Inspector.package/GTInspectorPragmaFilterStrategy.class/instance/as yet unclassified/changeFilterRequestFor_.st A GT-Inspector.package/GTInspectorPragmaFilterStrategy.class/instance/initialization/initialize.st A GT-Inspector.package/GTInspectorPragmaFilterStrategy.class/instance/testing/shouldDisplayPresentationCreateBy_.st A GT-Inspector.package/GTInspectorPresentationFilterStrategy.class/README.md A GT-Inspector.package/GTInspectorPresentationFilterStrategy.class/definition.st A GT-Inspector.package/GTInspectorPresentationFilterStrategy.class/instance/accessing/changeFilterRequestFor_.st A GT-Inspector.package/GTInspectorPresentationFilterStrategy.class/instance/testing/shouldDisplayPresentationCreateBy_.st M GT-Inspector.package/GTObjectVariablesBrowser.class/instance/private building/stringWithoutInitialCommentFrom_.st M GT-Inspector.package/extension/Object/instance/gtInspectorMetaIn_.st M GT-Inspector.package/extension/Object/instance/gtInspectorPresentationsIn_inContext_.st M GT-Inspector.package/extension/Object/instance/gtInspectorRawIn_.st A GT-InspectorExtensions-Core.package/extension/Pragma/instance/gtDisplayOn_.st M GT-Playground.package/GTPlayPage.class/instance/accessing/publishUrl.st M GT-Spotter.package/GTSpotterDropDownMorph.class/instance/accessing/spotterModel_.st A GT-Spotter.package/GTSpotterDropDownMorph.class/instance/as yet unclassified/buildPane_.st M GT-Spotter.package/GTSpotterDropDownMorph.class/instance/event handling/onStepAdded_.st R GT-Spotter.package/GTSpotterStepPane.class/README.md R GT-Spotter.package/GTSpotterStepPane.class/definition.st R GT-Spotter.package/GTSpotterStepPane.class/instance/accessing/resultsBrick.st R GT-Spotter.package/GTSpotterStepPane.class/instance/accessing/resultsBrick_.st R GT-Spotter.package/GTSpotterStepPane.class/instance/accessing/stepModel.st R GT-Spotter.package/GTSpotterStepPane.class/instance/accessing/stepModel_.st R GT-Spotter.package/GTSpotterStepPane.class/instance/as yet unclassified/initialize.st R GT-Spotter.package/GTSpotterStepPane.class/instance/instance creation/newResultsBrick.st M GT-Spotter.package/GTSpotterStepsBreadcrumb.class/instance/geometry/glmAnimateBrickBounds_duration_callback_.st M GT-Spotter.package/GTSpotterStepsBreadcrumb.class/instance/geometry/scrollToTheLastOne.st M GT-Spotter.package/GTSpotterWidgetThemer.class/instance/styles/closeButtonStyleFor_.st M GT-SpotterExtensions-Core.package/extension/GTSpotter/instance/spotterImplementorsFor_.st R Glamour-Morphic-Brick.package/GLMBandBrick.class/instance/as yet unclassified/doLayout.st R Glamour-Morphic-Brick.package/GLMBandBrick.class/instance/as yet unclassified/layoutChildren.st A Glamour-Morphic-Brick.package/GLMBandBrick.class/instance/layout brick/doLayout.st A Glamour-Morphic-Brick.package/GLMBandBrick.class/instance/layout brick/layoutChildren.st A Glamour-Morphic-Brick.package/GLMBrickHorizontalFillLayout.class/README.md A Glamour-Morphic-Brick.package/GLMBrickHorizontalFillLayout.class/definition.st A Glamour-Morphic-Brick.package/GLMBrickHorizontalFillLayout.class/instance/as yet unclassified/boundsOf_in_withArguments_.st A Glamour-Morphic-Brick.package/GLMBrickHorizontalFillLayout.class/instance/layouting/layout_in_.st M Glamour-Morphic-Brick.package/GLMGeneralScrollPaneBrick.class/instance/initialization/initialize.st M Glamour-Morphic-Brick.package/GLMGeneralScrollPaneBrick.class/instance/layouting/doLayout.st A Glamour-Morphic-Brick.package/GLMHorizontalBandBrick.class/README.md A Glamour-Morphic-Brick.package/GLMHorizontalBandBrick.class/definition.st A Glamour-Morphic-Brick.package/GLMHorizontalBandBrick.class/instance/geometry/width.st A Glamour-Morphic-Brick.package/GLMHorizontalBandBrick.class/instance/initialization/initialize.st A Glamour-Morphic-Brick.package/GLMHorizontalBandBrick.class/instance/layout brick/doLayout.st A Glamour-Morphic-Brick.package/GLMHorizontalBandBrick.class/instance/layout brick/layoutChildren.st A Glamour-Morphic-Brick.package/GLMHorizontalScrollPaneBrick.class/README.md A Glamour-Morphic-Brick.package/GLMHorizontalScrollPaneBrick.class/definition.st A Glamour-Morphic-Brick.package/GLMHorizontalScrollPaneBrick.class/instance/as yet unclassified/calculateMaxVelocity.st A Glamour-Morphic-Brick.package/GLMHorizontalScrollPaneBrick.class/instance/initialization/initialize.st A Glamour-Morphic-Brick.package/GLMHorizontalScrollPaneBrick.class/instance/instance creation/newBand.st A Glamour-Morphic-Brick.package/GLMHorizontalScrollPaneBrick.class/instance/scrolling/scrollDown_.st A Glamour-Morphic-Brick.package/GLMHorizontalScrollPaneBrick.class/instance/scrolling/scrollTo_.st A Glamour-Morphic-Brick.package/GLMHorizontalScrollPaneBrick.class/instance/scrolling/scrollUp_.st A Glamour-Morphic-Brick.package/GLMMorphBrick.class/instance/as yet unclassified/brickBounds_.st M Glamour-Morphic-Brick.package/GLMMorphBrick.class/instance/as yet unclassified/doLayout.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/README.md R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/definition.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/accessing/antialiasing.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/accessing/antialiasing_.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/accessing/isRoundedLeft.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/accessing/isRoundedLeft_.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/accessing/isRoundedRight.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/accessing/isRoundedRight_.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/drawing/drawCircle_position_on_color_antialiasing_.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/drawing/drawMorphicCircle_position_on_color_.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/drawing/drawTrachelCanvas_at_on_.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/drawing/drawTrachelCircle_position_on_color_.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/initialization/initialize.st R Glamour-Morphic-Brick.package/GLMRoundButtonBrickRenderer.class/instance/rendering/renderColorOf_on_.st M Glamour-Morphic-Brick.package/GLMScrollListBrick.class/class/as yet unclassified/exampleCollection.st M Glamour-Morphic-Brick.package/GLMScrollListBrick.class/instance/accessing/calculateMaxVelocity.st M Glamour-Morphic-Brick.package/GLMScrollListBrick.class/instance/scrolling/scrollDown_.st M Glamour-Morphic-Brick.package/GLMScrollPaneBrick.class/class/as yet unclassified/example.st M Glamour-Morphic-Pager.package/GLMPagerScrollBrick.class/instance/api/pushPane_.st M Glamour-Morphic-Pager.package/GLMPagerScrollBrick.class/instance/scrolling/glmAnimateValue_duration_callback_.st M Glamour-Morphic-Pager.package/GLMPagerScrollBrick.class/instance/scrolling/scrollTo_smooth_callback_.st M Glamour-Morphic-Pager.package/GLMPagerScrollBrick.class/instance/scrolling/updatePanes.st M Glamour-Morphic-Pager.package/GLMPagerScrollSlidingMorph.class/instance/scrolling/scrollTo_smooth_.st M Glamour-Morphic-Renderer.package/GLMMorphicAccumulatorRenderer.class/instance/rendering/render_.st M Glamour-Morphic-Renderer.package/GLMMorphicDropDownRenderer.class/instance/as yet unclassified/render_.st M Glamour-Morphic-Renderer.package/GLMMorphicListingRenderer.class/instance/rendering/render_.st M Glamour-Morphic-Renderer.package/GLMMorphicRubricTextRenderer.class/instance/rendering/render_.st M Glamour-Morphic-Renderer.package/GLMMorphicTextRenderer.class/instance/rendering/render_.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script410.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40410.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40410 14598 Spotter version 1.0.1 https://pharo.fogbugz.com/f/cases/14598 14597 GTools 2.0.5 https://pharo.fogbugz.com/f/cases/14597 http://files.pharo.org/image/40/40410.zip

Dec. 10, 2014

Re: [Pharo-dev] [ANN] RProjectConnector V1.0

by phil＠highoctane.be

Excellent. Of course, I want to participate! Le 8 dÃ©c. 2014 15:12, "Blondeau Vincent" <vincent.blondeau(a)worldline.com> a Ã©crit : > Hello everyone, > > > > I am glad to announce the first version of the RProjectConnector, a > binding between Pharo and R using NativeBoost. > > > > You can now call directly your R methods from Pharo: > > data := (1 to: 1000) collect: #yourself. > > res := (#acf asRFunctionWith: {data}) eval > > > > To use it, you should copy the R libraries near the Pharo VM (see the > documentation on SmalltalkHub to see how to proceed) and > > Gofer it > > smalltalkhubUser: 'VincentBlondeau' project: 'RProjectConnector'; > > configuration; > > loadStable > > Donât forget to relaunch Pharo after the installation to be able to use > the connector. > > > > The sources are available on Smalltalkhub: > > http://smalltalkhub.com/#!/~VincentBlondeau/RProjectConnector > > > > if you want to participate, just ask me! > > > > Cheers, > > > > Vincent BLONDEAU > > ------------------------------ > > Ce message et les piÃ¨ces jointes sont confidentiels et rÃ©servÃ©s Ã l'usage > exclusif de ses destinataires. Il peut Ã©galement Ãªtre protÃ©gÃ© par le secret > professionnel. Si vous recevez ce message par erreur, merci d'en avertir > immÃ©diatement l'expÃ©diteur et de le dÃ©truire. L'intÃ©gritÃ© du message ne > pouvant Ãªtre assurÃ©e sur Internet, la responsabilitÃ© de Worldline ne pourra > Ãªtre recherchÃ©e quant au contenu de ce message. Bien que les meilleurs > efforts soient faits pour maintenir cette transmission exempte de tout > virus, l'expÃ©diteur ne donne aucune garantie Ã cet Ã©gard et sa > responsabilitÃ© ne saurait Ãªtre recherchÃ©e pour tout dommage rÃ©sultant d'un > virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive this > e-mail in error, please notify the sender immediately and destroy it. As > its integrity cannot be secured on the Internet, the Worldline liability > cannot be triggered for the message content. Although the sender endeavours > to maintain a computer virus-free network, the sender does not warrant that > this transmission is virus-free and will not be liable for any damages > resulting from any virus transmitted. >

Dec. 10, 2014

Re: [Pharo-dev] About launching tools with Spotter

by Esteban Lorenzano

well, I vote the contrary: I want âappsâ to show first :P remember that is not just browsers what we openâ¦. Esteban > On 10 Dec 2014, at 19:01, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > >> On 10 Dec 2014, at 17:52, Damien Cassou <damien.cassou(a)gmail.com> wrote: >> >> On Wed, Dec 10, 2014 at 5:09 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >>> But, indeed, it seems that people prefer to have the applications on top and >>> the rest of the things below. So, a quick fix for this problem is to make >>> the Menu category come before the classes. >> >> >> but if you open a System Browser, the next step is to search for >> something in the System Browser. Why would you do that if you can use >> Spotter to directly search for the thing you want? >> >> Same thing for Monticello: spotter makes it apparently easy to commit >> directly from spotter. So, the main activity is to search for a >> package in spotter, not for Monticello. >> >> So, it looks like packages, classes and methods should come before >> applications :-) > > Yes! +1 > >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Success is the ability to go from one failure to another without >> losing enthusiasm." >> Winston Churchill >> > >

Dec. 10, 2014

Re: [Pharo-dev] About launching tools with Spotter

by Sven Van Caekenberghe

> On 10 Dec 2014, at 17:52, Damien Cassou <damien.cassou(a)gmail.com> wrote: > > On Wed, Dec 10, 2014 at 5:09 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> But, indeed, it seems that people prefer to have the applications on top and >> the rest of the things below. So, a quick fix for this problem is to make >> the Menu category come before the classes. > > > but if you open a System Browser, the next step is to search for > something in the System Browser. Why would you do that if you can use > Spotter to directly search for the thing you want? > > Same thing for Monticello: spotter makes it apparently easy to commit > directly from spotter. So, the main activity is to search for a > package in spotter, not for Monticello. > > So, it looks like packages, classes and methods should come before > applications :-) Yes! +1 > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without > losing enthusiasm." > Winston Churchill >

Dec. 10, 2014

Re: [Pharo-dev] About launching tools with Spotter

by Damien Cassou

On Wed, Dec 10, 2014 at 5:09 PM, Tudor Girba <tudor(a)tudorgirba.com> wrote: > But, indeed, it seems that people prefer to have the applications on top and > the rest of the things below. So, a quick fix for this problem is to make > the Menu category come before the classes. but if you open a System Browser, the next step is to search for something in the System Browser. Why would you do that if you can use Spotter to directly search for the thing you want? Same thing for Monticello: spotter makes it apparently easy to commit directly from spotter. So, the main activity is to search for a package in spotter, not for Monticello. So, it looks like packages, classes and methods should come before applications :-) -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." Winston Churchill

Dec. 10, 2014