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

[Pharo-project] [BUG] ColorForm fromUser
by StÃ©phane Ducasse Aug. 19, 2009

Aug. 19, 2009

while having fun rescuing, cleaning, commenting these nice morphic examples, I found that Form fromUser works but not its subclass ColorForm fromUser. Error when Display depth > 8 Inheritance at work :) http://code.google.com/p/pharo/issues/detail?id=1077 Stef

1 0

[Pharo-project] ST80 Pharo smalltalk based ebook for iphone goes to 1.1.0
by John M McIntosh Aug. 19, 2009

Aug. 19, 2009

After 10 days of waiting Apple has approved for sale my ST80Docs iPhone app, which is the Pharo based source code eBook. http://mobilewikiserver.com/ST80Docs.html Lurking under the covers is really a Pharo1.0beta-10401web09.07.5 image/changes/source which comes from Aug 8th 2009 which is wrapped with some UIKit UI code from WikiServer and some modifications to the Seaside code browser app to enable code browsing from a read only perspective and will actually work with Mobile Safari on the iPhone. This replaces alpha version of Pharo dated early April 09 which was in the 1.0.0 ST80Docs product. The html generator is now 30% faster so the application is more responsive. {Well actually the VM is 30% faster because I forgot a compiler setting when building the 1.0.0 product, and on a iPhone 3G most of the time is taken by javascript consuming the menu items that list the 100's of methods etc for a class} PS I did tap update to upgrade from 10401 but it hung at some point in loading the latest changes back on Aug 8th, so I abandon that idea and stuck with the *approved* 10401 version. Obviously when Pharo 1.0 production ships I will again update the application as soon as the Seaside/Pier folks build the official web version. If anyone wants some USA promo codes for a test run, you can email me not the list for them -- = = = ======================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com = = = ========================================================================

2 1

[Pharo-project] New Pharo based on core 10418
by Damien Cassou Aug. 19, 2009

Aug. 19, 2009

I've just uploaded new Pharo images: http://pharo-project.org/pharo-download In the zip files, you will find changelog.txt and packages.txt. The first file contains the list of packages that have changed between this version and the previous one while the second file contains the full list of non core packages. Here is the changelog.txt file from the new Pharo image: ImageForDevelopers-pharo-DamienCassou.186 => ImageForDevelopers-pharo-DamienCassou.189 NewInspector-PF.37 => NewInspector-PF.38 OB-Refactory-lr.158 => OB-Refactory-lr.159 OB-Standard-lr.425 => OB-Standard-DamienCassou.426 Refactoring-Core-lr.55 => Refactoring-Core-lr.56 -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

2 1

Re: [Pharo-project] Fwd: OverlyComplex
by Ken.Dickey Aug. 19, 2009

Aug. 19, 2009

Igor Stasenko <siguctua(a)gmail.com> > Stef, is this an invitation to continue discussion? >From ISSUE 1072: http://code.google.com/p/pharo/issues/detail?id=1072 ============================================== The intent is that this issue, 1072, introduces some problems which motivate SLICE-remove-Complex. I intend to open two new issues to be paired with (unreleased) SLICE-basic-Complex and SLICE-extended-Complex. So I would prefer people to hold back discussions of other issues than removal of Complex code until I open those issues. Baby steps. OK? ============================================== So, this is an invitation to the discussion "Should the Complex class and associated code be removed from Pharo-Core?". This is NOT an invitation to a discussion of what is reasonable in an optional Complex package. ... > I don't want to be peevish here, but things like: > >>Note that there is no attempt to change oddities of Smalltalk syntax. > >>E.g. > >> Â (3 + 1/2i) --> Â (0 - 2i) Â NOT Â (3 + (1/2)i) > > indicating that Ken don't realizing completely what is Smalltalk. I indicated that I know the Smalltalk syntax by knowing that (3 + 1/2i) --> (0 - 2i) and indicating I would _not_ change that. Smalltalk syntax is certainly confusing to people which come from other languages which parse 1/2i as a number, which is why I pointed it out -- for people who don't know the Smalltalk parse strategy. I presume that you _do_ want users to switch to Smalltalk from other languages! Yes? -KenD

5 8

[Pharo-project] Call for synchronization with OB tools
by StÃ©phane Ducasse Aug. 19, 2009

Aug. 19, 2009

Hi all I'm totally confused about the state of the OB tools and this is not a good point. So which version are loaded in pharo? What is the status of these versions? For the pharo book we are stuck because the chapters were using the package browser but now we cannot load it. Who controls what is loaded as OB tools? Stef (quite worried).

3 3

[Pharo-project] Class>>isSystemDefined ?
by Alexandre Bergel Aug. 19, 2009

Aug. 19, 2009

