- Pharo-dev - lists.pharo.org

[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

[Pharo-project] [update] #10402

by Marcus Denker

10402 ----- Issue 1019: 0006579: String>>#findLastOccuranceOfString:startingAt: isBuggedWhen: [substring first=substring last] Issue 1021: References to 'squeak' Issue 1015: The BlockClosureTests package is empty and should be removed Issue 1016: Package FreeType overrides methods in CanvasCharacterScanner which is not in the core Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

July 31, 2009

Re: [Pharo-project] Why I use Pharo

by Alexandre Bergel

> The fun thing is that this route supports both results that are far- > fetched researchy > prototypes (see my publications page, for example), as well as down- > to- > earth, usable, > stable artifacts. This is a very nice mixture, I have to admit. And very rare as well Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

July 31, 2009

Re: [Pharo-project] Beginner Tasks

by StÃ©phane Ducasse

> I have wanted to help Pharo, but being an un-skilled Smalltalk > programmer, Hi Robert you can help. Everybody can help. Reporting a bug clearly helps Commenting that a bug is reproducible helps Start small :) Point us to cool python techno we should get inspired too. > and having other Python-based projects that were more urgent, I > haven't done > much about it. However, this 'testServer' caught my eye, because > I've been > thinking about creating such a thing for my own Python-based use. > Please > let me know if what I propose is what you intend. If so I may be > willing to > try and create something for Pharo to use.

July 31, 2009

Re: [Pharo-project] Why I use Pharo

by Marcus Denker

On 31.07.2009, at 07:35, John Escobedo wrote: > I'm super excited to hear about Pharo 1.0 beta. I thought I'd post > about why I'm using Pharo. > > I started using Pharo about 2 weeks ago and have finally started > writing small programs in Smalltalk again. > > 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. Thanks for your kind words! > Looking back, it looks like Pharo > happened. > I think there was even some gap in between... and what I wonder always is this: What would habe happened if we would have just done the next small step for 10 years with Squeak as we now did for 13 Month with Pharo? The more I learn about software development, project management and life in general, the more I am convinced that incremental, evolutionary progress is the only way to move forward. And from that follows directly many very interersting questions both for research and engineering: How do we analyse the old to be able to move it forward? Can we provide better tools for evolution? Can new language features help to build evolvable systems? The fun thing is that this route supports both results that are far- fetched researchy prototypes (see my publications page, for example), as well as down-to- earth, usable, stable artifacts. This is a very nice mixture, I have to admit. Marcus -- Marcus Denker -- marcus(a)2denker.de http://www.2denker.de 2denker UG (haftungsbeschrÃ¤nkt) Sitz KÃ¶ln Amtsgericht - Registergericht - KÃ¶ln, HRB 65065 GeschÃ¤ftsfÃ¼hrer: Christian Denker und Dr. Marcus Denker

July 31, 2009

Re: [Pharo-project] A question about Gofer

by StÃ©phane Ducasse

On Jul 30, 2009, at 9:15 PM, Lukas Renggli wrote: >> I would like to know if Gofer is also working deconnected. > > If you specify a local repository, then yes. Otherwise Gofer currently > requires the repository to be accessible. I always have a local one. >> I often work in places where internet connection is not working and I >> would love >> to see my loading scripts checking my local cache for loading >> packages. > > Checking multiple repositories leads to even worse unpeedictable > behavior, when no exact version is specified. Yes I imagine. Usually I only have one and my cache >> If this is not there yet, Lukas may be I could add this features to >> Gofer? > > It can already be done when specifying a repository group. The API > needs to be improved to coveniently use it though. Ok I will try to find some time before esug to have a look at that. > > Lukas > > >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > Lukas Renggli > http://www.lukas-renggli.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] [ANN] Pharo 1.0 Beta

by Marcus Denker

On 31.07.2009, at 05:44, Tudor Girba wrote: > I just spotted that the hint text of the "Quit" menu item says: > > "Quit out of Squeak" > > Similarly for "Save and quit". Perhaps this could be changed? Yes, the Mac menus need to be improved. e.g. there should be just one Pharo menu instead of "Squeak VM" and "Files"... I will have a look at that soon. Marcus -- Marcus Denker -- marcus(a)2denker.de http://www.2denker.de 2denker UG (haftungsbeschrÃ¤nkt) Sitz KÃ¶ln Amtsgericht - Registergericht - KÃ¶ln, HRB 65065 GeschÃ¤ftsfÃ¼hrer: Christian Denker und Dr. Marcus Denker

July 31, 2009

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

by Adrian Lienhard

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

[Pharo-project] Why I use Pharo

by John Escobedo

I'm super excited to hear about Pharo 1.0 beta. I thought I'd post about why I'm using Pharo. I started using Pharo about 2 weeks ago and have finally started writing small programs in Smalltalk again. 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. Thanks so much to everyone.

July 31, 2009