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

[Pharo-project] [ANN] Pharo 1.0 Beta - Win32 Installer

by Torsten Bergmann

see http://pharo-project.org/pharo-download -- Neu: GMX Doppel-FLAT mit Internet-Flatrate + Telefon-Flatrate fÃ¼r nur 19,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02

July 31, 2009

Re: [Pharo-project] Fix for issue 981 Author class in pharo

by Miguel CobÃ¡

I have tested the SLICE of issue 981 on a new Pharo 10401 beta image and an updated 10402 image and it loads without problems. Should I mark this as milestone 1.0 or isn't elegible for this first release? I know that my opinion is biased, but I think that the 1.0 version of pharo should have the initials problem solved in order to base all the subsecuent code not to depende on initials. Comments? Has anyone confirmed that the functionality is correct? What about the format of the name and the message prompt? Cheers, Miguel CobÃ¡ On Mon, Jul 27, 2009 at 11:40 AM, Miguel CobÃ¡<miguel.coba(a)gmail.com> wrote: > 2009/7/25 Miguel Enrique CobÃ¡ Martinez <miguel.coba(a)gmail.com>: >> http://code.google.com/p/pharo/issues/detail?id=981 >> >> Name: SLICE-ChangeAuthorInitialsAndNameToFullName-MiguelCoba.3 >> Author: MiguelCoba >> Time: 25 July 2009, 3:53:41 am >> UUID: 27a1accc-4f41-4d11-94f5-9bdbb4166bd7 >> Ancestors: SLICE-ChangeAuthorInitialsAndNameToFullName-MiguelCoba.2 >> Dependencies: Monticello-MiguelCoba.372, Morphic-MiguelCoba.347, >> ScriptLoader-MiguelCoba.972, System-Changes-MiguelCoba.11, >> System-Support-MiguelCoba.62, Tools-MiguelCoba.179 >> >> Removes all the code from initials and name on Author class. It is >> replaced by a new fullName inst var and corresponding methods. The old >> code it is deprecated and the image contains no more calls to the old >> code. All the new code should call only the fullName methods in Author >> >> >> This is my first intent to rewrite the Author class to unify the >> instance variables. >> Please, check it on a 10392 core image and post your comments/critics. >> >> Also, I didn't modify the following methods of Utilities. Tell me what >> would you like to do with them, please: >> >> Utilities fixStamp: >> Utilities methodsWithInitials: >> Utilities doesMethod:forClass:bearInitials >> > > Also, it should fix also > > http://code.google.com/p/pharo/issues/detail?id=142 > http://code.google.com/p/pharo/issues/detail?id=344 > > I changed the status of 981 to fixed as directed by the > HowToContribute wiki page. > > Miguel CobÃ¡ > >> Cheers, >> Miguel CobÃ¡ >> >> >

July 31, 2009

[Pharo-project] Pharo name format

by Miguel Enrique CobÃ¡ Martinez

Now that the release date for pharo is close, I propose to use the following sintax for the pharo core products PharoCore-x.y-#####-TagName.zip where x.y is the version of pharo (0.1, 1.0, 1.1, 2.0, 2.1, etc) ##### is the number of image release in that version (10449, 10450, 10451, etc) TagName is a tag for better explain some specific feature of the image (closure, RELEASE, STABLE, beta, etc) e.g. For a normal daily release, say 10450, in the 0.1 branch: PharoCore-0.1-10450.zip For the image that has all tests in green: PharoCore-0.1-10456-AllTestGreen.zip For the image that it is the first stable 1.0: PharoCore-1.0-10478-RELEASE_1_0.zip For the next image with the NewCompiler code integrated, after the 1.0 release: PharoCore-1.0-10490-NewCompiler.zip For a subsecuent 1.1 release, that includes NewCompiler: PharoCore-1.1-10511-RELEASE_1_1.zip When, for example, 1.1 is the current branch, and 1.0 has fixes support and a new emergency release for the old 1.0 branch: PharoCore-1.0-10512-UPDATE_1.zip Release for pharo 2.0: PharoCore-2.0-10890-RELEASE_2_0.zip Other fix in the 1.1 branch (brach 1.0 is out of support): PharoCore-1.1-10915-UPDATE_1.zip Notes: We can also reset the number in each mayor release (0.1, 1.0, 1.1, etc) so that the updates to the old supportes branches can be a continuous. For example, the previous names would be (in the same order of release as the examples above): PharoCore-0.1-10450.zip PharoCore-0.1-10456-AllTestGreen.zip PharoCore-1.0-10001-RELEASE_1_0.zip PharoCore-1.0-10002-NewCompiler.zip PharoCore-1.1-10001-RELEASE_1_1.zip PharoCore-1.0-10003-UPDATE_1.zip PharoCore-2.0-10001-RELEASE_2_0.zip PharoCore-1.1-10002-UPDATE_1.zip etc Also, the PharoCore-1.0-10001-RELEASE_1_0.zip would be a copy of the last image of 0.1 branch (in this example PharoCore-0.1-10456-AllTestGreen.zip) But this is mostly estetic and can potentially confuse new users. What do you think?