Dear List members, The following method is defined in Class: -=-=-=-=-=-=-=-=-= Class>>isSystemDefined "Answer true if the receiver is a system-defined class, and not a UniClass (an instance-specific lightweight class)" ^ self == self officialClass -=-=-=-=-=-=-=-=-= isSystemDefined is sent a number of times. Especially by streams. I guess that this determines what should be serialized what should not. However, #officialClass has only two implementers: -=-=-=-=-=-=-=-=-= Class>>officialClass "I am not a UniClass. (See Player officialClass). Return the class you use to make new subclasses." ^ self -=-=-=-=-=-=-=-=-= And slightly more surprising: -=-=-=-=-=-=-=-=-= MorphicModel>>officialClass "We want to make a new instance of the receiver, which is a subclass of MorphicModel. Answer who to make a new subclass of. Also used to tell if a given class is a UniClass, existing only for its single instance." ^ self name last isDigit ifTrue: [MorphicModel] ifFalse: [self] "MorphicModel7 can not have subclasses, but Slider and SystemWindow may" -=-=-=-=-=-=-=-=-= There is a very strong smell for cleaning here. Apparently, most of usage of #isSystemDefined could be replaced by #isBehavior Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

5 8

Re: [Pharo-project] WeakSet growth (issue 1047)
by Henrik Johansen Aug. 19, 2009

Aug. 19, 2009

Ah yes, I have a bad habit of just replying to an old post, and erasing the subject, I'll try and improve my behaviour from now on. I posted a short update to the issue, as I borked up the test results (as usual...) the my first one. : However, the main improvement I expected (constant instead of growing runtime per iteration) still occurs when I run the test properly. Cheers, Henry On Aug 19, 2009, at 4:46 50PM, StÃ©phane Ducasse wrote: > henrik > please create new threads else people may miss your posts > > On Aug 19, 2009, at 4:41 PM, Henrik Johansen wrote: > >> I updated this issue with a solution which is simpler and less >> intrusive than the one in Mantis, >> and don't suffer from any Concurrency-issues not present already. >> (You could argue they solve different problems, but the impact of not >> recycling nilSlots is much less important with this patch, since >> WeakSets won't tend to grow as large) >> >> I'd be grateful if someone would read my reasoning/test the patch, >> and >> give feedback whether there are scenarios where it's not a valid >> solution. >> >> Cheers,

1 0

Re: [Pharo-project] Fwd: OverlyComplex
by Ken.Dickey Aug. 19, 2009

Aug. 19, 2009

From: "Ellen.Dickey" <Ellen.Dickey(a)whidbey.com>Â Â (occasional) To: Pharo-project(a)lists.gforge.inria.fr Date: Yesterday 08:38:13 pm >>Note that there is no attempt to change oddities of Smalltalk syntax. I apologize to the list for calling Smalltalk syntax "odd". Coming from Scheme, I certainly know better. Â I am certainly for minimalist syntax. I prefer (< lowBound x highBound) to ((lowBound < x) && (x < highBound)) and (+ 1/2 1/3 1/6) to (1/2) + (1/3) + (1/6) What can I say, I am lazy and a bad typist. Note that Scheme has zero (count 'em 0) precedence rules and 3+1/2i parses as a single number, not three numbers, two math "operations" and a coercion. I did mention that I am only an occasional Smalltalk user and I have used a lot of programming languages. Also, I am used to posting to systems which let me preview and exit my postings. This was a draft. Again, I apologize. -KenD

1 0

[Pharo-project] assert:includes
by Daniel P Zepeda Aug. 19, 2009

Aug. 19, 2009

Greetings, I've run across this in my own tests that ran fine in Squeak, but failed in Pharo. I thought it was just me being a dummy, but when I imported SandstoneDb and ran the tests, the exact same thing happens. It is a simple fix, but being fairly new at this, I'd like to know why this is, and if I should have to do this or not. So, for easy reference, I loaded the latest SandstoneDb (rjl.117) into my image (pharo1.0beta-10401web09.07.5) and ran the tests, several of which failed with a doesNotUnderstand: #assert:includes: Here is the test: testCollectionSerialization kid save. mom children: (OrderedCollection with: kid). mom save. self flushAndReload . self assert: mom refreshed children includes: kid refreshed if I simply put parens around the argument to assert: like this: assert: (mom refreshed children includes: kid refreshed) it passes. In all cases of failing tests with SandstoneDb, that is the case. Any insight here? Thanks! DZ

6 10

Re: [Pharo-project] WeakSet growth
by Henrik Johansen Aug. 19, 2009

Aug. 19, 2009

> From: Henrik Johansen <henrik.s.johansen(a)veloxit.no> > > I'd be grateful if someone would read my reasoning, and give > feedback whether there are .... argh, this was meant to be ended with: "scenarios in which it does not lead to adequate performance". Cheers, Henry

1 0