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

Re: [Pharo-project] About the download page

by StÃ©phane Ducasse

Hi hernan I can give you access to edit the page because I do not have the time to fix it. stef On Feb 8, 2009, at 8:14 AM, HernÃ¡n Morales Durand wrote: > Let's suppose I'm a first visitor reading this page: > > http://code.google.com/p/pharo/wiki/Downloads?tm=2 > > " ... A link is given below to get the image ... " > There are various links below, specifically what is that link? > (Suggestion: anchor the link word) > > " ... You can either upgrade your image ... " > Any hint or link explaining how? > > " ... The virtual machine may be downloaded from ... " > Suggestion: > " ... The virtual machine [for the X Operating System] may be > downloaded from ... " and then > "The virtual machine [for the Y Operating System] may be downloaded > from ... " > > " ... The lastest VM available ... " > " ... The latest VM available ... " (typo) > > " Pharo files are still hosted at the Pharo INRIA project site. " > From an user point of view I don't know why that would be relevant. > > " Please head over to http://gforge.inria.fr/frs/?group_id=1299 " > To get the image ? the image and VM ? to choose downloading options ? > (what I mean is that isn't clear the "image" reference at the > beggining of page refers to this link or the "specific files" link > below). > > " Here are some links to specific files: > Pharo Core: Pharo0.1Core-10204.zip " > Suggestion: > " If you want to do/have/use X, you can download Pharo Core... " > " If you want to do/have/use Y, you can download Pharo Developer... " > etc. > > Final notes: > -There is no "Installation instructions" guidelines or link, this > commonly is: "When download is completed, uncompress.... get a > mysterious .sources file, and then copy the .exe there......" > -Still remain assumptions for a first visitor, like he already knows > what is an image, a virtual machine. Many first visitors are > outsiders and they download first, read later (show me don't tell > me). My suggestion is to provide a link/page in key words "image", > "virtual machine", I guess there are many sites where this is > explained easily; and a reference link, to the SqueakByExample book > for example, for people who wants to read more. > Just a couple of suggestions. > > Cheers > > HernÃ¡n > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 8, 2009

Re: [Pharo-project] looking for Unicode testers

by Hilaire Fernandes

Does not work here. My system is LANG=fr_FR.UTF-8 My keyboard keying is us_intl, (accented character are composed), this set up is used to work with standard pharo and ecoding to latin1 In the workspace when I type in 'e, I get e? When I open the FileBrowser on a folder 'ici et lÃ ' it is ok. Hoever there are some random error related to #pathParts message sent to an undefined object. Next, in pharo.sh, the encoding is set to latin1, why ? I removed it before the test. Hilaire 2009/2/6 Michael Rueger <m.rueger(a)acm.org>: > Hi all, > > finally I have something to look at :-) > http://impara.de/michael/unicode.zip > > It is the pharo one click with a modified (slightly outdated) image and > an updated Unix VM. > The image is not cleaned up at all, just so you are warned ;-) > > Please try out this version on different platforms and check if unicode > keyboard input, clipboard copy and paste as well as filenames are working. > > There are probably still plenty of bugs in there, that's why I need > extra testers :-) > Please also point out any existing patches I missed to include in this > image. > > Enjoy > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- http://blog.ofset.org/hilaire

Feb. 8, 2009

[Pharo-project] About the download page

by HernÃ¡n Morales Durand

Let's suppose I'm a first visitor reading this page: http://code.google.com/p/pharo/wiki/Downloads?tm=2 " ... A link is given below to get the image ... " There are various links below, specifically what is that link? (Suggestion: anchor the link word) " ... You can either upgrade your image ... " Any hint or link explaining how? " ... The virtual machine may be downloaded from ... " Suggestion: " ... The virtual machine [for the X Operating System] may be downloaded from ... " and then "The virtual machine [for the Y Operating System] may be downloaded from ... " " ... The lastest VM available ... " " ... The latest VM available ... " (typo) " Pharo files are still hosted at the Pharo INRIA project site. " >From an user point of view I don't know why that would be relevant. " Please head over to http://gforge.inria.fr/frs/?group_id=1299 " To get the image ? the image and VM ? to choose downloading options ? (what I mean is that isn't clear the "image" reference at the beggining of page refers to this link or the "specific files" link below). " Here are some links to specific files: Pharo Core: Pharo0.1Core-10204.zip " Suggestion: " If you want to do/have/use X, you can download Pharo Core... " " If you want to do/have/use Y, you can download Pharo Developer... " etc. Final notes: -There is no "Installation instructions" guidelines or link, this commonly is: "When download is completed, uncompress.... get a mysterious .sources file, and then copy the .exe there......" -Still remain assumptions for a first visitor, like he already knows what is an image, a virtual machine. Many first visitors are outsiders and they download first, read later (show me don't tell me). My suggestion is to provide a link/page in key words "image", "virtual machine", I guess there are many sites where this is explained easily; and a reference link, to the SqueakByExample book for example, for people who wants to read more. Just a couple of suggestions. Cheers HernÃ¡n