July 31, 2009

[Pharo-project] keyboard shortcut open a warning

by StÃ©phane Ducasse

may be we should simply remove that item. menu system keyboard shortcuts Stef

July 31, 2009

Re: [Pharo-project] [ANN] Pharo 1.0 Beta

by StÃ©phane Ducasse

So what is the process now? Do we focus on 1.0? Can we integrate other issues? Do we have a separate stream for 1.1 alpha? Stef > Hi all, > > We are excited to announce the first Pharo 1.0 beta release. > > A new Pharo image (and also Pharo-web image) can be downloaded from > the website: > > http://pharo.cmsbox.ch/pharo-download > > The corresponding version number of Pharo-core is #10401. > > I'd like to thank all the people that have contributed to Pharo so > far! > > Have fun, > Adrian > > BTW, I also wrote about Pharo and the beta release on http://www.adrian-lienhard.ch/blog > > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 31, 2009

Re: [Pharo-project] Why I use Pharo

by StÃ©phane Ducasse

> I'm super excited to hear about Pharo 1.0 beta. I thought I'd post > about why I'm using Pharo. Thanks for sharing that with us. > I started using Pharo about 2 weeks ago and have finally started > writing small programs in Smalltalk again. Excellent! Smalltalking is good for the mind :) > Just over 2 years ago, I was learning Squeak but got frustrated at > finding most links dead or things that didn't seem to be maintained. I > was very excited with the changes in 3.8 and 3.9 but was left > wondering what happened after that. Looking back, it looks like Pharo > happened. We got frustrated by the lack of general quality and sad to see excellent ideas unfinished or rotting. Now you can help making pharo better. Have fun. > Thanks so much to everyone. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 31, 2009

Re: [Pharo-project] Fwd: [Bug and Fix] actualclass in presence of classtrait

by StÃ©phane Ducasse

When you have a class extension you need to know if a method belong to a package or another one. Now when enumerating methods you can always ask all the package which one defines the methods or simply asks the methodreference (in my rewrite of package I extended methodReference to avoid asking all the packages all the times). Stef

July 31, 2009

[Pharo-project] Fwd: Fonts (was Re: [etoys-dev] Wording in Clouds)

by StÃ©phane Ducasse

Begin forwarded message: > From: Bert Freudenberg <bert(a)freudenbergs.de> > Date: July 31, 2009 6:30:19 PM CEDT > To: etoys dev <etoys-dev(a)squeakland.org> > Subject: Re: Fonts (was Re: [etoys-dev] Wording in Clouds) > > > On 31.07.2009, at 08:31, Andreas Raab wrote: > >> Hi - >> >> I've integrated Bert's fix as well as support for .ttc collections: >> >> http://tracker.squeakland.org/browse/SQ-283 >> >> While working on this I realized how outdated the etoys image is >> when it comes to TTF support. I was trying to bring in some other >> necessary fixes but that wouldn't work at all, so I've added a >> filed out version of TTCFont.st from 3.10.2-trunk which has all the >> necessary fixes but probably some other issues. With this version >> things *almost* work: >> >> * Install TTFileDescription.5.cs >> * Install TTCFont.st >> * Install WhiteSpaceFixes.2.cs > > > I tried on a Mac, first failure in #fontOffsetsInFile:. There are > fonts that are tagged 'true' instead of (0 1 0 0): > > http://developer.apple.com/textfonts/TTRefMan/RM06/Chap6.html > > "The values 'true' (0x74727565) and 0x00010000 are recognized by the > Mac OS as referring to TrueType fonts." > > That's easy to fix. > > Then there are bitmap fonts like "NISC18030.ttf" which cannot be > loaded, they fail when looking for the 'head' table. > > The list of *ttf on the Mac isn't really long, most fonts are not in > truetype format apparently: > > ('Al Bayan' 'Andale Mono' 'AppleMyungjo' 'Arial' 'Arial Black' > 'Arial Hebrew' 'Arial Narrow' 'Arial Rounded MT Bold' 'Arial Unicode > MS' 'Ayuthaya' 'Baghdad' 'Brush Script MT' 'Chalkboard' 'Comic Sans > MS' 'Corsiva Hebrew' 'Courier New' 'DecoType Naskh' 'Devanagari MT' > 'Euphemia UCAS' 'Georgia' 'Gujarati MT' 'Gurmukhi MT' 'Impact' > 'InaiMathi' 'Kailasa' 'Kokonor' 'Krungthep' 'KufiStandardGK' > 'Microsoft Sans Serif' 'Mshtakan' 'Nadeem' 'New Peninim MT' > 'Plantagenet Cherokee' 'Sathu' 'Silom' 'Tahoma' 'Times New Roman' > 'Trebuchet MS' 'Verdana' 'Webdings' 'Wingdings' 'Wingdings 2' > 'Wingdings 3') > > There were 5 more fonts but their names were mangled (IIRC fonts can > store their meta data in various languages and encodings). > > I tried to install "Tahoma" but got the message that the subfamily > "Negreta" (span. "black") is not recognized in > #indexOfSubfamilyName:. After fixing that it worked fine. > > Attaching a changeset with my fixes (though maybe the bitmap > detection should not just rely on errors). > > If anyone else is testing on a Mac you might find this helpful (and > if you do, review and push, thanks): > > http://tracker.squeakland.org/browse/SQ-243 > > - Bert - > _______________________________________________ > etoys-dev mailing list > etoys-dev(a)squeakland.org > http://lists.squeakland.org/mailman/listinfo/etoys-dev

