September 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] DoubleArray

by Henrik Sperre Johansen

On 22.09.2010 23:09, Schwab,Wilhelm K wrote: > Squeak, deliberately, does not have a double array class. Is that because there is some horrible reason it can't work, or because it won't work on certain platforms? If the goal is to pass it as a parameter to an external function, one way would be to subclass WordArray, storing(and reading) each Float in two elements, and have the endianness decided by Smalltalk endianness. Probably want a startUp method for the class to swap instances endianness if the platform has changed as well. > Put another way, should we add such a class, if only via an external heap or whatever would be needed to make it reliable? > > Bill More likely because no one has actually had a need for one. It's definitely not _needed_ in base, where normal arrays of floats would do the same job just as well, if not better. IMHO, if someone makes one, it so should probably be part of a package related to external interfacing. Cheers, Henry

Sept. 22, 2010

Re: [Pharo-project] DejaVu extra sizes Re: DemoMode should not change Fonts only sizes?

by Mariano Martinez Peck

On Tue, Sep 21, 2010 at 2:34 PM, Sven Van Caekenberghe <sven(a)beta9.be>wrote: > > On 21 Sep 2010, at 13:11, Fernando olivero wrote: > > > thanks Alain and Juan, CUIS fonts gave a excellent look and feel to > Gaucho! > > > > I highly recommend using them as the default Pharo font family > > > > Fernando > > > > pd: what i did is add the following line to the ConfigurationOfGaucho. > > > > spec > > blessing: #baseline; > > repository: 'http://www.squeaksource.com/gaucho'; > > package: 'DejaVuBitmapFonts' with:[ spec repository: ' > http://www.squeaksource.com/DejaVu'] ; > > .... > > This package works great (Pharo 1.1, Cog, OSX). Thanks for the pointer. > > Due to the size issue, I wouldn't include them all by default. > > Maybe we could make some clever set of MC packages that you can load for > each font size that you want ? > Or load the spec data from a file/url ? > You have a point here. Maybe we don't need to put all the families and all the size in the core....just the most used ones. Then, in the Dev image we can load all the rest, and the settings to set the Demo Fonts. what do you think alain? Anyway, all these fonts should be removed in #cleanUpForProduction I think. cheers mariano > > I think most people will only need one or two sizes. The fallback should > just be miminal. > > Sven > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Sept. 22, 2010

Re: [Pharo-project] Changes in external packages for Pharo 1.2

by Schwab,Wilhelm K

Mariano, I do not like the new inspector, but as long as you do not force me to use it, I'm happy to have it in the image. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Mariano Martinez Peck [marianopeck(a)gmail.com] Sent: Wednesday, September 22, 2010 4:36 PM To: Pharo Development; A friendly place where any question about pharo is welcome Subject: [Pharo-project] Changes in external packages for Pharo 1.2 Hi folks. I would like to write now the changes for the development image for Pharo 1.2. Right now I have the following: - Let (load) NewInspector in the image, but put the old one as the default. Several people were against NewInspector. I like it for example, but anyway, if it is present in the image then I would be able to use it. - Add Memory Monitor tool from Alexandre Bergel. - Add AutoTest from Laurent Laffont. - Add GoferProjectLoader from Esteban Lorenzano, to easily manage Metacello. For any package we include, it would be AWESOME to have: - tests - a Metacello configuration So, questions: 1) do you more ore less agree with them??? (we cannot be all agree with ALL items) 2) for package developers: do you agree we include all of them in PharoDev? will you help maitaining them? are they all MIT? (I think so) Please, confirm us this. 3) do you think there are more packages/projects we should include? What about, for example: - WorkingSet from Romain Robbes - Algernon (still doesn't work in 1.1) - TDDFacilties from Hernan Wilkinson - SimpleLogger from German Arduino I know this is not Dev, but I hope in Pharo1.2 we will have: - The new method finder from Benjamin that mixes both, and remove the old ones. - The new RecentSubmisons, and remove the old one. Thanks Mariano

Sept. 22, 2010

[Pharo-project] DoubleArray

by Schwab,Wilhelm K

Squeak, deliberately, does not have a double array class. Is that because there is some horrible reason it can't work, or because it won't work on certain platforms? Put another way, should we add such a class, if only via an external heap or whatever would be needed to make it reliable? Bill

Sept. 22, 2010

