September 2015 - Pharo-users

Trying DynaCASE in Pharo 5

by HernÃ¡n Morales Durand

Hello, I'm trying DynaCASE modeling platform in latest Pharo 5 installing with the following script: Metacello new baseline: 'DynaCASE'; repository: 'github://dynacase/dynacase/repository'; load. When I click both DC Finite State Machine -> FSM Example Divisibility DC Finite State Machine -> FSM Example Decimal I get MessageNotUnderstood: receiver of "handlesAnnouncement:" is nil So my question is how should I install DynaCASE to get a functional version? Cheers, HernÃ¡n

Sept. 22, 2015

Re: [Pharo-users] A keyboard controlled code editor, how difficult would that be?

by Peter UhnÃ¡k

> I made it work nicer with the dark theme. Thanks! > Anyone know how to get a good result for the package name that > is shown above the method name? Nautilus is using this for extension methods (interestingly it ignores Theme, but it works for both) ~~~~~~~~~~~~~~~~~~~~~~~~~~~ AbstractNautilusUI>>extensionColor ^ Color gray darker ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Could it be also added to the world menu? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ CodePanel>>menuCommandOn: aBuilder <worldMenu> (aBuilder item: #CodePanel) order: 0; "something meaningful, perhaps not the first one" parent: #MostUsedTools; action: [ self new openInWindow ] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Peter

Sept. 22, 2015

Re: [Pharo-users] DesktopManager in Pharo 5 - Video

by Tudor Girba

You should :) Doru On Tue, Sep 22, 2015 at 4:01 AM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Damn...so super cool that I want to use 5.0 grrrrrr > > On Mon, Sep 21, 2015 at 11:38 AM, Alexandre Bergel < > alexandre.bergel(a)me.com> wrote: > >> +1 >> >> Alexandre >> >> >> > On Sep 21, 2015, at 11:15 AM, Tudor Girba <tudor(a)tudorgirba.com> wrote: >> > >> > The Spotter integration is really cool. >> > >> > Cheers, >> > Doru >> > >> > On Mon, Sep 21, 2015 at 3:30 PM, Torsten Bergmann <astares(a)gmx.de> >> wrote: >> > https://www.youtube.com/watch?t=118&v=zpLY7uQnPsg >> > >> > >> > >> > >> > -- >> > www.tudorgirba.com >> > >> > "Every thing has its own flow" >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> >> > > > -- > Mariano > http://marianopeck.wordpress.com > -- www.tudorgirba.com "Every thing has its own flow"

Sept. 22, 2015

Re: [Pharo-users] Exploring Pier

by Jimmie Houchin

I know there are options to Pier. To a certain extent part of the purpose of my email was to explore whether or not Pier is a viable option and if it has community support that I am not easily seeing. I want to stick with reasonably well supported options. I thought the cms and blog parts of Pier looked interesting. This is all personal and not for business or public. I definitely want to learn Pillar as it is required if at some point I want to contribute to any of the documentation. And it looks like a pretty powerful tool. I do not have any clearly defined goals which make Pier a requirement. The blog and cms like features are possibly reasonably implementable in the more currently supported options. And those are simply things I am exploring not requiring. It seems that Doru possibly uses it on the http://www.humane-assessment.com/blog site. Thanks. Jimmie On 09/22/2015 02:38 AM, Damien Cassou wrote: > Hi, > > Jimmie Houchin <jlhouchin(a)gmail.com> writes: > >> I am interested in learning to use Pier. I browsed the mailing list to >> learn about current status and documentation. It seems to be pretty >> quiet on the mailing lists. >> >> There seems to be some activity on Smalltalkhub on Pier3. > > Pillar, the document model and parser of Pier is alive. I need help but > the project is definitely not dead as we use it for all books we are > writing. > > The rest of Pier, mainly the web interface, looks rather dead for me as > well. > > Why are you interested in Pier? We might help you find other projects > that could suit your needs. >

Sept. 22, 2015

Re: [Pharo-users] Adding a #development version of a Git project in the catalog

by Damien Cassou

Dale Henrichs <dale.henrichs(a)gemtalksystems.com> writes: > On 09/21/2015 10:46 AM, Dale Henrichs wrote: >> >> >> On 09/21/2015 06:31 AM, Damien Cassou wrote: >>> Yuriy Tymchuk <yuriy.tymchuk(a)me.com> writes: >>> >>>> Can you simply define symbolic version as a normal one? >>> >>> when I tried I got an error message. Metacello was trying to parse >>> 'development' as a semantic version number >> You can implement #versionNumberClass in your configuration or >> baseline to switch version number parser to MetacelloVersionNumber >> which is less picky:) >> >> versionNumberClass >> ^ MetacelloVersionNumber > So using MetacelloVersionNumber does look like you can define the > following version: > > versionDev: spec > <version: 'dev'> > spec > for: #'common' > do: [ > spec > baseline: 'Jenkins' > with: [ spec repository: > 'github://DamienCassou/pharo-jenkins:master/src' ]; > import: 'Jenkins' ] > > and then use a standard symbolic version definition: > > development: spec > <symbolicVersion: #'development'> > spec for: #'common' version: 'dev' thank you very much, it helped me a lot. -- Damien Cassou http://damiencassou.seasidehosting.st "Success is the ability to go from one failure to another without losing enthusiasm." --Winston Churchill