Feb. 8, 2009

[Pharo-project] [ANN] Monticello1.5/1.6 is now fully under MIT

by Keith Hodges

The audit involved scanning all of the following repositories: 1. Wiresong/mc (duplicated in squeaksource/Monticello) 2. impara/mc 3. squeaksource/mc 4. squeakfoundation.org/39a 5. squeakfoundation.org/310 Scanning every single version of the following packages 1. Monticello 2. TweakMC 3. MC1.5 4. MonticelloConfigurations 5. PackageInfo Collating every contributor, of any method, anywhere. Those initials that I am treated as approved are in the package MethodAuthorship, class side of class Authorship. It defines the following categories 1) contributor signed the viewpoints agreement, 2) mc1.5 contributors (the squeaksource repo was designated MIT licence) 3) pharo contributors (those who made their contribution to Pharo under MIT) 4) new squeak contributors (e.g. Ralph Johnson) Assuming that these lists are acceptable, we have now completed the audit of Monticello MC1.5, MC1.0 (in 3.10.2), MC1.0 (in 3.9), MC1.0 (impara's versions) MC1.5 has had a few minor changes applied in order to ensure that it does not use any contributions from any non-approved authors. Thus MC1.5/1.6 is now completely licenced under MIT. (Those who wish to audit other versions of MC, MC1.5 has the tools to help you do so). cheers Keith ===== AUDIT DETAILS ==== Code submitted by non-approved authors was reviewed as follows: > 'swr'->'?' > MCRepository class flushPasswords - swr's contribution is not in the history of current MC's - MC1.5 has this functionality reimplemented differently MCWorkingCopy-#nextVersionName - not in current MC1.5 - implementation is now completely different. Both of swr's package commits do not appear in the history of any currently used MC > 'kb'->'Ken Bryant'??? > MCChangeLogEntry-#repository: MCChangeLogEntry-#fileNameForVersionName: MCChangeLogEntry-#changesAccordingTo: MCChangeLogEntry-#ancestors - All contributions in the squeaksource.com/mc repository are MIT - Looking in detail at the check-in these methods first appeared Monticello-kph.354, this was a major refactoring carried out entirely by kph. Therefore it looks like 'kb' must be a typo, and should be kph. -- fixed in latest to avoid further confusion. > 'SR'->'?' > MCClassDefinition-#= -- rewritten by kph 10/25/2008 02:10 MCFileRepositoryInspector-#packageList MCFileRepositoryInspector-#packageSelection MCFileRepositoryInspector-#setRepository:workingCopy MCFileRepositoryInspector-verisionList MCFileRepositoryInspector-versionSelection -- This class was removed as a result of a refactoring in MC1.5, while other methods of the same name exist in the new implementation, the actual implementations of those methods are entirely new. MCHttpRepository-writeStreamForFileNamed:replace:do: - SR tweaked avi's code - cds tweaked avi's code again, removing most of SR's contribution - kph finally removed any trace of SR's contribution. (sorry SR whoever you are) MCMethodDefinition-#postload -- obsolete in MC1.5 MCRepository class-#settingsFileName -- obsolete MCWorkingCopyBrowser-defaultExtent - SR just changed some values as an arbitrary UI preference, the original code was avi's - kph has changed them again in MC1.5. MCWorkingCopyBrowser-widgetSpecs -- SR didnt change the code which was originally, avi's (see Monticello-avi.275.mcz) > 'pmm'->'Philippe Marschall?' > PackageInfo-#category:matches: -- obsolete method not included in MC1.5 > ''->'?' > MCMockClassA-#a #b #c #d #one #two #truth #moreTruth -- Traced methods back to avi, and cwp. Timestamps are now fixed and in Monticello.test an optional package. > 'ul'->'?' > - These minor contributions to the squeaksource,com/mc repository are under MIT > 'a'->'?' > Tracked down to TweakProjectBuilder-bf.40, this is not part of Monticello, and it should be 'ar' i.e Andreas. 'abc' -> '?' (not Colin Putney this time) see Monticello-abc.414 , Monticello-abc.414 - This contribution to the squeaksource,com/mc repository is under MIT - code is actually replacing some missing methods, so not originally authord by abc. - I believe abc is Gary Chambers in this case.

Feb. 8, 2009

Re: [Pharo-project] Small Monticello fix in PharoInbox

by StÃ©phane Ducasse

in 10225 :) On Feb 7, 2009, at 10:30 PM, Alain Plantec wrote: > Hi all, > <+Repository> button on Monticello browser do not work anymore > because of > a bug I've introduced by PopUpRemoval updates. > Monticello-alain_plantec.345 fixes the bug. > Cheers > Alain > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 7, 2009

