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

[Pharo-project] Packages and Pharo and Portability : the 3 Ps !
by Torsten Bergmann Dec. 29, 2011

Dec. 29, 2011

Hi Stef, >I created MetaReportForPharo14 I already created "MetaRepoForPharo14" on squeaksource today with Markus and me as admins. I can add you as admin too but the repo is read/write already. You should delete your "MetaReportForPharo14" since this is the wrong name (Report instead of Repo)! >I would like to load your browser in 1.4. Does it make sense? The Config browser is already in 1.4, but empty since the http://www.squeaksource.com/MetaRepoForPharo14/ repo that I created today still has no configs. See world menu "Tools" -> "Configuration Browser" IMHO we should fill the repo once a Pharo version has a first release candidate or is released. So we should care for 1.3 and not yet for 1.4. since this is what people use. Bye T. -- Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de

2 2

Re: [Pharo-project] Pharo Launcher app
by Fernando Olivero Dec. 29, 2011

Dec. 29, 2011

Noury, i believe i could build the app targeted a snow leopard as well. Sean, how you would launch the pharo launcher written in pharo? Still need to point to a vm + image, so this was the problem i was solving with this app. I assume that writing such an app, for the remaining OS shouldn't pose a challenge. Fernando On Wed, Dec 28, 2011 at 6:28 PM, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > > Noury Bouraqadi-2 wrote >> >> Sounds Cool. It's a pity that it's for Lion only. >> > > Where could we find a platform to write it in that would work on any major > modern OS... Oh, yeah, someone could write it in Pharo ;-) > > -- > View this message in context: http://forum.world.st/Pharo-Launcher-app-tp4238576p4240646.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >

1 0

[Pharo-project] Packages and Pharo and Portability : the 3 Ps !
by Torsten Bergmann Dec. 29, 2011

Dec. 29, 2011

While I agree that we have to be radical with throwing out ugly code and the like if we want to reinvent the future ... but if we do not care about external packages than we just work towards a clean Pharo platform that is of no use for anyone. I dont want Pharo to be fully compatible to Squeak or older Pharo versions but we have to find a way for people to follow the Pharo train and move there code forward toward a cleaner and better state also. And to see which packages are working and which not. Otherwise anyone of us will try these packages on his own, see them crash or repair them on his own way. And yes - I liked the concept of Squeakmap - install the things that are know to work right from within your image. Thats why I implemented a Configuration Browser which is accessible from world menu "Tools" -> "ConfigurationBrowser". It is a simple tool that should easy loading without all these Gofer and install scripts. Its a simple tool - depending on Pharo version XX it points to http://www.squeaksource.com/MetaRepoForPharoXX and displays all ConfigurationOfXYZ within that repo. This worked in Pharo 1.2 and works in Pharo 1.3 also. By default in Pharo 1.3 it opens on http://www.squeaksource.com/MetaRepoForPharo13 - since this is empty and not filled by the community the browser is unfortunately empty too. In Pharo 1.2 it showed some contents since I filled http://www.squeaksource.com/MetaRepoForPharo12 with copies of configs that are know to work with Pharo 1.2. If you like you can (programmatically) open it on any repository with configs you like: (MetacelloConfigurationBrowser new) repository: 'http://www.squeaksource.com/MetacelloRepository'; open So the idea is simple: if you have a ConfigurationOfSOMEPACKAGE that is know to work in Pharo 1.3 then use the copy button of Monticello browser to copy it to http://www.squeaksource.com/MetaRepoForPharo13 So it is a simplified SqueakMap for Monticello configs. If you know Seaside is working than copy the mcz's of it's config to http://www.squeaksource.com/MetaRepoForPharo13 and others can easily load it without evaluating scripts in workspaces or search in repos. Unfortunately nobody cared to copy the configs. Anything that has to happen is that the community copies the config that are tested and that are known to work. My fault is that it looks like I missed to answer some questions on [1] and [2] or to make it more clear what the tool is all about. This simple tool will not solve the problem of porting packages but may raise the visibility of packages that are known to work in a Pharo version! Nothing more. Bye T. [1] http://forum.world.st/Configuration-Browser-is-a-mastery-td3706003.html [2] http://stackoverflow.com/questions/6880596/how-to-browse-metacello-reposito… -- NEU: FreePhone - 0ct/min Handyspartarif mit Geld-zurÃ¼ck-Garantie! Jetzt informieren: http://www.gmx.net/de/go/freephone