July 31, 2009

[Pharo-project] Fwd: Fonts (was Re: [etoys-dev] Wording in Clouds)

by StÃ©phane Ducasse

Begin forwarded message: > From: Andreas Raab <andreas.raab(a)gmx.de> > Date: July 31, 2009 8:31:02 AM CEDT > To: etoys dev <etoys-dev(a)squeakland.org> > Subject: Re: Fonts (was Re: [etoys-dev] Wording in Clouds) > > Hi - > > I've integrated Bert's fix as well as support for .ttc collections: > > http://tracker.squeakland.org/browse/SQ-283 > > While working on this I realized how outdated the etoys image is > when it comes to TTF support. I was trying to bring in some other > necessary fixes but that wouldn't work at all, so I've added a filed > out version of TTCFont.st from 3.10.2-trunk which has all the > necessary fixes but probably some other issues. With this version > things *almost* work: > > * Install TTFileDescription.5.cs > * Install TTCFont.st > * Install WhiteSpaceFixes.2.cs > > (oh, stupid, stupid JIRA - it does not preserve the ordering in > which files were added and you cannot order by date even in "manage > attachments" mode; make sure you do *not* load TTFileDescription.st > since it's outdated) > > * If on Windows, execute: > > TTFileDescription installFamilyNamed: 'Batang'. > > (this is a standard font on Windows which has CJK support) > > * Change the standard menu font to Batang > * Switch the image to Japanese language > > At this point the image blows up somewhere in > TextMorph>>authoringPrototype. But if you proceed and open a menu it > shows CJK-ish looking characters (not that I could tell if it's > correct ;-) > > In any case, using the current versions of TTCFont in 3.10.2-trunk I > was able to produce the attached image which shows a bit of text > from Squeak's wikipedia entry in various languages. > > Yoshiki - for some strange reason it seems that some of the glyphs > in the Japanese entry are substituded by the default glyph (see the > fourth glyph in what I think is the phonetic transcription of Squeak). > > Do you have any idea if that is the expected behavior for Batang or > if there might be something wrong? It would be good if we could get > the text in Squeak to show up correctly, and I'm at a loss here > since I have no idea even what code ranges to look at ;-) > > Cheers, > - Andreas > _______________________________________________ > etoys-dev mailing list > etoys-dev(a)squeakland.org > http://lists.squeakland.org/mailman/listinfo/etoys-dev

July 31, 2009

Re: [Pharo-project] Kom not starting in Pharo-web image

by Schwab,Wilhelm K

Adrian, It appears to be a known problem. I reported it here, and (too lazy to check on who<g>) somebody pointed to some similar traffic on the Seaside list. There I saw things like "none of us noticed because we are all using the new conrol panel." See for example, the "MNU after clean install..." thread from 22-24 Jul. They also mention problems I do not recognize, but seems related. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Adrian Lienhard Sent: Friday, July 31, 2009 6:42 AM To: Pharo Development Subject: [Pharo-project] Kom not starting in Pharo-web image In the latest Pharo-web image on startup HttpService complains that 'a service is already running on port 8080' (stack trace attached). Damien said he loaded the latest versions of Seaside/Kom from SqueakSource. If I do "WAKomEncoded startOn: 8080" and restart the image, it works. Is this a known problem and if not, what would be the right place to report it? On the Seaside bug tracker? Cheers, Adrian

July 31, 2009