[Pharo-project] HashedCollection showstopper :(

by Igor Stasenko

Unfortunately, when preparing new finalization stuff, i got stuck with HashedCollection which is not yet integrated to Pharo. (Sets with nils also depending on that). In Squeak, old WeakRegistry does the trick by setting a #finalizer: to WeakKeyDictionary instance. Levente, can i ask you to give me a bits, (changesets or mcz packages), which contain HashedCollection refactorings. Or, we can follow an easier path, just extract the delta from two packages, which i found in mail archives: --- I uploaded two packages which contain this change. To load it evaluate the following: (Installer squeakfoundation project: 'inbox') install: 'Collections-ul.310.mcz'; install: 'Collections-ul.311.mcz' --- these are only related to WeakKeyDictionary, made by Levente to speedup old finalization. -- Best regards, Igor Stasenko AKA sig.

Sept. 22, 2010

[Pharo-project] Changes in external packages for Pharo 1.2

by Mariano Martinez Peck

Hi folks. I would like to write now the changes for the development image for Pharo 1.2. Right now I have the following: - Let (load) NewInspector in the image, but put the old one as the default. Several people were against NewInspector. I like it for example, but anyway, if it is present in the image then I would be able to use it. - Add Memory Monitor tool from Alexandre Bergel. - Add AutoTest from Laurent Laffont. - Add GoferProjectLoader from Esteban Lorenzano, to easily manage Metacello. For any package we include, it would be AWESOME to have: - tests - a Metacello configuration So, questions: 1) do you more ore less agree with them??? (we cannot be all agree with ALL items) 2) for package developers: do you agree we include all of them in PharoDev? will you help maitaining them? are they all MIT? (I think so) Please, confirm us this. 3) do you think there are more packages/projects we should include? What about, for example: - WorkingSet from Romain Robbes - Algernon (still doesn't work in 1.1) - TDDFacilties from Hernan Wilkinson - SimpleLogger from German Arduino I know this is not Dev, but I hope in Pharo1.2 we will have: - The new method finder from Benjamin that mixes both, and remove the old ones. - The new RecentSubmisons, and remove the old one. Thanks Mariano

Sept. 22, 2010

Re: [Pharo-project] Class comment in OB

by Schwab,Wilhelm K

Stef, I noticed it in 1.1, so it's probably old news. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of StÃ©phane Ducasse [stephane.ducasse(a)inria.fr] Sent: Wednesday, September 22, 2010 4:13 PM To: Pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] Class comment in OB did you check in 1.2 because this was fixed normally On Sep 22, 2010, at 9:43 PM, Schwab,Wilhelm K wrote: > I just pasted some typical C header file contents into a class comment: underscores were displayed as back arrows. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 22, 2010

Re: [Pharo-project] Pharo XMLRPC Project

by GermÃ¡n Arduino

Forgot it, I solved. Now, will build a Metacello configuration to make easy to install. The, will continue with the development. Cheers. 2010/9/21 GermÃ¡n Arduino <garduino(a)gmail.com>: > Hi Skrish: > > I'm trying to integrate all the current stuff on the XMLRPC repo on > Squeaksource [1] (integrating some previous work of me adding > bytestring support on the spy client). I need to understand exactly > all the prereq of your work because had some trouble loading on a > Pharo 1.1 image. > > Can you comment in which version of image are you working and the > exact package versions of the prereq? > > Thanks! > GermÃ¡n. > > > [1] I already asked permit to the authors of the current versions on > Squeaksource and they agree on we use this code base as a starting > point. All is MIT. Thanks Markus Fritsche, Christian Langreiter and > Cesar Lesc. > > > 2010/9/19 Serge Stinckwich <serge.stinckwich(a)gmail.com>: >> Hi Skrish, >> >> I'm quite interested to join your effort, because i would like to use >> XML-RPC for a project. >> Doing a ConfigurationOf... is not really difficult. I could do it. >> >> Maybe the modifications should be done on the original XML-RPC repository. >> >> Regards, >> >> 2010/9/20 Sudhakar Krishnamachari <skrishnamachari(a)gmail.com>: >>> Most welcome.. >>> >>> Â Also the link to a quick notes on this work is up at >>> >>> http://skrishnamachari.wordpress.com >>> >>> -Skrish >>> >>> ********************** >>> >>> Good! >>> The ESUG board decided to support german as originally mentioned >>> so he should probably join your effort. >>> >>> >>> Stef >>> >>>> Is there anything that is complete with respect to the XMLRPC Project..? >>>> >>>> Our notes: vibhu and I have put through the package ported from the >>>> available squeak work: >>>> >>>> http://skrishnamachari.wordpress.com/2010/09/19/pharo-xmlrpc-kick-start/ >>>> >>>> This is just the first shot at it.. >>>> >>>> Will come up with the ConfigurationOfXMLRPC shortly to bind the >>>> dependencies properly and fix anything that may required to take care of it >>>> as possible. >>>> >>>> -skrish >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> >> >> -- >> Serge Stinckwich >> UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam >> Every DSL ends up being Smalltalk >> http://doesnotunderstand.org/ >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > ================================================= > GermÃ¡n S. ArduinoÂ <gsa @ arsol.net>Â Â Twitter: garduino > Arduino Software & Web HostingÂ Â http://www.arduinosoftware.com > PasswordsProÂ http://www.passwordspro.com > ================================================= > -- ================================================= GermÃ¡n S. ArduinoÂ <gsa @ arsol.net>Â Â Twitter: garduino Arduino Software & Web HostingÂ Â http://www.arduinosoftware.com PasswordsProÂ http://www.passwordspro.com =================================================

Sept. 22, 2010

Re: [Pharo-project] Class comment in OB

by StÃ©phane Ducasse

did you check in 1.2 because this was fixed normally On Sep 22, 2010, at 9:43 PM, Schwab,Wilhelm K wrote: > I just pasted some typical C header file contents into a class comment: underscores were displayed as back arrows. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Sept. 22, 2010

[Pharo-project] Class comment in OB

by Schwab,Wilhelm K

I just pasted some typical C header file contents into a class comment: underscores were displayed as back arrows.

Sept. 22, 2010