- Pharo-dev - lists.pharo.org

[Pharo-project] monticello + filesystem performance
by Camillo Bruni Feb. 3, 2013

Feb. 3, 2013

I'm giving a bit more love to my git-exports these days and I see strange anomalies... https://ci.inria.fr/pharo/job/Pharo-2.0-Git-Export/buildTimeTrend Pharo version 20458 and starting from 20463, the export takes a factor 6 longer. I did not investigate further much further, so I will wait until I catch up to the latest Pharo release.

2 1

[Pharo-project] pharo/updates now git tracked
by Camillo Bruni Feb. 3, 2013

Feb. 3, 2013

I fixed the files under http://pharo.gforge.inria.fr/updates/ so that all of them are now tracked in the git repository. now the only thing missing is changing the update process to work on proper branches ;): Currently there is a branch for each pharo-release: 10, 11, 12, 13, 14, 20 - Each update should then be applied to a dev branch which triggers all the tests - after all tests succeed the dev branch is merged into the stable branch by our ci services. The update-process on the ci server is almost ready: - Pharo-2.0-Update-Tracker - Pharo-2.0-Update-Validation - Pharo-2.0-Update-Release What is missing? Get Pharo down to 0 Failing tests :P

1 0

[Pharo-project] updates files
by Camillo Bruni Feb. 2, 2013

Feb. 2, 2013

Can I remove the uncategorized update files fro 1.0 from gforge? http://pharo.gforge.inria.fr/updates/ seems like a part of them is duplicated. The standard location would be http://pharo.gforge.inria.fr/updates/pharo1.0/ no?

2 1

[Pharo-project] [update 2.0] #20507
by Marcus Denker Feb. 2, 2013

Feb. 2, 2013

20507 ----- Issue 7400: BlockClosure #decompile should not reference Decompiler directly http://code.google.com/p/pharo/issues/detail?id=7400 Issue 7392: completion was not working properly http://code.google.com/p/pharo/issues/detail?id=7392 Diff information: http://ss3.gemstone.com/ss/Pharo20/NOCompletion-MarcusDenker.34.diff http://ss3.gemstone.com/ss/Pharo20/NECompletion-MarcusDenker.80.diff http://ss3.gemstone.com/ss/Pharo20/Keymapping-Core-MarcusDenker.140.diff http://ss3.gemstone.com/ss/Pharo20/Compiler-MarcusDenker.371.diff

1 0

[Pharo-project] Please review Issue 7390
by Sean P. DeNigris Feb. 2, 2013

Feb. 2, 2013

Issue 7390: FileDialogWindow answers wrong FileReference for selected file http://code.google.com/p/pharo/issues/detail?id=7390 This one is important because in 20503, directory repositories can not be added via the MC browser. Steps to reproduce: 1. In MC Browser, click +Repository, choose Directory 2. Select a directory in the "File" (right) pane of the directory chooser, and accept Problem: The returned FileReference will be the path to the directory selected in the left pane, with a printString of a FileDirectoryEntry appended to it - i.e. garbage Fix in inbox: SLICE-Issue-7390-FileDialogWindow-answers-wrong-FileReference-for-selected-file-SeanDeNigris.1 - Fix FileDialogWindow>>selectedAnyFileDirectory - return the proper FileReference when a file is selected - Refactor for clarity incl. adding temps - Clean up comment -- View this message in context: http://forum.world.st/Please-review-Issue-7390-tp4667063.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

[Pharo-project] [update 2.0] #20506
by Marcus Denker Feb. 2, 2013

Feb. 2, 2013

20506 ----- Issue 7353: Problem with PickList http://code.google.com/p/pharo/issues/detail?id=7353 Issue 7270: Failing test for RPackageCategorySynchronisationTest http://code.google.com/p/pharo/issues/detail?id=7270 Issue 7399: cleanup uses of Compiler a little http://code.google.com/p/pharo/issues/detail?id=7399 Diff information: http://ss3.gemstone.com/ss/Pharo20/Spec-Widgets-MarcusDenker.90.diff http://ss3.gemstone.com/ss/Pharo20/RPackage-SystemIntegration-MarcusDenker.… http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1297.diff http://ss3.gemstone.com/ss/Pharo20/Compiler-MarcusDenker.369.diff

1 0

[Pharo-project] [update 2.0] #20505
by Marcus Denker Feb. 2, 2013

Feb. 2, 2013

20505 ----- Issue 7372: Deadcode http://code.google.com/p/pharo/issues/detail?id=7372 Issue 7352: Changing a superclass removes the Class from the superclass subclasses http://code.google.com/p/pharo/issues/detail?id=7352 Diff information: http://ss3.gemstone.com/ss/Pharo20/Network-Url-MarcusDenker.84.diff http://ss3.gemstone.com/ss/Pharo20/Network-Kernel-MarcusDenker.85.diff http://ss3.gemstone.com/ss/Pharo20/Monticello-MarcusDenker.750.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-MarcusDenker.1295.diff

