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

[ann] snapshotcello
by Tudor Girba July 25, 2013

July 25, 2013

Hi, Stef and I developed Snapshotcello, a little utility that enables you to freeze a snapshot of a given configuration based on what is already loaded in your current image. The idea is simple. You develop against the latest versions of all packages, and commit your changes for each package. When you are ready for a release, you assemble your image, and generate a snapshot version that can be reloaded later. Here is an example of how it can work to take a snapshot of a development version: Snapshotcello new configurationClass: ConfigurationOfMoose; configurationVersion: #development; publishVersion: '4.8-snapshot' You can find more details here: http://www.tudorgirba.com/blog/snapshotcello-take-a-snapshot-when-you-re-re… You can get the code at: Gofer new smalltalkhubUser: 'girba' project: 'Snapshotcello'; package: 'ConfigurationOfSnapshotcello'; load. (Smalltalk globals at: #ConfigurationOfSnapshotcello) loadDevelopment Cheers, Doru -- www.tudorgirba.com "Every successful trip needs a suitable vehicle."

5 23

[pharo-project/pharo-core]
by GitHub July 25, 2013

July 25, 2013

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

1 0

[pharo-project/pharo-core] e8dc17: 30299
by GitHub July 25, 2013

July 25, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: e8dc17cb1e2f94c6f9802d25be5f5d539505777f https://github.com/pharo-project/pharo-core/commit/e8dc17cb1e2f94c6f9802d25… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-07-25 (Thu, 25 Jul 2013) Changed paths: A FuelTools-Debugger/extension/DebugSession/class/encodeDebugInformationOn_.st A FuelTools-Debugger/extension/DebugSession/class/serializeTestFailureContext_toFileNamed_.st A FuelTools-Debugger/extension/DebugSession/instance/serializeStack.st M FuelTools-Debugger/extension/Debugger/class/encodeDebugInformationOn_.st A FuelTools-Debugger/extension/SpecDebugger/class/menuFuelStackAction_.st A FuelTools-Debugger/extension/SpecDebuggerToolbar/instance/serializeStack.st M Kernel-Methods/ContextPart.cls/instance/debugger access/errorReportOn_.st A ScriptLoader30/ScriptLoader.cls/instance/pharo - scripts/script134.st A ScriptLoader30/ScriptLoader.cls/instance/pharo - updates/update30299.st M ScriptLoader30/ScriptLoader.cls/instance/public/commentForCurrentUpdate.st M Spec-Debugger/SpecDebugger.cls/class/menu/menuStackAction_.st M Spec-Debugger/SpecDebugger.cls/class/menu/menuStack_.st Log Message: ----------- 30299 11239 ContextPart>>errorReportOn: uses deprecated methods https://pharo.fogbugz.com/f/cases/11239 11232 Fuel out stack menu entry is missing https://pharo.fogbugz.com/f/cases/11232

1 0

[update 3.0] #30299
by Marcus Denker July 25, 2013

July 25, 2013

30299 ----- 11239 ContextPart>>errorReportOn: uses deprecated methods https://pharo.fogbugz.com/f/cases/11239 11232 Fuel out stack menu entry is missing https://pharo.fogbugz.com/f/cases/11232 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.10… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Kernel-MarcusDenker.1534.diff http://smalltalkhub.com/mc/Pharo/Pharo30/main/FuelTools-Debugger-MarcusDenk…

1 0

[pharo-project/pharo-core]
by GitHub July 25, 2013

July 25, 2013

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

1 0

[pharo-project/pharo-core] 332e8c: 30298
by GitHub July 25, 2013