2 1

[Pharo-project] Loading projects into changing Pharo
by Sean P. DeNigris Dec. 29, 2011

Dec. 29, 2011

This is an important question that deserves its own thread... > I was wondering what is planned regarding packages available on > SqueakSource and Pharo. More and more packages can't load in Pharo and it > gets more and more frustrating not being able to load anything without > having to add/modify methods/classes all over the place so those packages > can load properly in Pharo. Are we looking at a Pharo-only kind of > SqueakSource in the future ? > > Besides, having to handle platform specific (i.e. Pharo vs Squeak) for > every package is adding more complexity than what is needed. I know > backward compatibility was thrown away from the start to avoid compromises > in Pharo but how do we take care of the fact that as each day passes, less > and less stuff from SqueakSource is usable in Pharo ? > > tia > > ----------------- > Benoit St-Jean > Yahoo! Messenger: bstjean > A standpoint is an intellectual horizon of radius zero. > (Albert Einstein) > -- View this message in context: http://forum.world.st/Loading-projects-into-changing-Pharo-tp4243184p424318… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

1 0

Re: [Pharo-project] [Pharo-users] [COTDC] 98 - ZipFileConstants
by StÃ©phane Ducasse Dec. 29, 2011

Dec. 29, 2011

I defined some constant for the file compression. On Dec 28, 2011, at 7:50 PM, sean(a)clipperadams.com wrote: > 97 classes done > 798 classes remaining > Continuing in Compression... > > Today: ZipFileConstants > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > p.s. this message was sent from a pharo image. Did you know you could easily do that?! >

2 1

Re: [Pharo-project] [COTDC] 98 - ZipFileConstants
by Ben Coman Dec. 29, 2011

Dec. 29, 2011

sean(a)clipperadams.com wrote: > 97 classes done > 798 classes remaining > Continuing in Compression... > > Today: ZipFileConstants > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > p.s. this message was sent from a pharo image. Did you know you could easily do that?! > This class defines magic numbers taken from the PKWARE ZIP Application Note [1] approved by ISO/IEC JTC 1/SC 34 N 1621 in July 2011 [2] to be the international normative reference for the zip file format. A class imports these bindings as 'class variables' by including the following in its class definition: poolDictionaries: 'ZipFileConstants' There is a single method on the class side to initialise the values. [1] http://www.pkware.com/documents/casestudies/APPNOTE.TXT [2] http://www.itscj.ipsj.or.jp/sc34/open/1621.pdf Following are pertinent extracts from the PKWARE ZIP Application Note.... All values are stored in little-endian byte order unless otherwise specified. A. local file header signature 4 bytes (0x04034b50) C. Data descriptor: crc-32 4 bytes compressed size 4 bytes uncompressed size 4 bytes F. central file header signature 4 bytes (0x02014b50) I. end of central dir signature 4 bytes (0x06054b50) J. Explanation of fields: * version made by (2 bytes) 0 - MS-DOS and OS/2 (FAT / VFAT / FAT32 file systems) 3 - UNIX 1,2,4-20 not implemented * compression method: (2 bytes) 0 - The file is stored (no compression) 6 - The file is Imploded 8 - The file is Deflated 1-7,9-19,97,98 not implemented * For Methods 8 and 9 - Deflating Bit 2 Bit 1 0 0 Normal (-en) compression option was used. 0 1 Maximum (-exx/-ex) compression option was used. 1 0 Fast (-ef) compression option was used. 1 1 Super Fast (-es) compression option was used. * internal file attributes: (2 bytes) Bits 1 and 2 are reserved for use by PKWARE. The lowest bit of this field indicates, if set, that the file is apparently an ASCII or text file. If not set, that the file apparently contains binary data. Note the following do not appear in the PKWARE ZIP Application Note. Should they be defined elsewhere? "Unix permission bits" DefaultDirectoryPermissions := 8r040755. DefaultFilePermissions := 8r0100666. DirectoryAttrib := 8r040000. FileAttrib := 8r0100000.

