- Pharo-dev - lists.pharo.org

[Pharo-project] Mars project on SqueakSource "reseted"
by Esteban Lorenzano Jan. 7, 2010

Jan. 7, 2010

Hi, I want to inform that all packages on Mars project on squeaksource were removed, because its unusability. Those packages were from the "first attempt" to build a native UI, and now I'm working with a new approach. I will start upload new versions of Mars and Deimos project right after send this email. Cheers, Esteban pd: if someone is interested on those old files, please email me and I will send a zip will latest versions.

1 0

[Pharo-project] getting crazy with ImageSegment code
by Mariano Martinez Peck Jan. 7, 2010

Jan. 7, 2010

Hi folks. I will pay a beer in next ESUG to the person that helps me to refactor this piece of code of ImageSegments: The idea is that I have a list of classes that were inactive and I want to group them by category (actually, seeing the code I think it is package) and to to create an ImageSegment per category (or package). This is the code (ONLYYYYY a piece...I cut all the rest) unused := self inactiveClassesDuringDiscovery. "These are the classes that were not used" groups := Dictionary new. SystemOrganization categories do: [:cat | i := (cat findLast: [:c | c = $-]) - 1. i <= 0 ifTrue: [i := cat size]. groups at: (cat copyFrom: 1 to: i) put: (groups at: (cat copyFrom: 1 to: i) ifAbsent: [Array new]) , ((SystemOrganization superclassOrder: cat) select: [:c | unused includes: c]) asArray]. groups keys do: [:cat | roots := groups at: cat. Transcript cr; cr; show: cat; cr; print: roots; endEntry. roots := roots , (roots collect: [:c | c class]). "There seems to be a problem with these packages, thus they are excluded." ((cat beginsWith: 'Sys') or: [cat beginsWith: 'Multilingual'] or: [cat beginsWith: 'Kerne'] ) ifFalse: [(ImageSegment new copyFromRoots: roots sizeHint: 0) extract; writeToFile: cat]. Transcript cr; print: Smalltalk garbageCollect; endEntry] Can someone help me tu rewrite this? I think I could use PackageOrganizer or PackageInfo but I have no idea. Thanks! Mariano

4 4

Re: [Pharo-project] [Metacello] Gofer and Metacello don't work again in 10505
by Dale Henrichs Jan. 7, 2010

Jan. 7, 2010

The packaging for Gofer has changed, so that breaks the ensureMetacello code that was trying to determine the version of Gofer that was loaded ... there is no package named Gofer anymore, so I'll have to figure something out ... Dale ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: | Gofer-Core-AdrianLienhard.114 from | http://www.squeaksource.com/Pharo | cheers | | mariano | | On Thu, Jan 7, 2010 at 12:09 AM, Dale Henrichs | <dale.henrichs(a)gemstone.com>wrote: | | > What version of Gofer is loaded into the Core? | > | > Dale | > ----- "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: | > | > | The error is Working copy for Gofer not found | > | | > | To reproduce it, update your Pharo 1.0 core image to 10505 and | > | evaluate any | > | load of any ConfigurationOf...for example | > | | > | (ConfigurationOfPharoMorphicExtras project version: '1.0') load | > | | > | The error is not even fixed evaluating: | > | | > | [ Gofer gofer load ] | > | on: Error | > | do: [ :err | err retry ]. | > | Gofer gofer recompile. | > | | > | I attach PharoDebug.log | > | | > | Any help? | > | | > | Thanks | > | | > | Mariano | >

3 3

[Pharo-project] Gofer and Metacello don't work again in 10505
by Mariano Martinez Peck Jan. 7, 2010

Jan. 7, 2010

The error is Working copy for Gofer not found To reproduce it, update your Pharo 1.0 core image to 10505 and evaluate any load of any ConfigurationOf...for example (ConfigurationOfPharoMorphicExtras project version: '1.0') load The error is not even fixed evaluating: [ Gofer gofer load ] on: Error do: [ :err | err retry ]. Gofer gofer recompile. I attach PharoDebug.log Any help? Thanks Mariano

2 4