1 0

Re: [Pharo-project] [squeak-dev] Re: [vwnc] Does anyone have a "new" string literal?
by Eliot Miranda Feb. 2, 2013

Feb. 2, 2013

On Fri, Feb 1, 2013 at 10:44 AM, Colin Putney <colin(a)wiresong.com> wrote: > > > > On Fri, Feb 1, 2013 at 10:28 AM, Eliot Miranda <eliot.miranda(a)gmail.com>wrote: > > >> David Leibs has been pushing a well-thought-through facility he calls >> (and other systems name) "quasi-quote". Here, a string literal contains >> escape sequences, a little like printf, that allow one to substitute >> values. Dave's syntax uses square brackets to escape into Smalltalk. >> > > That's certainly a useful construct, but I don't think it addresses > Terry's problem. He wants a string literal that can include $' and CR > without escaping. Something like HEREDOC or Python's triple-double-quote > string literals. > If I had a brain I would have remembered the syntax and hence that it does address Terry's point. The quote character for quasi-quote is ` (back tick), so single ticks are literal inside a quasi-quote. <blush>Sorry</blush> > > Colin > > > > -- best, Eliot

2 1

Re: [Pharo-project] I hate 'as yet unclassified'
by Fernando Olivero Feb. 1, 2013

Feb. 1, 2013

Hi, i think i found a hint on the questions posed in this thread: why the Smalltalk tools moved from "protocols" to "categories". Maybe it happened when Morphic took over MVC? Because the term categories is used in SELF, look at the outliner in the attached image. Morphic originally was included in SELF, and later ported to Smalltalk. Fernando On Thu, Jan 31, 2013 at 12:28 PM, S Krish <krishnamachari.sudhakar(a)gmail.com > wrote: > > Auto categorization in the old browser: " Categorize all uncategorized " > had simple rules especially overridden methods / known methods in their > known categories.. > > That would help greatly for most developers, more so the beginners to get > a good feel of recommended categorization. > > But can auto categorization cause wrong labeling may need to weighed, > better to leave it uncategorized in that case. > > > **************** > PS: At work on a VAGE code, I was pointing to the exact same issue of > missing categorization over last many years..!.. The lack of categorization > limits comprehension of the codebase... especially of code built over 20 > yrs. > > > > On Thursday, January 31, 2013, Camillo Bruni wrote: > > On 2013-01-31, at 03:53, Ben Coman <btc(a)openInWorld.com> wrote: > > > > > Camillo Bruni wrote: > >> I was just waiting for the google issue tracker to come back to life... > >> > >> https://code.google.com/p/pharo/issues/detail?id=7373 > >> > >> => Slice in Inbox > >> > >> the major problem I have now, is that wrong categorizations might > easily spread :P, the sepll-fleu and the space - vi rus, are very common... > >> > >> > > > > Can the auto-categorization mark such methods as "auto-categorized" ? > So that later if it doesn't seem quite right, a human can make a better > judgment rather than assuming someone else had already made such a judgment > for some-good-reason. In reality perhaps such re-categorization wouldn't > happen a lot, but "being at least able to" make such judgment increases > confidence in the system, which can be subtly undermined by automated tools > (and anyway I hate throwing away information that is easily available at > the time). This wouldn't need any tool support straight away, but at least > the data is captured for later use. > > the categorization will happen only upon user interaction. > hence I think such a control is not needed directly. > Feel free to extend the current classifier to support it, the code is > fairly simple.. >

1 0

[Pharo-project] [ANN]: SimplePersistence 2.0 - now with fuel!
by Sean P. DeNigris Feb. 1, 2013

Feb. 1, 2013

Simple Image-based Persistence Based on the idea that - most applications will not have to scale (i.e. become the next Twitter) - simply saving the image is slow and error-prone. For the full motivation and description, see Ramon Leon's blog post at http://onsmalltalk.com/simple-image-based-persistence-in-squeak/. I pretty much just packaged up the code from Ramon's blog, made some small refactorings, and confirmed it was MIT. New in version 2.0 - Uses Fuel instead of ReferenceStream for the serialization - Loads and tests passing in Pharo 1.4 and 2.0 (would probably work in Squeak, but depends on FileSystem) Gofer new url: 'http://ss3.gemstone.com/ss/SimplePersistence'; package: 'ConfigurationOfSimplePersistence'; load. "load: 'ALL' = load the tests. If you don't want them, send #load" (Smalltalk at: #ConfigurationOfSimplePersistence) project development load: 'ALL'. -- View this message in context: http://forum.world.st/ANN-SimplePersistence-2-0-now-with-fuel-tp4667114.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0