- Pharo-dev - lists.pharo.org

[Pharo-project] Google code / test running
by Torsten Bergmann Oct. 16, 2009

Oct. 16, 2009

The SqueakSVN pages moved to: http://www.hpi.uni-potsdam.de/hirschfeld/projects/ssvn/index.html Maybe it is of use to automate the SVN tasks ... Bye T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

2 1

[Pharo-project] Polymorph observations
by Schwab,Wilhelm K Oct. 15, 2009

Oct. 15, 2009

Gary, I have done a little with Polymorph and am quite impressed. A small usability suggestion for the examples is to include comments with the text on a line by itself. It is a lot easier to execute something formatted as " ThisOrThat example ThisOrThat someOtherExample " than it is the (very common in Squeak) "GoAhead iChallengeYouToSelectMe andMissTheQuotes". On to more substantive things. TEasilyThemed is a big help, but some model and/or presenter classes would help. Consider a list. One has to define an aspect for the selection index and initialize it to zero. Similar comments apply to trees, with the added wrinkle of wrapping the nodes with appropriate objects. Dolphin's MVP framework creates default models that can be replaced. One weakness of the defaults is that they can take significant time to create for substantial objects. I hacked around that, and we could easily design it out of anything that we build. Dolphin lists and trees treat their selection in terms of the object selected rather than the index. One can get and set the index if needed, but it is not generally as interesting as the object behind the selection. One good thing about specifying the aspect is that one can can connect a view to an aspect of any model. Dolphin allows for the same flexibility via value adapters and type converters. Does TEasilyThemed include helpers for creating splitters? Bill

2 2

[Pharo-project] Google code / test running
by Torsten Bergmann Oct. 15, 2009

Oct. 15, 2009

Havent tried it but there is a SqueakSVN project to get access to SVN: http://map.squeak.org/package/184ebabe-a32c-403f-8088-ff85233cabca/autovers… Read more here: http://news.squeak.org/2008/09/16/subversion-integration-for-squeak/ Bye Torsten -- Neu: GMX DSL bis 50.000 kBit/s und 200,- Euro Startguthaben! http://portal.gmx.net/de/go/dsl02

1 0

[Pharo-project] Google code / test running
by Michael Roberts Oct. 15, 2009

Oct. 15, 2009

I have uploaded a GoogleCode package to PharoTaskForces. It is an improvement on the baseline test scripts. To get going have a look at PharoTestScript and modify some of the constants. If you want to participate running tests you need to first checkout the wiki using svn. You can see how that is done in the code or just follow google's help page. You need your profile password to do commits. I have a minimal svn wrapper which is intended to be hooked up to e.g OSProcess but that is just scaffolding until i can test it. The operation is basically runs all the tests, write out a wiki page, and add & commit to the wiki. There is more to do, but it is better than the original changeset. cheers, Mike

1 0

[Pharo-project] [update] #10471
by StÃ©phane Ducasse Oct. 15, 2009

Oct. 15, 2009

10471 ----- - Issue 1309: Date and time speedup creation from squeaktrunk - Issue 1233: Needs changes after fix 1129 Stef

1 0

[Pharo-project] New items in Pharo Core merger
by Henrik Johansen Oct. 15, 2009

Oct. 15, 2009

