August 2012 - Pharo-dev - lists.pharo.org

[Pharo-project] Spec (1.0): A few Things
by Sean P. DeNigris Aug. 9, 2012

Aug. 9, 2012

All in all, Spec is *much* easier to work with than PolyMorph directly. The builder alone makes for much less code, as we only have to specify the attributes we care about. Ben, thanks for all the great work so far! While pushing on it, I ran into a few problems... 1. Issue 6547: [BUG Spec]: Populating a MultiColumnListModel http://code.google.com/p/pharo/issues/detail?id=6547 The following only populates runListModel if the final line is uncommented. It took quite a long time to figure out why nothing was appearing in the list! Apparently, this is an issue with MultiColumnListModel because ListComposableModels get populated w/o the update: initializeWidgets self instantiateModels: #( runListModel MultiColumnListModel). runListModel items: self model runs; menu: [ :aMenu | self runMenu: aMenu ]; displayBlock: [ :e | self wrapItem: e ]. " WorldState addDeferredUIMessage: [ runListModel updateList ]." 2. Issue 6546: [BUG Spec 1.4]: Menus don't forward action to model http://code.google.com/p/pharo/issues/detail?id=6546 Model>>perform: selector orSendTo: otherTarget ^ otherTarget perform: selector. In Pharo 2.0, #perform:orSendTo: has been moved to Object and does what it says it will. I copied that implementation to ComposableModel. It should probably be in a 1.4 platform package (although I guess there'd be little harm in adding across the board, save the duplication). 3. MultiColumnListModel sounds really cool, but seems to be in alpha. To be generally useful, it would have to have a feature set similar to Mac Finder. That is, for example: * a header row * resizable columns * editable cells (but only the ones you want to be editable) Cheers, Sean p.s. I still can't get Spec 1.1 to load in Pharo 1.4 -- View this message in context: http://forum.world.st/Spec-1-0-A-few-Things-tp4643653.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

[Pharo-project] Pharo 2.0-20245 | Group creation
by Noury Bouraqadi Aug. 9, 2012

Aug. 9, 2012

Hi, Group creation raises a DNU. Replacing messages -GroupAnnouncer announcer by -GroupAnnouncer uniqueInstance seems to solve the problem, though I'm not sure if this is correct. Noury -- http://twitter.com/#!/NouryBouraqadi http://www.kroobe.com/profile/noury

2 3

[Pharo-project] FileSystem differences between Pharo-2.0 and Pharo-1.4
by Dale Henrichs Aug. 9, 2012

Aug. 9, 2012

I'm starting a port of FileTree to Pharo-2.0 and I'm planning on using Pharo-1.4 (summer) to do the actual port, since I can't run my development environment in Pharo-2.0 (chicken and egg problem). I'm wondering if there are any significant differences between the FileSystem implementations on the two platforms that I should be aware of... Dale

4 9

[Pharo-project] Versionner: Committing a config commits twice
by Sean P. DeNigris Aug. 8, 2012

Aug. 8, 2012

Versionner is getting *really* cool!! I found a bug: http://ss3.gemstone.com/ss/Versionner.html/Issues Issue 1: Committing a config commits twice 1. In Pharo 2.0, "ConfigurationOfVersionner project development load:#('Core' 'Spec')." 2. Create new config for a package 3. Click commit It saves it, but then is shows it dirty again and asks about a new version number. Even though I cancelled, it saved the config to the repo (in this case http://ss3.gemstone.com/ss/VimPharo) again: ConfigurationOfVimPharo-SeanDeNigris.1.mcz ConfigurationOfVimPharo-SeanDeNigris.2.mcz -- View this message in context: http://forum.world.st/Versionner-Committing-a-config-commits-twice-tp463898… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 5

[Pharo-project] I'm going to integrate Metacello into Pharo 2.0
by Esteban Lorenzano Aug. 8, 2012

Aug. 8, 2012

Hi, Just as Gofer, it is just too important to keep it outside. Also, most of our packages now are loaded through a configuration (if there is one god, thanks him for that :), so it will be in most installations anyway. Of course, I will make sure that it is unloaded in a #cleanUpForProduction. Cheers, Esteban

5 6

[Pharo-project] StartupPreferences gone wild in 1.4
by Sean P. DeNigris Aug. 8, 2012

