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

[Pharo-project] [update 2.0] #20432
by stephane ducasse Dec. 7, 2012

Dec. 7, 2012

20432 ----- Issue 7103: Job should use normalize progress [0.0 - 1.0] PART 1 http://code.google.com/p/pharo/issues/detail?id=7103 Diff information: http://ss3.gemstone.com/ss/Pharo20/Polymorph-Widgets-StephaneDucasse.742.di… http://ss3.gemstone.com/ss/Pharo20/Morphic-StephaneDucasse.1300.diff http://ss3.gemstone.com/ss/Pharo20/KernelTests-StephaneDucasse.458.diff http://ss3.gemstone.com/ss/Pharo20/Kernel-StephaneDucasse.1265.diff http://ss3.gemstone.com/ss/Pharo20/Deprecated20-StephaneDucasse.27.diff I will raise a debugger at the end. Just close it :). Stef

4 3

[Pharo-project] [update 2.0] #20433
by StÃ©phane Ducasse Dec. 7, 2012

Dec. 7, 2012

20433 ----- Issue 7110: FIx Refresh of ProgressBar http://code.google.com/p/pharo/issues/detail?id=7110 Diff information: http://ss3.gemstone.com/ss/Pharo20/Morphic-StephaneDucasse.1301.diff Stef

1 0

[Pharo-project] Delay bug
by Guillermo Polito Dec. 7, 2012

Dec. 7, 2012

Hi, When using a Delay and saving the image, the delay becomes stupidly broken. Look at this: With the following code Object subclass: #DelayBug instanceVariableNames: 'delay process' classVariableNames: '' poolDictionaries: 'private' category: 'DelayBug' start delay := Delay forMilliseconds: 300. process := [ [ Transcript logCr: 'test'. delay wait . false ] whileFalse: [ ] ] fork. - Then evaluate. *db := DelayBug new.* *db start.* - inspect *db instVarAt: 'delay'.* * * The delay seems ok. - save the image The delay has a stupid time to be finished :/ Guille

4 15

[Pharo-project] [update 2.0] #20432
by Marcus Denker Dec. 7, 2012

Dec. 7, 2012

20432 ----- Issue 6923: Missing Method in SocketStream http://code.google.com/p/pharo/issues/detail?id=6923 Diff information: http://ss3.gemstone.com/ss/Pharo20/Network-Kernel-MarcusDenker.76.diff

1 0

[Pharo-project] Pharo 2.0 BETA, Configs and Seaside
by Torsten Bergmann Dec. 7, 2012

Dec. 7, 2012

1. Since NativeBoost is now integrated I removed the config from the ConfigurationBrowser - because it makes no sense to install when it is already in the image :) 2. Please help to test external packages and if they are known to work on Pharo 2.0 please put a copy of ConfigurationOf... also into https://ss3.gemstone.com/ss/MetaRepoForPharo20.html Do not forget to put a symbolic version for #stable into the metacello config. This way they will show up in and will be loadable from the ConfigurationBrowser. 3. I would like to see a config with a recent Seaside for Pharo 2.0 showing up and putting it into ConfigurationBrowser too so Seaside is easily loadable right from Pharo 2.0. It loads well on the BETA when one uses: https://github.com/renggli/builder/blob/master/scripts/seaside31-pharo2.st and Gofer new squeaksource: 'ZincHTTPComponents'; "package: 'Zinc-HTTP';" package: 'Zinc-Seaside'; load. The only thing I've hit was some deprecation stuff #includesSubString: vs. includesSubstring: but I did not check all seaside tests. @Dale: whats the state of a Seaside config for Pharo 2.0? Thanks T.

5 4

[Pharo-project] [Fuel] Materialization error, #DoIt Not found
by Vanessa PeÃ±a Araya Dec. 7, 2012

Dec. 7, 2012

Hi, I was working with Fuel to save and load a Roassal view (serialize and materialize), and everything works perfect (so far) except for one thing: if I have an Anouncer which its registry has an announcementSubscription with a nil subscriber, it does not work is gives me this error: Standard Roassal interactions are OK, but if I do: aRoElement on: ROMouseClick do: [something] in a Wokspace materialization does not work. If I execute the same code in a method send as message to an object I have not this error and materialization works perfectly. This means I can not save some visualizations created in the Workspace. Have anyone experience something like this? Thanks, Vanessa.

2 4

[Pharo-project] Pharo 2.0 BETA, Configs and Seaside
by Torsten Bergmann Dec. 6, 2012

Dec. 6, 2012

>> 1. Since NativeBoost is now integrated I removed the config >> from the ConfigurationBrowser - because it makes no >> sense to install when it is already in the image :) >> >... >Do people only use the ConfigurationBrowser for initial installing of the >packages, or does it get used for when the package is updated? If the >former, this makes a lot of sense; if the later, you might want to rethink >removing it. When there is a newer NB version we will either integrate it into the base image or put the config (with a higher version declared as stable) in again so this newer version can be loaded easily from the tool. Bye T.

2 1

[Pharo-project] [update 2.0] #20430
by Torsten Bergmann Dec. 6, 2012

Dec. 6, 2012

>I'm working now in produce branded Pharo VMs with NB support out of the box. Please - can we use the attached icon for the new "branded" windows VM. It is more Pharo like than the "Cog wheel" one and includes all sizes. Thanks T.

6 6

[Pharo-project] Spec bindings assignment
by Pavel Krivanek Dec. 6, 2012

Dec. 6, 2012

Hi Ben, what was changed in the Spec bindings assignment in the new Spec versions? Because Periscope uses own subclass of MorphicBindings to provide own widgets including window widget but now only standard widgets are used and the different binding is not taken into account. Cheers, -- Pavel

2 3

Dec. 6, 2012

Hi guys We mentioned it in the past but now this is really official. To support the consortium, Inria is paying one full year to Igor Stasenko. We want to thank Inria for its continuous support. Stef

8 7