2 1

[Pharo-project] [update 1.4] #14276
by StÃ©phane Ducasse Dec. 29, 2011

Dec. 29, 2011

14276 ----- - Issue 5135: Set>>grow buggy for sets with nil. Thanks Igor Stasenko. http://code.google.com/p/pharo/issues/detail?id=5135 - Issue 5130: Remove magicHalo behavior. http://code.google.com/p/pharo/issues/detail?id=5130 Stef and Igor Hacking HazelTracer

2 1

[Pharo-project] Roeltyper
by Sean P. DeNigris Dec. 29, 2011

Dec. 29, 2011

I added a little blurb w. link to the collaborative book - http://book.pharo-project.org/book/PharoTools/roeltyper/ -- View this message in context: http://forum.world.st/Roeltyper-tp4233847p4233847.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 10

[Pharo-project] changing the class of an existing object to a subclass
by Ben Coman Dec. 29, 2011

Dec. 29, 2011

greetings all, I am using ConfigurationOfODBC in Pharo 1.3. I have had success with getting an ODBCResultTable(OrderedCollection) containing ODBCRow containing about 30 fields. By default the fields are accessed by "row at: #fieldName" but I wanted to add some convenience methods to instead go "row fieldName." My searching and experimentation led me to subclassing ODBCRow as EAPPackage and then using "adoptInstance:" on each ODBCRow to convert it to the subclass. This was to avoid having to having to understand and change any of the ConfigurationOfODBC code. I had tried copyFrom: but some of the instance variables inherited from ODBCRow were not filled in, generating exceptions in some of the inherited methods. I had also considered "become:" but that didn't seem appropriate. Using "adoptInstance:" worked fine until I added a new instance variable to EAPPackage. Subsequently for "<primitive: 160 error: ec>", ec = #'bad receiver'. The "adoptInstance:" method comment says it follows the same rules as "primitiveChangeClassTo:" (yet note that "primitiveChangeClassTo:" never worked) The "primitiveChangeClassTo:" method comment says "The primitive will fail in most cases that you think might work [...] The facility is really provided for certain, very specific applications (mostly related to classes changing shape) and not for casual use" so I wondered if there was another way to achieve this. The full code is hopefully not too long to include for reference below. The use of "adoptInstance:" in the last section listed. ------ ODBCRow subclass: #EAPPackage instanceVariableNames: 'parent' "note adoptInstance works without this instance variable, and not with" classVariableNames: '' poolDictionaries: '' category: 'BTC-EA-Explore' ------ EAPPackage >> name ^ self at: #Name ------ ODBCResultTable subclass: #EAPPackages instanceVariableNames: '' classVariableNames: '' poolDictionaries: '' category: 'BTC-EA-Explore' ------ EAPPackages class >> newFromConnection: connection | packages parent | packages := (connection query: 'select * from t_package;') execute asTable. self adoptInstance: packages. packages do: [ :row | EAPPackage adoptInstance: row. ]. ^packages. ------ In a Workspace I successfully evaluate the following three lines without : connection := ODBCConnection dsn: 'CIM' user: '' password: ''. packages := EAPPackages newFromConnection: connection. connection close. ------ I found the ODBCRow instance creation to ODBCResultSet>>fetchRow. One alternative I've considered is to somehow pass through a custom SomeClass in a variable to replace the hard reference to ODBCRow - but I don't want to chase back all the cascading call references. Is there another way to change an existing object to another class, such that it can be specialised with both additional methods and instance variables? I would appreciate any pointers. regards, Ben

4 6

[Pharo-project] [COTDC] 98 - ZipFileConstants
by sean＠clipperadams.com Dec. 28, 2011

Dec. 28, 2011

97 classes done 798 classes remaining Continuing in Compression... Today: ZipFileConstants Comment Of The Day Contest - One Day One Comment Rules: #1: Each day a not commented class is elected. Each day the best comment will be integrated with name of the author(s). #2: If you cannot comment it, deprecate it. Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest p.s. this message was sent from a pharo image. Did you know you could easily do that?!

1 0