[Pharo-project] Small Monticello fix in PharoInbox

by Alain Plantec

Hi all, <+Repository> button on Monticello browser do not work anymore because of a bug I've introduced by PopUpRemoval updates. Monticello-alain_plantec.345 fixes the bug. Cheers Alain

Feb. 7, 2009

Re: [Pharo-project] Call for UI gripes

by StÃ©phane Ducasse

When I here that I'm like puzzled. We never said that we will not integrate code that speed up pharo. We started with marcus to clean morphic and there are certainly a large place for possible improvement. Now if you wait that we do it. May be it will happen or may be not. Because we have also quite busy agenda. Stef On Feb 7, 2009, at 6:31 PM, Ramon Leon wrote: >> The biggest concern I have right now is speed. I'm not >> saying Pharo is too slow; I'm simply admitting that I do not >> know whether it is fast enough for some of the things I want to do. > > +10 to this. > > The UI is looking really great lately, but overall the experience is > it's > just too slow. Cracking open a raw squeak base image reminds me how > snappy > the UI used to be. Not really complaining, it's totally bearable, > but it'd > sure be nice if the pretty UI was quick and snappy, and you are > asking. > > Ramon Leon > http://onsmalltalk.com > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 7, 2009

Re: [Pharo-project] Call for UI gripes

by StÃ©phane Ducasse

Igor :) do you have some code so that we make progress on that side. On Feb 7, 2009, at 8:23 PM, Igor Stasenko wrote: > 2009/2/7 Ramon Leon <ramon.leon(a)allresnet.com>: >>> The biggest concern I have right now is speed. I'm not >>> saying Pharo is too slow; I'm simply admitting that I do not >>> know whether it is fast enough for some of the things I want to do. >> >> +10 to this. >> >> The UI is looking really great lately, but overall the experience >> is it's >> just too slow. Cracking open a raw squeak base image reminds me >> how snappy >> the UI used to be. Not really complaining, it's totally bearable, >> but it'd >> sure be nice if the pretty UI was quick and snappy, and you are >> asking. >> > Sure thing > MessageTally spyOn:[self fullDrawOn: World assuredCanvas] "where self > is an OB system window morph" > > 16.7% {10ms} BalloonEngine>>copyLoopFaster > 11.7% {7ms} SimpleBorder>>frameRectangle:on: > 6.7% {4ms} Array(SequenceableCollection)>>select: > 5.0% {3ms} ByteString(String)>>= > 5.0% {3ms} SmallInteger(Number)>>to:by:do: > 5.0% {3ms} > GrafPort(BitBlt)>>primDisplayString:from:to:map:xTable:kern: > 5.0% {3ms} BorderStyle>>frameRectangle:on: > 3.3% {2ms} ByteSymbol>>species > 3.3% {2ms} ByteString class(String class)>>new: > > total 61ms. > > some hot points crying to be optimized: > cache the OBMonticelloPackageNode>>classCategories , which get > rebuilt each time you draw the window. > this can make following numbers much smaller: > 5.0% {3ms} ByteString(String)>>= > 6.7% {4ms} Array(SequenceableCollection)>>select: > 3.3% {2ms} ByteString class(String class)>>new: > > Making SystemWindow>>drawDropShadowOn: to do nothing makes a > difference: > > [10 timesRepeat: [self fullDrawOn: World assuredCanvas ]] timeToRun > with shadows: 530 > without: 473 > ~ 10% speedup > > Changing the theme makes some difference (no shadows/with shadows): > - Watery 2: 50/60 ms > - Standard Squeak: 38/43 ms > - Soft Squeak: 46/55 ms > - Vistary: 56/62ms > (keep in mind these numbers are polluted with messageTally) > > As to me, the theme variancy is quite acceptable - a most complex > theme (with transulency) is drawn just 50% slower than most simple > one. > > As for, > 3.3% {2ms} ByteString class(String class)>>new: > > Total count of ByteString>>new: calls during > GlobalCounter reset. > self fullDrawOn: World assuredCanvas. > GlobalCounter counters copy inspect > > is 7146, > which again makes me look suspicious at OB here.. Hey! Are we drawing, > or processing a text?!?! > > >> Ramon Leon >> http://onsmalltalk.com >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 7, 2009