July 25, 2013

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: 332e8c4ead04b4a592097e915c355841cc6a9023 https://github.com/pharo-project/pharo-core/commit/332e8c4ead04b4a592097e91… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2013-07-25 (Thu, 25 Jul 2013) Changed paths: A ScriptLoader30/ScriptLoader.cls/instance/pharo - scripts/script133.st A ScriptLoader30/ScriptLoader.cls/instance/pharo - updates/update30298.st M ScriptLoader30/ScriptLoader.cls/instance/public/commentForCurrentUpdate.st M Settings-Tools/DebugSystemSettings.cls/class/settings/debugSettingsOn_.st A Spec-Debugger/SpecDebugger.cls/class/utilities/closeAllDebuggers.st A Spec-Debugger/SpecDebugger.cls/class/window color/patchworkUIThemeColor.st M Spec-Debugger/SpecDebugger.cls/instance/actions/close.st M Spec-Debugger/SpecPreDebugWindow.cls/instance/protocol/initialExtent.st Log Message: ----------- 30298 11236 Proceed action does not close the refresh processes https://pharo.fogbugz.com/f/cases/11236 11235 The new debugger is missing some utilities methods https://pharo.fogbugz.com/f/cases/11235 11231 Predebugger window too small & not skipped to full debugger https://pharo.fogbugz.com/f/cases/11231

1 0

[update 3.0] #30298
by Marcus Denker July 25, 2013

July 25, 2013

30298 ----- 11236 Proceed action does not close the refresh processes https://pharo.fogbugz.com/f/cases/11236 11235 The new debugger is missing some utilities methods https://pharo.fogbugz.com/f/cases/11235 11231 Predebugger window too small & not skipped to full debugger https://pharo.fogbugz.com/f/cases/11231 Diff information: http://smalltalkhub.com/mc/Pharo/Pharo30/main/Spec-Debugger-MarcusDenker.10… http://smalltalkhub.com/mc/Pharo/Pharo30/main/Settings-Tools-MarcusDenker.4…

1 0

Fwd: [Pharo-bugtracker] FogBugz (Case [Issue]11237) Collection - #sorted no longer copies Arrays
by StÃ©phane Ducasse July 25, 2013

July 25, 2013

We should add a test and fix that issue. > From: "Pharo Issue Tracker" <do-not-reply(a)pharo.fogbugz.com> > Subject: [Pharo-bugtracker] FogBugz (Case [Issue]11237) Collection - #sorted no longer copies Arrays > Date: July 25, 2013 12:14:23 AM GMT+02:00 > To: "pharo-bugtracker(a)lists.gforge.inria.fr" <pharo-bugtracker(a)lists.gforge.inria.fr> > > A FogBugz case was opened by Sven Van Caekenberghe. > > Case ID: 11237 > Title: #sorted no longer copies Arrays > Status: Work Needed > Category: Bug > Project: Collection > Area: Misc > Priority: 5 - Fix If Time > Milestone: Later > Assigned To: Everyone > > URL: https://pharo.fogbugz.com/default.asp?11237 > > It seems that the introduction of TSortable removed Array>>#sorted: which made a aopy in order to honour the #sorted[:] contract of returning a new collection. This is now broken for Arrays. > > For example: > > #(4 3 2 1) inspect; sorted > > shows that the original changes, which is wrong. > > I guess the fix is to reinstate this missing method. > > > You are subscribed to this case. If you do not want to receive automatic notifications in the future, unsubscribe (https://pharo.fogbugz.com/default.asp?pre=preUnsubscribe&pg=pgEditBug&comma…) from this case. > > _______________________________________________ > Pharo-bugtracker mailing list > Pharo-bugtracker(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-bugtracker

1 0

smalltalkHub and Watch Project - espeically 'recently watched events'
by Chris Cunningham July 25, 2013

July 25, 2013

Hi. so, I have about 5 projects that I'm 'watching' in SmalltalkHub. On the home page (after I'm logged in), 1/2 of that page is taken up with the 'Recent watched events' list, which are a series of commit messages from one of my watched projects that were generated back in February of this year. More importantly, none of the recent activities for the projects show up at all in that list. Is this functionality turned on, or is it in a beta (mostly not working) state? I think I'd like it if it did show the most recent commits to the watched projects - that would be neat. So, then I logged out (thinking maybe it would refresh when I logged back in), but now I seem to be unable to log in via the web browser. I'm using Chrome - if I log in with correct user/password, it goes back to the 'not logged in' page. If I use the wrong password, I get told the user/password is wrong. Very odd. -Chris