[Pharo-project] EOCD zip errors
by Michael Roberts Jan. 6, 2010

Jan. 6, 2010

Hi, i an getting sporadic EOCD errors when applying updates in PharoCore 1.1. The workaround mentioned on the list is to remove the mcz file from the cache and try again. Does anyone know the exact nature of this error? e.g a corrupt zip? It does not appear deterministic... thanks, Mike

1 0

Re: [Pharo-project] Polymorph
by Gary Chambers Jan. 6, 2010

Jan. 6, 2010

Thank you Steph... it will be a challenge to produce a framework to support all our needs but I believe we have, between us all, the expertise and motivation to make it so! ----- Original message ----- Gary I feel honored by your trust (which is a ***really*** important value for me - mainly my own value). Now slices are only good when dealing with crosscutting changes. They help us finding the packages in the kind of random order of the inbox :) > Given the integration of Polymorph with Pharo and the distinct direction that Squeak is going I am going to have to mark an end to Polymorph as an ongoing project, as such. >Â > Further changes/additions/refactorings will now be limited to Pharo and must be therefore done using the Slice system (will take a while to get to grips with as time allows). What I would like is to have a deeper merge (not turning around morphic idiosyncrasies). For fun I wanted to check CUIS Morph since juan removed a lot of unnecessary code. >Â A final release of Polymorph will be made on SqueakSource, as time allows soon. This will be the last (allegedly compatible) version with Squeak, though I expect in its current state it is effectively not loadable into recent Squeak images. >Â > I'll try to get the time to make any changes via Pharo slices though I still like the modularity of packaging systems. Can't have both it seems. Polymorph is mature enough that, moving forward, most else can be done as additions rather that overrides. Cool. > Perhaps an "extras" package? > Thanks to all who have been involved with Pharo and helping us to move forward. Here's to the new baseline! >Â > Shame the StrikeFonts don't do all that they should... always a compromise of speed vs. functionality (c.f. translucent text). >Â > On a personal note, it would be nice to start to leverage the possiblility of an open approach to visuals, host windows etc. Valuable lessons have been learned and I think Pharo can provide a baseline for moving forward to a more flexible and performant ui substrate. Happy to work with you all to achieve that goal! Excellent! We really want to learn from your experience. I have rome also in my scanner. > Regards, Gary > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

[Pharo-project] Mac VM 5.2b3 & iPhone VM 2.1.0 ships
by John M McIntosh Jan. 6, 2010

Jan. 6, 2010

I've push the latest cocoa based 32/64bit macintel/powerpc VM Various users pointed out that option-arrow key did not work. Oddly I had marked moveWordForward/Back/etc as being required but couldn't figure out what the magic keystrokes were. 5.2b3 fixes the problem. Look for the folder experimental/64bits in the regular places found via http://smalltalkconsulting.com/squeak.html or ftp://ftp.smalltalkconsulting.com/experimental/64bit/32bitImage*64bitVM/ file name: Squeak 64-32 5.2b3.app.zip This *beta* VM runs in 32 or 64 bit mode on macIntel, and 32bit mode on powerpc to support Squeak 32bit images. Requires os-x 10.5 or higher. -------------------------------- iPhone VM 2.1.0 The iPhone VM now uses the pharo1.0-10502-rc1dev09.12.2.image The image feels faster, likely due to the ongoing Pharo optimization work. I note I can no longer build custom VM's for people's iPhones since I've exceeded the number of devices I can dedicate to iPhone development. People who have not use the iPhone VM in the past will need another developer to build a VM for them, or will need to purchase Apple's iPhone SDK. ----------------------------------- For the moment source for both VMs can be found at http://isqueak.org -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================

3 3

[Pharo-project] Dev images with or without tests?
by Mariano Martinez Peck Jan. 6, 2010

Jan. 6, 2010