Sept. 22, 2015

Re: [Pharo-users] Integrating a custom spotter, reusing current code

by Stephan Eggermont

On 22-09-15 14:02, Peter UhnÃ¡k wrote: >> Also, how do I get to a list >> of the implementers/senders/references/etc of the method/class? >> What is the improved and approved way to do this :) ? > > do you mean sending them #senders and #implementors? Or am I missing something? No, how do I get a spotter morph showing the implementors so I can choose one. Without duplicating too much. Stephan

Sept. 22, 2015

Re: [Pharo-users] Integrating a custom spotter, reusing current code

by Thierry Goubier

2015-09-22 14:02 GMT+02:00 Peter UhnÃ¡k <i.uhnak(a)gmail.com>: > > Also, how do I get to a list > > of the implementers/senders/references/etc of the method/class? > > What is the improved and approved way to do this :) ? > > do you mean sending them #senders and #implementors? Or am I missing > something? > > aCompiledMethod senders. > (Morph>>#drawOn:) implementors. > Morph allCallsOn. > > This will list everything. Nautilus can also filter it, because it > keeps track of the current scope, but I don't know if this is > abstracted. > Well, implementors refer to SystemNavigation allImplementorsOf:, and SystemNavigation has an environment instance variable which may allow for scoping... Maybe something like anEnvironment asSystemNavigationEnvironment implementorsOf: aCompiledMethod selector The API for scopped use of SystemNavigation is very limited. Maybe because only Nautilus seems to have a use for it? Thierry > > Peter > >

Sept. 22, 2015

Re: [Pharo-users] Integrating a custom spotter, reusing current code

by Peter UhnÃ¡k

> Also, how do I get to a list > of the implementers/senders/references/etc of the method/class? > What is the improved and approved way to do this :) ? do you mean sending them #senders and #implementors? Or am I missing something? aCompiledMethod senders. (Morph>>#drawOn:) implementors. Morph allCallsOn. This will list everything. Nautilus can also filter it, because it keeps track of the current scope, but I don't know if this is abstracted. Peter

Sept. 22, 2015

Integrating a custom spotter, reusing current code

by Stephan Eggermont

In the CodePanel demo, I now managed to add some spotter integration by copy-pasting some code from GTSpotter and adding actLogic. Object subclass: #CardSpotterModel instanceVariableNames: 'panel' classVariableNames: '' category: 'NewUI' CardSpotterModel>>spotterImplementorsFor: aStep <spotterOrder: 10> aStep listProcessor title: 'Implementors'; filter: GTFilterImplementor item: [ :filter :context | SystemNavigation default allBehaviorsDo: [ :class | class methodsDo: filter ] ]; wantsToDisplayOnEmptyQuery: false; actLogic: [:item :step | step exit. panel newCardFor: item] That is used CodeCard>>spotImplementers |model| model := CardSpotterModel on: self panel. GTSpotterMorph new extent: 400@500; doLayout; spotterModel: (GTSpotter on: model); openCenteredInWorld. That is ugly, as it is a duplication. Also, how do I get to a list of the implementers/senders/references/etc of the method/class? What is the improved and approved way to do this :) ? Stephan

Sept. 22, 2015

Re: [Pharo-users] A keyboard controlled code editor, how difficult would that be?

by Stephan Eggermont

On 22-09-15 09:59, phil(a)highoctane.be wrote: > Hi Stephan, > > I made it work nicer with the dark theme. Thanks. I adopted the changes and tuned them to work better with both themes. Anyone know how to get a good result for the package name that is shown above the method name? I need a less prominent variant of the textColor. CodeCard>>packageColor Smalltalk ui theme class = Pharo3Theme ifTrue: [ ^Smalltalk ui theme borderColor ] ifFalse: [ ^Color veryLightGray ] > - the cards aren't picking up changes done elsewhere, nor are they saving > the contents back to the system. Ah, I wanted to use it for a lot of coding > already! Peter is right, no more picking around when focusing on one > interaction. Hmm, I thought I had that working at some moment. I have fought with Rubric a lot the last days, so I probably broke it. Stephan

Sept. 22, 2015