April 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] In-Image Documentation Dashboard

by Sean P. DeNigris

Sean P. DeNigris wrote > DocumentationPlugin Should work in Pharo 2.0 and 3.0. ----- Cheers, Sean -- View this message in context: http://forum.world.st/In-Image-Documentation-Dashboard-tp4679472p4679473.ht… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 3, 2013

[Pharo-project] In-Image Documentation Dashboard

by Sean P. DeNigris

We have so many cool mechanisms for in-image and external documentation now that I sometimes get confused! I considered a rant, but figured it'd be just as easy to write a plugin for Nautilus (thanks to Ben) ;) It gives you two buttons: - "Browse Tests", which becomes enabled when there are test methods in the image that reference the selected class - "Browse Help", which becomes enabled if there is a CustomHelp subclass in a category similar to the selected category (i.e. the package names match up to the first $-) Limitations: I hacked this together to scratch an itch, so I'm sure there are many. For instance: - it does not look in test helper methods, only #testSelectors. - I think I remember HelpSystem also allowing pragmas, so the logic may have to be extended It's a nice visual reminder that documentation may be available, with easily accessible links thereto. Gofer new repository: 'http://ss3.gemstone.com/ss/PharoSpd'; package: 'ConfigurationOfPharoSpd'; load. (Smalltalk at: #ConfigurationOfPharoSpd) project bleedingEdge load: #('NautilusSpd'). Then enable DocumentationPlugin e.g. "Nautilus pluginClasses addLast: { DocumentationPlugin. #bottom }" p.s. if there is not a better way to programmatically enable a plugin, we should add that ;) p.p.s. if you load the 'IDE' group instead of 'NautilusSpd', you will get some unrelated but useful enhancements like Nautilus context menu items for adding boilerplate for new Spec UI's and adding custom attributes to Metacello configurations. They handle a few common cases in my personal development - use at your own risk... ----- Cheers, Sean -- View this message in context: http://forum.world.st/In-Image-Documentation-Dashboard-tp4679472.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 3, 2013

[Pharo-project] SystemNavigation API: browseAllXyz vs. browseAbc

by Sean P. DeNigris

Some selectors are of the form browseAllXyz (e.g. browseAllSendersOf:), while others are like browseAbc (e.g. browseSendersOf:name:autoSelect:) The "All"s seem extraneous. If the thing being browsed is plural (e.g. Senders instead of sender), that implies "All" since there are no other qualifiers, and there's no alternate case unlike subclasses v.s. allSubclasses. ----- Cheers, Sean -- View this message in context: http://forum.world.st/SystemNavigation-API-browseAllXyz-vs-browseAbc-tp4679… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 3, 2013

Re: [Pharo-project] The ultimate SmalltalkHub migration script

by stephane ducasse

Thanks Damien!!! Stef On Apr 3, 2013, at 11:03 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > I've just used the following scripts to copy many of Lukas' repositories to SmalltalkHub. > > | source goSource destination goDestination files destinationFiles | > > source := MCHttpRepository location: 'http://source.lukas-renggli.ch/pier2addons'. > destination := MCSmalltalkhubRepository owner: 'Pier' project: 'Pier2Addons' user: 'DamienCassou' password: 'XXXXXX'. > > goSource := Gofer new repository: source. > goDestination := Gofer new repository: destination. > > files := source allVersionNames. > > (goSource allResolved select: [ :resolved | files anySatisfy: [ :each | resolved name = each ] ]) do: [ :each | goSource package: each packageName ]. > > goSource fetch. "downloads all mcz on your computer" > > destinationFiles := destination allVersionNames. "checks what files are already at destination" > files reject: [ :file | destinationFiles includes: file ] thenDo: [ :file | goDestination version: file ]. "selects only the mcz that are not yet at destination" > > goDestination push. "sends everything to SmalltalkHub" > > self assert: destination allVersionNames sorted = files sorted. "checks we have exactly the same files at source and destination" > > > > -- > Damien Cassou > http://damiencassou.seasidehosting.st > > "Success is the ability to go from one failure to another without losing enthusiasm." > Winston Churchill

April 3, 2013

Re: [Pharo-project] Pharo Vision is becoming reality

by stephane ducasse

