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

Re: [Pharo-project] [update 2.0] #20583

by Marcus Denker

On Tue, Mar 5, 2013 at 1:43 AM, Paul DeBruicker <pdebruic(a)gmail.com> wrote: > Camillo Bruni-3 wrote >> >> it is downloaded automatically with the zerconf scripts, otherwise here: >> >> http://files.pharo.org/image/PharoV20.sources >> http://files.pharo.org/image/PharoV20.sources.zip > > > Are the zeroconf scripts different than these: > > http://pharo.gforge.inria.fr/ci/script/ ? > > If so where can I find the zeroconf scripts? > > If not which one of them gets the PharoV20 sources + VM + image? > wget --quiet -O - http://pharo.gforge.inria.fr/ci/script/ciPharo20PharoVM.sh | bash Curl seems to not work anymore, no idea why. Marcus -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

March 5, 2013

[Pharo-project] Public FogBugz Access

by Sean P. DeNigris

I see all the issues are being migrated to FogBugz, which is cool :) What was the resolution to being able to view/search through them without being logged in? Cheers, Sean ----- Cheers, Sean -- View this message in context: http://forum.world.st/Public-FogBugz-Access-tp4673849.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 5, 2013

Re: [Pharo-project] about run tests from nautilus

by Sean P. DeNigris

Camillo Bruni-3 wrote > Now this is what Phexample brings, 10 clicks less per failed assertion. > I want that in 3.0 +1 and love good error messages for free ----- Cheers, Sean -- View this message in context: http://forum.world.st/about-run-tests-from-nautilus-tp4673439p4673846.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 5, 2013

Re: [Pharo-project] [update 2.0] #20583

by Paul DeBruicker

Camillo Bruni-3 wrote > > it is downloaded automatically with the zerconf scripts, otherwise here: > > http://files.pharo.org/image/PharoV20.sources > http://files.pharo.org/image/PharoV20.sources.zip Are the zeroconf scripts different than these: http://pharo.gforge.inria.fr/ci/script/ ? If so where can I find the zeroconf scripts? If not which one of them gets the PharoV20 sources + VM + image? Also the links in the readme.txt are out of date so copying, pasting then running them gives an error in curl. I made an issue here: http://code.google.com/p/pharo/issues/detail?id=7640 Thanks -- View this message in context: http://forum.world.st/update-2-0-20583-tp4673631p4673824.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

March 5, 2013

Re: [Pharo-project] [ANN] Moose 4.7

by phil＠highoctane.be

http://news.ycombinator.com/newest Push the story up! 2013/3/3 Tudor Girba <tudor(a)tudorgirba.com>: > We are happy to announce the Moose Suite version 4.7: > http://moosetechnology.org/download > > What is new: > â¢ Integration of the Roassal visualization engine > â¢ New PetitParser browser with integrated refactorings > â¢ Improved Glamorous Toolkit for Pharo including the Glamorous Inspector and Debugger > â¢ Several features in Glamour including Watcher support (similar to OS X preview) > â¢ Significant improvements in FAMIX > â¢ Improved external VerveineJ parser for Java > â¢ Based on Pharo 1.4 > > A list of issues addressed in this release can be found at: > http://code.google.com/p/moose-technology/issues/list?can=1&q=status=Fixed%… > > Have fun, > The Moose Team

March 4, 2013

[Pharo-project] Inspiration!

by phil＠highoctane.be

Go Pharo, Go! http://lemire.me/blog/archives/2013/03/04/where-are-the-big-problem-jobs/ Phil

March 4, 2013

Re: [Pharo-project] [Nautilus] Slow Package Menu on Mouse Button Right Click + Fix

by Mariano Martinez Peck

Don't forget to sign the license and send it if you didn't do it yet! Best, On Mon, Mar 4, 2013 at 4:50 PM, stephane ducasse <stephane.ducasse(a)free.fr>wrote: > Thanks a lot Mike. > Such contributions are really welcome. We are all working like nuts on so > many things :). > > Stef > > > > Dear Pharoers, > > thank you all for your time and great contributions! > > Here is a quick performance fix for Nautilus. > > In Pharo2.0a #20581 and previous versions, selecting the package menu with > my right mouse button lasts too long; > here is why: > > 95.4% {564ms} NautilusUI(AbstractNautilusUI)>>packageMenuBuilder > 95.4% {564ms} PragmaMenuBuilder class>>withAllPragmaKeywords:model: > 95.4% {564ms} PragmaMenuBuilder>>buildTree > 95.4% {564ms} PragmaMenuBuilder>>collectRegistrations > *90.3%* {534ms} CriticBrowser class>>packagesMenu: > > Solution, only call CriticsBrowser initialization when this exact menu > item is selected. > > CriticsBrowser>>packagesMenu: aBuilder > <nautilusGlobalPackageMenu> > (aBuilder item: #'Critics Browser') > action: [ | packages target env rules | > target := aBuilder model. > packages := OrderedCollection new. > target selectedPackages do: [:p | MCWorkingCopy managersForCategory: p > packageName do: [:package | packages add: package]]. > rules := RBCompositeLintRule allGoodRules. > env := (RBPackageEnvironment new packages: packages ). > self openOnRule: rules onEnvironment: env]; > help: 'Running critics rules on this package'. > > > Maybe there are more > > > -- Mariano http://marianopeck.wordpress.com

