- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] how do you use scripts?

by phil＠highoctane.be

Esteban, Interesting that cron thing with jobs/. Maybe could we list these patterns as they seem to be pretty generic for those business apps of ours. Phil

Dec. 12, 2014

Re: [Pharo-dev] how do you use scripts?

by Esteban A. Maringolo

Hi Tudor, I'll reply you below. El Fri Dec 12 2014 at 8:15:40 AM, Tudor Girba <tudor(a)tudorgirba.com> escribiÃ³: > - What kind of actions do you put in scripts? > - Configuration expressions (to startup a headless image). - One shot tasks run by cron jobs. - Patching expressions evaluated by CodeImporter > - Do you rely on script files stored on the disk at all? > Absolutely. > - Where do you store your scripts (in one folder, in many folders)? > Setup and configuration scripts in the image directory. Cron task in a jobs/ subdirectory. Updates/Patches in updates/ > - Do you version your scripts? > I do. Using git along the static assets. > - Do you store them in separate files with dedicated names, or tend to put > multiple snippets in one larger file? > Normally it's only one setup file. In the case of cron tasks They can contain parts of the setup and a message send that starts all the actions. - Do you rely on the names of the scripts? > Just for reference. And in the case of cron tasks the file name is static. > - Why do you use a script file and not a class? > I can modify most of the tasks by using a text editor (vim) through ssh. Regards!

Dec. 12, 2014

Re: [Pharo-dev] [squeak-dev] Context release 4 alpha 1

by Chris Muller

Is Context the software formerly known as Spoon? On Tue, Dec 9, 2014 at 7:51 AM, Craig Latta <craig(a)netjam.org> wrote: > > Hoi-- > > I've released Context 4 alpha 1. This one fixes loading errors in > the welcome page, supports remote debugging and process browsing, and > makes Naiad and remote messaging support available as Monticello > packages. Thanks in advance for reporting bugs! > > http://tinyurl.com/pcj59xw (thiscontext.com) > > I'm around on the #context channel on squeak.slack.com for live > discussion. > > > thanks! > > -C > > -- > Craig Latta > netjam.org > +31 6 2757 7177 (SMS ok) > + 1 415 287 3547 (no SMS) > >

Dec. 12, 2014

[pharo-project/pharo-core] f58dbd: 40413

by GitHub

Branch: refs/heads/4.0 Home: https://github.com/pharo-project/pharo-core Commit: f58dbdb415f8f02af91238c1ba1a5af21f9ebb3e https://github.com/pharo-project/pharo-core/commit/f58dbdb415f8f02af91238c1… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2014-12-12 (Fri, 12 Dec 2014) Changed paths: M Nautilus.package/AbstractNautilusUI.class/class/menu/classesMenu_.st M Nautilus.package/AbstractNautilusUI.class/class/menu/packagesMenu_.st M Nautilus.package/AbstractNautilusUI.class/class/menu/sourceCodeMenuExtra_.st M Nautilus.package/AbstractNautilusUI.class/class/shortcuts/buildExtraShortcutsOn_.st M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/forceGenerateInitialize.st M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/generateInitialize.st M Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/runTestsOfGroups_notifying_.st A Nautilus.package/AbstractNautilusUI.class/instance/menus behavior/toggleBytecodes.st M Nautilus.package/AbstractNautilusUI.class/instance/private/runClassTests_notifying_.st M Nautilus.package/AbstractNautilusUI.class/instance/private/runPackagesTestsNotifying_.st M Nautilus.package/AbstractNautilusUI.class/instance/test creation/createTestForClass_.st M Nautilus.package/MethodWidget.class/class/menu/elementsMenu_.st M Nautilus.package/MethodWidget.class/class/shortcuts/buildMethodShortcutsOn_.st M Nautilus.package/PackageTreeNautilusUI.class/instance/private/runPackagesTestsNotifying_.st M NautilusCommon.package/KonamiCodePlugin.class/instance/private/konamiCode.st M NautilusCommon.package/NautilusHistoryEntry.class/instance/protocol/applyTo_.st A NautilusCommon.package/NautilusHistoryEntry.class/instance/protocol/hash.st M NautilusCommon.package/extension/CompiledMethod/instance/correspondingMethods.st M NautilusCommon.package/extension/CompiledMethod/instance/isTestMethod.st M NautilusCommon.package/extension/RGMethodDefinition/instance/correspondingMethods.st A NautilusCommon.package/extension/String/instance/transformSelectorForComparison.st A SUnit-Core.package/TestCase.class/class/testing/isTestCase.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - scripts/script413.st A ScriptLoader40.package/ScriptLoader.class/instance/pharo - updates/update40413.st M ScriptLoader40.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st Log Message: ----------- 40413 14190 Nautilus Refactoring 10: Code-Critics cleanup https://pharo.fogbugz.com/f/cases/14190 14609 Cannot show bytecodes anymore in Nautilus https://pharo.fogbugz.com/f/cases/14609 http://files.pharo.org/image/40/40413.zip