Aug. 8, 2012

StartupPreferences calls #loadStartupScript (loading all the StartupPreferences) ~10 times!! Also, will there be another 1.4 bug fix release? Thanks, Sean -- View this message in context: http://forum.world.st/StartupPreferences-gone-wild-in-1-4-tp4643586.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

2 1

[Pharo-project] Can you say "fuel" when one of its packages is changed?
by Mariano Martinez Peck Aug. 8, 2012

Aug. 8, 2012

Hi guys. As you can imagine, even if Fuel was integrated in 2.0, we continue developing it in our repo. This means that we have to merge with the changes "we/you" do in the Fuel version integrated in Pharo 2.0. To reduce the amount of work and to simplify the process, can I ask that in each issue that you provide a fix touches any of the Fuel packages, just say "Fuel" somewhere in the issue? I have a filter that detects if "Fuel" is part of an email so I will see it quickly and I will be able to merge it with our code base in ss3. Thanks in advance, -- Mariano http://marianopeck.wordpress.com

2 1

[Pharo-project] [update 2.0] #20248
by Esteban Lorenzano Aug. 8, 2012

Aug. 8, 2012

20248 ----- Issue 6441: Several CompiledMethod fixes from Squeak http://code.google.com/p/pharo/issues/detail?id=6441 Issue 6444: Improve NonInteractiveUIManager>>nonInteractive: http://code.google.com/p/pharo/issues/detail?id=6444 Issue 6486: Fix Slider missing method http://code.google.com/p/pharo/issues/detail?id=6486 Issue 6488: Fix SplitterMorph http://code.google.com/p/pharo/issues/detail?id=6488 Issue 6543: GeneralScrollPane>>#newScroller is wrongly assigning red color http://code.google.com/p/pharo/issues/detail?id=6543

1 0

[Pharo-project] [update 2.0] #20247
by Esteban Lorenzano Aug. 8, 2012

Aug. 8, 2012

20247 ----- Issue 6493: Integrate new version of Fuel and remove obsolete packages http://code.google.com/p/pharo/issues/detail?id=6493 Issue 6517: recategorizing some methods in PollyMoprh http://code.google.com/p/pharo/issues/detail?id=6517 Issue 6519: Merge NE and NO Completion http://code.google.com/p/pharo/issues/detail?id=6519 Issue 6534: Morphic+Polymorph changes http://code.google.com/p/pharo/issues/detail?id=6534 Issue 6536: add convenience BlockClosure>>#valueWithoutNotification http://code.google.com/p/pharo/issues/detail?id=6536 Issue 6537: gofer tests is using #doSilently: http://code.google.com/p/pharo/issues/detail?id=6537

1 0

[Pharo-project] RE : Re: [Vm-dev] Android Cog VM/Pharo Builds at INRIA Jenkins
by Philippe Back Aug. 8, 2012

Aug. 8, 2012

works on my samsung galaxy mini 1. will have to use a lighter image but works well and is responsive. ram footprint is 25 megs. Philippe Back StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> a Ã©crit : thanks Dmitry I'm sure that igor would love that you use the vm blog to collect vm information :). Stef On Aug 7, 2012, at 4:04 PM, Dmitry Golubovsky wrote: > > Hi, > > There are two CI (continuous integration) jobs running periodically at > the INRIA Jenkins server: CogDroid and PharoDroid. The former is an > unbundled NonJIT Cog VM for Android which can run any Smalltalk image > original Cog VM can run. The latter is the same Cog VM bundled with a > generic Pharo 1.4 Smalltalk image. These two builds complement each > other, and together they comprise an Android analog of the one-click > Pharo distribution: a practically usable piece of software ready for > development and exploration of possible uses of Smalltalk on mobile > devices. > > Whoever is interested to try Pharo and other compatible Smalltalk > implementations on Android devices are welcome to use these builds. A > brief overview with installation and usage recommendations can be > found here: > > http://code.google.com/p/squeakvm-tablet/wiki/JenkinsBuilds > > The developer of CogDroid and PharoDroid hopes that these new Android > applications will help the adoption of Smalltalk for writing > applications for mobile devices. > > Any thoughts, suggestions and critics are welcome. > > Thanks. > > -- > Dmitry Golubovsky > > Anywhere on the Web

1 0