March 4, 2013

[Pharo-project] ConfigurationOfSeaside for Pharo 2.0

by Torsten Bergmann

Hi @seaside-dev (CC-ing Pharo list and seaside users list): Pharo 2.0 is upon completion and it would be good to have a working Seaside running on it out of the box using a ConfigurationOfSeaside accessible through the configuration browser. (Aida is also already working this way). What I currently know from own simple tests and postings is that it is basically working on Pharo 2.0 using this load script: https://github.com/renggli/builder/blob/master/scripts/seaside31-pharo2.st and then "Zinc Server" Gofer new squeaksource: 'ZincHTTPComponents'; "package: 'Zinc-HTTP';" package: 'Zinc-Seaside'; load. "Start Zinc" " (ZnZincServerAdaptor port: 8080) codec: GRPharoUtf8Codec new; start. " There are some small issue left in #includesSubString: vs. #includesSubstring: (now in Pharo). I found it in - WAAbstractFileLibrary>>updateRoot:, - WAFormTag>>isInternetExplorer - WARenderContext>>absoluteUrlForResource: Also when one uploads files using config -> files the methods for the uploaded content get generated but not packaged with Monticello for whatever reason. Is there a plan/timeline for having a valid Seaside on top of Pharo available. Creating an updates ConfigurationOfSeaside was also discussed here on the seaside list ... but still not yet realized. We all know time is always an issue - but at least I want to start a dicussion if it is possible (maybe with the help from many using a virtual sprint). Also is there any plan in moving Seaside to SmalltalkHub as well? Since there is now infrastructure for CI ready on Pharo side it could be used for Seaside also. Any comments? If possible respond on "seaside-dev" list so it is discussed on one central place (http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev) Thanks T.

March 4, 2013

Re: [Pharo-project] Android VM builds restored

by stephane ducasse

Thanks for your time Dmitry CogDroid is important for us. Stef On Mar 4, 2013, at 12:29 AM, Dmitry Golubovsky <golubovsky(a)gmail.com> wrote: > Hi, > > The unbundled Android VM builds on new Jenkins have been restored. No > changes in the source codes on my part, and I tried to preserve the > building environment. > > The new download page is at: > > https://ci.inria.fr/pharo-contribution/job/CogDroid/ > > Feel free to download and try it with your images. > > Bundled builds haven't been restored yet, but I am planning to work on > it in the future. > > Thanks. > > -- > Dmitry Golubovsky > > Anywhere on the Web >

March 4, 2013

Re: [Pharo-project] About development on symbolic versions

by stephane ducasse

Thanks dale I should have tried. I will discuss with the CI guru here and probably the > spec for: #'common' version: '1.1-baseline' which is what I'm looking for. I will add that to the book :) > > For the #development symbolic version you can use any version that you'd like (including another symbolic version) so you could do any one of the following: > > development: spec > <symbolicVersion: #'development'> > > spec for: #'common' version: '1.1' > > > development: spec > <symbolicVersion: #'development'> > > spec for: #'common' version: '1.1-baseline' > > > development: spec > <symbolicVersion: #'development'> > > spec for: #'common' version: #stable > > Does that help? > > Dale > > > ----- Original Message ----- > | From: "StÃ©phane Ducasse" <stephane.ducasse(a)inria.fr> > | To: "Pharo-project(a)lists.gforge.inria.fr Development" <Pharo-project(a)lists.gforge.inria.fr> > | Cc: "Dale Henrichs" <dhenrich(a)vmware.com> > | Sent: Sunday, March 3, 2013 1:51:18 AM > | Subject: About development on symbolic versions > | > | Hi dale > | > | for pharo 3.0 alpha I want the following setup. > | > | I want to monitor all the pharo-contribution using jenkins. So is there a > | pattern to make sure that at the same > | time I can load the stable version of the project on 2.0 but the development > | baseline for the 3.0 (which may match the 20 if no change are made)? > | > | for example for XMLParser I have > | > | stable: spec > | <symbolicVersion: #'stable'> > | > | spec for: #'common' version: '1.1'. > | > | > | now what should I write for development? > | > | development: spec > | <symbolicVersion: #'development'> > | > | spec for: #'common' version: ???? > | > | Thanks

March 4, 2013