On Apr 1, 2013, at 5:54 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Out of the 14 action items laid out in the 5 year vision, /over half now > exist one year later/ in the 2.0 release! > > Here's the current progress (corrections/updates welcome): > > In 2.0: > 2a Rewrite of Filesystem > 7 Packages as real objects (RPackage) we should continue on that front - less bugs - remove package info - offer new versionner tools supporting key process patterns and generation of configuration - change RPackage used as categories to real package (and get rid of category) + save package tag in monticello metadata > 8 Package Meta-Data (manifest classes) > 9 Less Model Clutter and Duplication (Ring) we should continue to remove pseudo classes and others > 10 Building and Reusing UI Logic (Spec) we should have a painter > 11 New Network Layer (Zinc/Zodiac) > 12 Serializers (Fuel) > 13 System Change Notifier replacement (SystemAnnouncer) - continue to polish that > For 3.0 [1]: > 6 Fully parametrized compiler tool chain (this means Opal, right?) - not really - when Opal is in the image we can continue. systemNavigation (is taking an environment as input), test runner should be parametrized > 1 A Robust and Extensible System Events (guessing this is event model from > [1]) we should continue to push the work we did to clean the systemevents > 2b Rewrite of Streams > 4 UI Canvas for Zoomable Interfaces (I'm assuming this is part of Athens?) Yes > > In progress (deadline unclear) > 3 Announcements and Ephemerons > 5 Bootstrap of the Core This is done but we should now have the complete process building from the core. > 14 Cleaning Morphic > > [1] http://forum.world.st/Pharo-3-td4677109.html > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Pharo-Vision-is-becoming-reality-tp4679202.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

April 3, 2013

Re: [Pharo-project] how to load from STHub at #pharoconf

by Sean P. DeNigris

Sven Van Caekenberghe-2 wrote > I updated the Getting Started Workspace: > > http://ws.stfx.eu/1WS4U > > to reflect the existence of the ConfigurationOfSharedWorkspace. It takes a village :) ----- Cheers, Sean -- View this message in context: http://forum.world.st/how-to-load-from-STHub-at-pharoconf-tp4679416p4679438… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

April 3, 2013

Re: [Pharo-project] how to load from STHub at #pharoconf

by Sven Van Caekenberghe

I updated the Getting Started Workspace: http://ws.stfx.eu/1WS4U to reflect the existence of the ConfigurationOfSharedWorkspace. On 03 Apr 2013, at 16:39, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > > On 03 Apr 2013, at 16:22, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > >> Tudor Girba-2 wrote >>> Indeed, much better. I keep on forgetting that :). >> >> Me too! Really cool service :) I just made a config and uploaded to sqs and >> ss3/meta...for...20 >> >> Gofer it >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfSharedWorkspace'; >> load. >> >> (or load via the configuration browser) > > Hey Sean, > > Thanks a lot: this was on my todo list, but I kept not doing it ! > It is really important to be able to load stuff with one click. > > Sven > >> n.b. I didn't address Sven's note to update Zinc on 1.4 > > That is not really necessary, it is from long ago. > It is also good that you did not put in a full Zn dependency. > >> ----- >> Cheers, >> Sean >> -- >> View this message in context: http://forum.world.st/how-to-load-from-STHub-at-pharoconf-tp4679416p4679426… >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > -- > Sven Van Caekenberghe > http://stfx.eu > Smalltalk is the Red Pill > > --- > Proud supporter of Pharo > http://consortium.pharo.org > >

April 3, 2013

Re: [Pharo-project] Where to report Pharo Metacello issues

by stephane ducasse

better Metacello Stef On Apr 3, 2013, at 4:10 PM, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > MetacelloToolBox > createBaseline: '1.0-baseline' > for: 'MyProject' "Project name" > repository: 'http://squeaksource.com/MyRepo' > requiredProjects: #() > packages: #('MyPackage') > repositories: #() > dependencies: { } > groups: { }. > > creates a configuration class named MyProject instead of > ConfigurationOfMyProject. Do I make a Pharo issue or report to MetaC? > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/Where-to-report-Pharo-Metacello-issues-tp4679424.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

April 3, 2013

[Pharo-project] [update 3.0] #30021

by Marcus Denker

30021 ----- 10193 newRow: #methods bottom: 0.5 https://pharo.fogbugz.com/f/cases/10193 10121 do #cleanUpForRelease on every update https://pharo.fogbugz.com/f/cases/10121 Diff information: http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/UpdateStreamer-Core-MarcusDe… http://smalltalkhub.com/#!/~Pharo/Pharo30/diff/Spec-Layout-MarcusDenker.38

April 3, 2013

Re: [Pharo-project] how to load from STHub at #pharoconf

by Sven Van Caekenberghe

On 03 Apr 2013, at 16:22, "Sean P. DeNigris" <sean(a)clipperadams.com> wrote: > Tudor Girba-2 wrote >> Indeed, much better. I keep on forgetting that :). > > Me too! Really cool service :) I just made a config and uploaded to sqs and > ss3/meta...for...20 > > Gofer it > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfSharedWorkspace'; > load. > > (or load via the configuration browser) Hey Sean, Thanks a lot: this was on my todo list, but I kept not doing it ! It is really important to be able to load stuff with one click. Sven > n.b. I didn't address Sven's note to update Zinc on 1.4 That is not really necessary, it is from long ago. It is also good that you did not put in a full Zn dependency. > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/how-to-load-from-STHub-at-pharoconf-tp4679416p4679426… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. -- Sven Van Caekenberghe http://stfx.eu Smalltalk is the Red Pill --- Proud supporter of Pharo http://consortium.pharo.org

April 3, 2013