Re: [Pharo-project] Call for UI gripes

by Igor Stasenko

2009/2/7 Ramon Leon <ramon.leon(a)allresnet.com>: >> The biggest concern I have right now is speed. I'm not >> saying Pharo is too slow; I'm simply admitting that I do not >> know whether it is fast enough for some of the things I want to do. > > +10 to this. > > The UI is looking really great lately, but overall the experience is it's > just too slow. Cracking open a raw squeak base image reminds me how snappy > the UI used to be. Not really complaining, it's totally bearable, but it'd > sure be nice if the pretty UI was quick and snappy, and you are asking. > Sure thing MessageTally spyOn:[self fullDrawOn: World assuredCanvas] "where self is an OB system window morph" 16.7% {10ms} BalloonEngine>>copyLoopFaster 11.7% {7ms} SimpleBorder>>frameRectangle:on: 6.7% {4ms} Array(SequenceableCollection)>>select: 5.0% {3ms} ByteString(String)>>= 5.0% {3ms} SmallInteger(Number)>>to:by:do: 5.0% {3ms} GrafPort(BitBlt)>>primDisplayString:from:to:map:xTable:kern: 5.0% {3ms} BorderStyle>>frameRectangle:on: 3.3% {2ms} ByteSymbol>>species 3.3% {2ms} ByteString class(String class)>>new: total 61ms. some hot points crying to be optimized: cache the OBMonticelloPackageNode>>classCategories , which get rebuilt each time you draw the window. this can make following numbers much smaller: 5.0% {3ms} ByteString(String)>>= 6.7% {4ms} Array(SequenceableCollection)>>select: 3.3% {2ms} ByteString class(String class)>>new: Making SystemWindow>>drawDropShadowOn: to do nothing makes a difference: [10 timesRepeat: [self fullDrawOn: World assuredCanvas ]] timeToRun with shadows: 530 without: 473 ~ 10% speedup Changing the theme makes some difference (no shadows/with shadows): - Watery 2: 50/60 ms - Standard Squeak: 38/43 ms - Soft Squeak: 46/55 ms - Vistary: 56/62ms (keep in mind these numbers are polluted with messageTally) As to me, the theme variancy is quite acceptable - a most complex theme (with transulency) is drawn just 50% slower than most simple one. As for, 3.3% {2ms} ByteString class(String class)>>new: Total count of ByteString>>new: calls during GlobalCounter reset. self fullDrawOn: World assuredCanvas. GlobalCounter counters copy inspect is 7146, which again makes me look suspicious at OB here.. Hey! Are we drawing, or processing a text?!?! > Ramon Leon > http://onsmalltalk.com > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

Feb. 7, 2009

Re: [Pharo-project] It's time for Squeak 4.0!

by StÃ©phane Ducasse

thanks matthew!!! Stef On Feb 7, 2009, at 3:25 PM, Matthew Fulmer wrote: > On Sat, Feb 07, 2009 at 10:18:27AM +0100, St?phane Ducasse wrote: >> Matthew >> >> where did you get the list of people that signed the MIT agreement? I >> asked several times >> but never got any answer. > > The list of contributors is part of Yoshiki's > MethodAuthorship package: > > http://www.squeaksource.com/MethodAuthorship.html > > See the methods in the #data category of class Authorship > > I attached a log of an irc conversation with Yoshiki that may > clear a few things up. It is also included with > http://ftp.squeak.org/4.0alpha/squeak4.0-relicensingTools.zip > > -- > Matthew Fulmer -- http://mtfulmer.wordpress.com/ > <yoshi-irc.txt>_______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 7, 2009