Would it be possible to enable "Keep current version" (ie, don't install the version from the thing being merged) to the menu list for New items in the Monticello merger? It's kind of hard to f.ex. merge Squeak-trunk Collections, containing Base64MimeConverter, when in Pharo, that Class exists in a different package. At least as far as I can tell (haven't actually done it, as I don't feel like resolving the 260 other conflicts just to find out), applying the merge will result in move the class. Alternatively to check if the item already exists in the system, but in a different package, and mark that as a conflict. Cheers, Henry

3 2

[Pharo-project] Fwd: [squeak-dev] The Trunk: Kernel-ar.271.mcz
by CÃ©drick BÃ©ler Oct. 15, 2009

Oct. 15, 2009

---------- Forwarded message ---------- From: <commits(a)source.squeak.org> Date: 2009/10/15 Subject: [squeak-dev] The Trunk: Kernel-ar.271.mcz To: squeak-dev(a)lists.squeakfoundation.org Andreas Raab uploaded a new version of Kernel to project The Trunk: http://source.squeak.org/trunk/Kernel-ar.271.mcz ==================== Summary ==================== Name: Kernel-ar.271 Author: ar Time: 14 October 2009, 8:49:48 am UUID: a603d2fe-dccf-894f-95db-ef577480b03c Ancestors: Kernel-nice.270, Kernel-ul.270 Merging Kernel-ul.270: - faster DateAndTime and Date creation with #year:month:day: and friends - minor formatting fixes =============== Diff against Kernel-nice.270 =============== Item was changed: ----- Method: DateAndTime>>midnight (in category 'squeak protocol') ----- midnight "Answer a DateAndTime starting at midnight local time" + ^self class basicNew + setJdn: jdn + seconds: 0 + nano: 0 + offset: self class localOffset - ^ self - dayMonthYearDo: [ :d :m :y | self class year: y month: m day: d ] ! Item was changed: ----- Method: DateAndTime class>>year:month:day:hour:minute: (in category 'squeak protocol') ----- year: year month: month day: day hour: hour minute: minute + "Return a DateAndTime" + ^self - "Return a DateAndTime" ^ self year: year month: month day: day hour: hour minute: minute second: 0 ! Item was changed: ----- Method: DateAndTime class>>year:month:day:hour:minute:second:nanoSecond:offset: (in category 'squeak protocol') ----- year: year month: month day: day hour: hour minute: minute second: second nanoSecond: nanoCount offset: offset "Return a DateAndTime" + | monthIndex daysInMonth p q r s julianDayNumber | - | monthIndex daysInMonth p q r s julianDayNumber since | monthIndex := month isInteger ifTrue: [month] ifFalse: [Month indexOfMonth: month]. daysInMonth := Month daysInMonth: monthIndex forYear: year. day < 1 ifTrue: [self error: 'day may not be zero or negative']. day > daysInMonth ifTrue: [self error: 'day is after month ends']. p := (monthIndex - 14) quo: 12. q := year + 4800 + p. r := monthIndex - 2 - (12 * p). s := (year + 4900 + p) quo: 100. julianDayNumber := ( (1461 * q) quo: 4 ) + ( (367 * r) quo: 12 ) - ( (3 * s) quo: 4 ) + ( day - 32075 ). + ^self basicNew + setJdn: julianDayNumber + seconds: hour * 60 + minute * 60 + second + nano: nanoCount + offset: offset; - since := Duration days: julianDayNumber hours: hour - minutes: minute seconds: second nanoSeconds: nanoCount. - - ^ self basicNew - ticks: since ticks offset: offset; yourself! Item was changed: ----- Method: DateAndTime class>>year:month:day: (in category 'squeak protocol') ----- year: year month: month day: day + "Return a DateAndTime, midnight local time" + + ^self - "Return a DateAndTime, midnight local time" ^ self year: year month: month day: day hour: 0 minute: 0 ! -- CÃ©drick

3 2

[Pharo-project] Pharo by example
by Schwab,Wilhelm K Oct. 15, 2009

Oct. 15, 2009

Stef, My printed copy arrived today. It looks like a really good book. There are some headings that have missing letters, for example, see pg. 27 ("A rst application") pg. 215 (section 10.4, "Using streams for le access"); the 10-07 pdf looks ok, so this could be a Lulu mistake. I reserve the right to retract this as I continue reading, but the dropped letters all appear to be from (sub)section names, and so far, they do *not* look like areas that were "low on ink." The adjacent text looks crisp; it simply looks as though the letters were somehow dropped from the titles. One small suggestion/request for future prined copies would be to make the pages a little wider and move the text outward slightly. As it is, it sometimes gets a little tight into the spine. Nice job - thanks to all involve for writing it! Bill

1 0

Oct. 14, 2009

Hi, With the attached changed set, it's now possible to delete morph from the right click menu (see the pic). ps: I also renamed 'selection' to 'halo on' (and halo off). Not sure this is a good choice. hth, -- CÃ©drick

2 3

[Pharo-project] Default String encoding when storing to file?
by Henrik Johansen Oct. 14, 2009

Oct. 14, 2009

Hi, just did a small test of a faster storeOn: for ByteStrings (using next:putAll:startingAt: for sequences not containing quotes, instead of nextPut: for each character ), and ran into a weird quirk. When writing to disk (on Windows), the old storeOn: would result in storing the Ã¸'s in the string below as F8, while with storeOn2: they are stored as C3 B8. (Haven't looked at exactly why they're saved differently.) As far as I can tell from a google search, F8 is ascii encoding, and C3 B8 is UTF8 encoding. Could this be a cause for the "invalid UTF8 character"-errors we've been seeing sporadically? Attached a changeset with storeOn2: , below is the workspace I used. Cheers, Henry str := 'asdfasdfadfadfrgjn''fgoibocbxlgjsrgoihrgohgfn''cx,bmxnbÃ¸zghÃ¸fhzÃ¸dfhxcvnzdfljfoaurgaorhr8htg0ae8gofhef08hasovhdfhÃ¸xo''vh89ah4f9aw8hf'. str storeOn: (FileStream newFileNamed: 'test22.txt'). Time millisecondsToRun: [|fs| fs := FileStream oldFileNamed: 'test22.txt'. 50000 timesRepeat: [str storeOn: fs]. fs close]. 23494 22869 str storeOn2: (FileStream newFileNamed: 'test2.txt'). Time millisecondsToRun: [|fs| fs := FileStream oldFileNamed: 'test2.txt'. 50000 timesRepeat: [str storeOn2: fs]. fs close]. 1303 1383 'From Pharo1.0beta of 16 May 2008 [Latest update: #10470] on 12 October 2009 at 2:31:08 pm'! !ByteString methodsFor: 'printing' stamp: 'HenrikSperreJohansen 10/12/2009 14:30'! storeOn2: aStream "Print inside string quotes, doubling inbedded quotes." | ix startIx| aStream nextPut: $'. startIx := 1. [(ix := self indexOf: $' startingAt: startIx) > 0 ] whileTrue: [ aStream next: ix +1 - startIx putAll: self startingAt: startIx. aStream nextPut: $'. startIx := ix +1]. aStream next: self size +1 - startIx putAll: self startingAt: startIx. aStream nextPut: $'. ! ! !ByteString methodsFor: 'printing' stamp: 'HenrikSperreJohansen 10/12/2009 14:30'! storeString2 "Answer a String representation of the receiver from which the receiver can be reconstructed." |result ws | result := String new: self size +2. ws := result writeStream. self storeOn2: ws. ^ws position = result size ifTrue: [result] ifFalse: [ws contents] ! !

3 4