Dec. 12, 2014

[pharo-project/pharo-core]

by GitHub

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

Dec. 12, 2014

Emergency evaluator while loading configuration

by Stephan Eggermont

I'm doing some work on the upcoming Moose 5 release. While loading the configuration I get an emergency evaluator Anyone know what can be causing this? Gofer new smalltalkhubUser: 'Moose' project: 'Moose'; configuration; load. ((Smalltalk at: #ConfigurationOfMoose) project version: #'release5.0') load In a 30860 Stephan

Dec. 12, 2014

GTSpotter sub-item search

by Guillermo Polito

Hi, I was playing with spotter a bit and run into the following idea. I wanted to search for the Configuration Browser. So I type "configuration bro". Of course, nothing appears because it is in the Tools submenu of the World menu. Which I should know if I'm looking for it... But, I thought that maybe it would make sense to show then the "Tools" menu when I type configuration browser. More generally, when the thing I look for is in the sub menu of an item, I show its parent. I found my way and change this method: MenuMorph>>spotterItemsFor: aStep <spotterOrder: 10> ^ aStep listProcessor title: 'Items'; candidatesLimit: Float infinity; allCandidates: [ self items ]; itemName: #contents; itemIcon: [ :item | item icon ]; actLogic: [ :item | item hasSubMenu ifTrue: [ aStep diveIn ] ifFalse: [ item spotterActDefault. aStep exit ] ]; added ==> matchLogic: [ :item :string | item hasSubMenu ifFalse: [ (string, '*') match: item contents ] ifTrue: [ item subMenu allItems anySatisfy: [ :sub | (string, '*') match: sub contents ] ]] My question is: Does this behavior make sense to my spotter designer friends? Can it be applied more generally? Then, something I didn't implement but I'd like to have. When a sub-item matches, the shown element should have some visual feedback showing the reason of the selection...

Dec. 12, 2014

Re: [Pharo-dev] (Ring?) Working with 'virtual' code entites

by stepharo

yes you should have a look at Ring on the contribution-pharo there is a JET image it can give you an idea. Stef Le 12/12/14 11:46, Yuriy Tymchuk a Ã©crit : > Hi everyone! > > As you may know Iâm working on code quality/smells/critics. And I want to analyze bigger projects like Moose for example. But Moose works on Pharo3 while my system works on Pharo4. Is is possible to somehow obtain Classes and methods from the repository and perform some analysis on them without installing them in the system? Because in my general workflow I just create a collection of classes like: `packages flatCollect: #definedClasses` and then work with them. > > So any suggestions are welcome :) > > Cheers. > Uko >

Dec. 12, 2014

Re: [Pharo-dev] Slice Integrator Tool

by Marcus Denker

> On 12 Dec 2014, at 14:46, Ben Coman <btc(a)openInWorld.com> wrote: > > Could I get a look at the new slice Integrator tool ? > > I'd like to try pulling some bits into PharoLauncher to assist individuals to review resolved cases. > The CI job is here: https://ci.inria.fr/pharo-contribution/job/Integrator/

Dec. 12, 2014

Slice Integrator Tool

by Ben Coman

Could I get a look at the new slice Integrator tool ? I'd like to try pulling some bits into PharoLauncher to assist individuals to review resolved cases. cheers -ben

Dec. 12, 2014