Ok, that's the big questions. Until now, the Dev image only cointained the tests of the PharoCore image. Actually, it also included the tests fro those projects where the test were in the same package (for example, RoelTyer). Now, with the new Metacello infrastructure, you will be able to take a PharoCore and evaluate: (ConfigurationOfPharo project version: '10496') load (which it will load the defualt stuff, in this case, all the stuff for a dev image) or (ConfigurationOfPharo project version: '10496') load: 'StandardDevImageWithTests' which will loads not only all the packages, but also ALL the test of all packages (all packages that have tests). So, my question is, should the test be included in the default dev image? I think that yes, because of the following: 1) Tests are useful for documentation 2) It encourages people to run the tests before committing something (that may break something) 3) You can see the state of the image you are using. 4) Because they are not bad 5) Because if you don't want to load the test, just add a simple 'StandardDevImageWithoutTests' after the load. 6) I don't think they take a lot of size in an image. In addition, it is a DEV image, not production. In production is logic that you don't want the tests and that may be even done with something similar to ScriptLoader >> cleanUpForProduction So..what do you think ? Cheers Mariano

8 12

Re: [Pharo-project] Finalization quirk
by Gary Chambers Jan. 6, 2010

Jan. 6, 2010

Indeed, not all per pass... I find that, in Squeak, compared to VisualAge, for instance, that finalisation rarely happens regularly... This does tend to lead to quite prolonged processing when most critical... ----- Original message ----- Bill, I always tell people (a) finalization will occur later, not when you think it should (b) finalization will occur slower/faster than you think. (c) both (a) & (b) will vary You're violating (a) There is mention of doing a full GC will force the finalization, but I can't recall if that finalizes (all) objects in old oops space in one pass with squeak. Various Smalltalk flavours and versions do things differently, some at different times & versions perhaps would only finalize one oops per pass (visualage). On 2010-01-06, at 10:12 AM, Schwab,Wilhelm K wrote: > I am trying to add finalization to something and appear to be at a point that finalization does not happen until I open the process browser.Â Any ideas? > > Bill > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- =========================================================================== John M. McIntosh <johnmci(a)smalltalkconsulting.com>Â Twitter:Â squeaker68882 Corporate Smalltalk Consulting Ltd.Â http://www.smalltalkconsulting.com =========================================================================== _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Jan. 6, 2010

Some emails about traits from their father @ google :) > Hi Stef > > Sorry for the late reply. I'm just going through my email after the Christmas break... > > > Could someone please come up with ONE example where MI (traits in particular) solve an *actual* problem and not just some academic BS? > > I have encountered a bunch of cases in my every-day work at Google where single inheritance was not good enough to write the functionality that we needed without (a) code duplication and/or (b) boilerplate for object delegation (plus the associated complexity/slow-down/etc.). This was getting so annoying that I went through the hassle of implementing a template-based traits mechanism in C++ that we have been using quite regularly. > > For example, we have been designing and implementing a very complex framework for efficient handling of massive entity/relation graphs (billions of nodes). Since we needed this framework to be general across multiple aspects, we simply couldn't come up with a good way of doing this without some sort of MI, and traits proved to be extremely useful. So, based on my experience, I certainly have seen plenty of real-world applications where traits can make a tremendous difference!! > > That said, I can absolutely see that an overuse of traits can also add a lot of additional complexity. But in my opinion, this is not specific to traits and much more applies to almost any concept when it is overused. Consider for example single inheritance. If someone needs a class with 50 methods and decide to split this into a 10-level deep class hierarchy (just in case that somebody might want to reuse a part of it later), this will annoy a lot of other people and make things unnecessary complex. Similarly, if somebody splits a method with a 20 line algorithm into 10 helper methods with hard-to-understand names and consisting of only 2 lines each, this will probably make things much harder to understand (although having small methods is generally a good thing). > So, despite the fact that the concepts of single inheritance and (helper-)methods can be overused, I'm sure that neither of us would argue that they are bad/useless in the first place. And this is the same for any of the other nice programming concepts that come to mind, like meta-programming and closures (as much as I love closures for parametrization, overuse of functional elements can make code really hard to understand as well...) > > From my point of view, the same applies to traits: If traits are used in cases where they actually bring a benefit, i.e., they factor together a set of methods that conceptually and logically belong together and actually facilitate code reuse, they have been very useful to me. > > > Happy New Year and all the best, > Nathanael >

2 2