3 2

Fwd: [vwnc] Doodling with Cairo...
by stephane ducasse July 24, 2013

July 24, 2013

Begin forwarded message: > From: Michael Lucas-Smith <michael.lucassmith(a)gmail.com> > Subject: Re: [vwnc] Doodling with Cairo... > Date: July 24, 2013 12:31:24 PM GMT+02:00 > To: stewart(a)xtra.co.nz > Cc: vwnc(a)cs.uiuc.edu > > Hi Stewart, > > Gizmo was just something Travis Griggs and I made to experiment with CairoGraphics. We wanted to see how it would perform, what kinds of issues we might run in to using Cairo resources in widgets, that sort of thing. > > The doodle layout algorithm is a variant of the CSS layout algorithm, significantly simplified, by me as a way to avoid having to do a full on layout algorithm but still get the majority of what we needed to experimenting. This approach to layout is not the future for the UI, we have other plans there using a constraint based solver that has been proven in production code both in Smalltalk and in other languages. > > As an experiment, it was a complete success - we sold ourselves on the idea that Cairo was completely viable for our customers to use for this kind of work (ie: custom widgets) and potentially for doing the core widgets too. Some of the people in the community have gone even further, making graphics contexts that use CairoGraphics and whole suits of widgets. It's inspiring and very cool. > > So, you've stumbled upon some of the humble beginnings - I frankly didn't realise we'd put that stuff in the open repository, I thought we'd left it in our private repository. Have fun with it if you want.. somewhere in there is my fancy clock that moves the numbers instead of the clock hands and also a Dr. Who animation. > > Cheers, > Michael > > On 10/01/2008, at 2:34 AM, Stewart MacLean <stewart(a)xtra.co.nz> wrote: > >> Hi, >> >> Iâve been experimenting with the various Cairo bits and pieces trying to figure out how to get a nice looking tree/UI â some interesting stuff! (thanks for the previous pointers, everyone). >> >> One of which is the Gizmo â which on first impression I wondered whatâs with all these pink rectangles? >> >> But delving deeper it looks like a pretty cool open ended framework â Iâve been experimenting with nesting and it sort of works, but not sure if Iâm configuring it correctly. >> >> The Cairo Wrapper Kit is a piece of art, but Iâm struggling to get my head around it â wrapper hell? >> >> Anyway, I was wondering where the âDoodle Layout Algorithmâ came from? â all I can find are references to a constraint based object visualization system from the mid 90âs. >> >> BTW, I know Smalltalk is generally self documenting code, but some âbig pictureâ class/package documentation with these lovely experiments would make them a lot more accessible! >> >> Cheers, >> >> Stewart >> >> >> Gizmo>>layoutFromIndex: index >> "** The Doodle Layout Algorithm ** >> 1) Use desiredLayoutBlock to find out what we want as our bounds inside the availableExtent given to us. Store this in @desired. >> 2) Figure out what extent we want to offer our children based on our @desired bounds. Store this in @offered. >> @desired may contain a width/height of BlockClosure. In this case, we offer the >> available space for that dimension to our children >> 3) Offer the @offered space to each child, storing their @requested space >> 4) Keep a record of the @maximum extent that our children reach inside us so that we can decide how to clip correctly. >> 5) <pluggable> Use our child layout algorithm to position and size the @requested space as the @bounds of the child >> 6) Return our @desired bounds to our parent as a requested space replacing any BlockClosure with details from our children's @maximum extent. >> ." >> >> >> _______________________________________________ >> vwnc mailing list >> vwnc(a)cs.uiuc.edu >> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc > > _______________________________________________ > vwnc mailing list > vwnc(a)cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

1 0