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

[Pharo-project] Cleaning included Monticello repositories in PharoCore

by Mariano Martinez Peck

Hi folks: I was thinking that at least for the 1.0 release we should remove obsolete default repositories. I don't know if the word is "default" but I mean to those repositories that are already added when you download PharoCore 1.0 image. Those repositories are: 1) http://www.squeaksource.com/Pharo 2) http://www.squeaksource.com/PharoInbox 3) www.squeaksource.com/Installer 4) www.squeaksource.com/UIEnhancements 5) http://source.lukas-renggli.ch/flair 1) and 2) are ok. 3) I think we should remove it. 4) and 5) are there becuase Gofer and Polymorph are included in the Core image? What do you think ? Cheers Mariano

Feb. 14, 2010

Re: [Pharo-project] Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore

by Mariano Martinez Peck

On Sun, Feb 14, 2010 at 11:04 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > > > On Sun, Feb 14, 2010 at 10:09 PM, Yanni Chiu <yanni(a)rogers.com> wrote: > >> The last word on Metacello, that I recall reading in this list, is that >> it is an experiment. Has that changed? I'm happy enough to changed my >> habits, if that is the case. >> > > Metacello seems to be very stable, not an experiment any more. There are a > lot of big projects that are being managed with it such us Moose, GLASS, > PharoDev images, etc. Take a look to > http://www.squeaksource.com/MetacelloRepository > for all the available configurations. > Nevertheless, Metacello hasn't released the 1.0 stable version. It is still > in beta state, but I think the 1.0 will be very soon. > > >> In this case, my build script was loading Albatross, which had the >> dependency on FFI (so I was not directly interested in FFI). The script >> I had was pieced together somehow, long ago, and was using #loadFFI, >> which worked fine until a few days ago. >> >> BTW, since all FFI-Examples packages were removed from the FFI >> repository, even Metacello "versions" would fail because the package is >> no longer there. >> > > > Thank for the report. I have just commited a new version that fix this and > another couple of things. Can you tell me if it works ok for you ? > > > Gofer new > squeaksource: 'MetacelloRepository'; > package: 'ConfigurationOfFFI'; > load. > > ((Smalltalk at: #ConfigurationOfFFI) project version: '1.0') load. > > Sorry, It is this: ((Smalltalk at: #ConfigurationOfFFI) project version: '1.2') load. > > I have one failing test :( > testUlongRange > > > > > >> -- >> >> Yanni >> >> >> StÃ©phane Ducasse wrote: >> >> did you check the configurationOfFFI ??? >> >> Does it exist? >> >> >> >> Stef >> >> >> >> On Feb 14, 2010, at 7:45 AM, Yanni Chiu wrote: >> >> >> >>> Oops, this was on Pharo. I just checked Squeak3.11-9371-alpha.zip, and >> ScriptLoader>>loadFFI does not exist there. >> >>> >> >>> Anyhow, what is the proper way to load FFI? >> >>> >> >>> >> >>> Yanni Chiu wrote: >> >>>> "ScriptLoader loadFFI" now fails because the package FFI-Examples is >> no longer in the repository. >> >>>> Does ScriptLoader need to be updated, or was the package deleted >> accidentally? >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > >

Feb. 14, 2010

Re: [Pharo-project] Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore

by Mariano Martinez Peck

On Sun, Feb 14, 2010 at 10:09 PM, Yanni Chiu <yanni(a)rogers.com> wrote: > The last word on Metacello, that I recall reading in this list, is that > it is an experiment. Has that changed? I'm happy enough to changed my > habits, if that is the case. > Metacello seems to be very stable, not an experiment any more. There are a lot of big projects that are being managed with it such us Moose, GLASS, PharoDev images, etc. Take a look to http://www.squeaksource.com/MetacelloRepository for all the available configurations. Nevertheless, Metacello hasn't released the 1.0 stable version. It is still in beta state, but I think the 1.0 will be very soon. > In this case, my build script was loading Albatross, which had the > dependency on FFI (so I was not directly interested in FFI). The script > I had was pieced together somehow, long ago, and was using #loadFFI, > which worked fine until a few days ago. > > BTW, since all FFI-Examples packages were removed from the FFI > repository, even Metacello "versions" would fail because the package is > no longer there. > Thank for the report. I have just commited a new version that fix this and another couple of things. Can you tell me if it works ok for you ? Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfFFI'; load. ((Smalltalk at: #ConfigurationOfFFI) project version: '1.0') load. I have one failing test :( testUlongRange > -- > Yanni > > > StÃ©phane Ducasse wrote: > >> did you check the configurationOfFFI ??? > >> Does it exist? > >> > >> Stef > >> > >> On Feb 14, 2010, at 7:45 AM, Yanni Chiu wrote: > >> > >>> Oops, this was on Pharo. I just checked Squeak3.11-9371-alpha.zip, and > ScriptLoader>>loadFFI does not exist there. > >>> > >>> Anyhow, what is the proper way to load FFI? > >>> > >>> > >>> Yanni Chiu wrote: > >>>> "ScriptLoader loadFFI" now fails because the package FFI-Examples is > no longer in the repository. > >>>> Does ScriptLoader need to be updated, or was the package deleted > accidentally? > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 14, 2010

Re: [Pharo-project] 16rff broke 16r8e7

by Levente Uzonyi

On Sun, 14 Feb 2010, Nicolas Cellier wrote: > 2010/2/14 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> what does our wonderful ANSI standard mentions? > > Base 2 to 36 with letter A to Z. > Nothing about a-z. But nothing against it. At 3.5.6 the BNF allows only uppercase letters (uppercaseAlphabetic). Lowercase letters are not valid. Levente > > In the rationale, 10e10 is not allowed (Squeak), nor 1.0q (VW) > >>> >>>> Previous usage of e notation was far better because just extending an >>>> existing syntax, not creating a new one. >>>> Maybe you'll have other ideas... >>> >>> Stef >> >> _______________________________________________ >> 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 >

Feb. 14, 2010

Re: [Pharo-project] web services, pharo

by StÃ©phane Ducasse

I really like the idea of scripting and gluing together behavior. What I would love to be able to do is to use the webcam of my machine to scan a book ISBN number and fetch all the data from a given provider. Does anybody have an idea how we could plug all that together. Stef On Feb 14, 2010, at 8:45 PM, laurent laffont wrote: > Thanks for help and .... enjoy :) http://pharocasts.blogspot.com/2010/02/rest-xml-parsing-and-photos.html > > > Laurent Laffont > > > On Sun, Feb 14, 2010 at 1:20 PM, laurent laffont <laurent.laffont(a)gmail.com> wrote: > > > Make sure that the stream is binary: > SketchMorph fromStream: ('http://lh3.ggpht.com/_BvlW9mJ6MFc/R-p4PtCKitI/AAAAAAAAA1A/jySYN6rz_pc/DSC00…' asUrl retrieveContents contents asByteArray readStream) > > > Levente > > > It works ! Thank you ! You've just saved a screencast :) > > Laurent Laffont > > > > > > > Laurent Laffont > > > 2010/2/13 Mariano Martinez Peck <marianopeck(a)gmail.com> > > I think he talks about this one > > http://coweb.cc.gatech.edu/squeakbook/ > > > 2010/2/13 laurent laffont <laurent.laffont(a)gmail.com> > > Which web page ? > > Laurent Laffont > > > > On Sat, Feb 13, 2010 at 3:42 PM, StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr> wrote: > > laurent have a look in the network chapter of the new blue book > (collective book available on web page) > because I do not remember but you could find some snippets going in the > same sense. > > Stef > > On Feb 13, 2010, at 3:29 PM, laurent laffont wrote: > > (SketchMorph fromStream: > ('http://code.google.com/p/pharo/logo' > asUrl retrieveContents contentStream)) openInWorld > > > _______________________________________________ > 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 > > > > _______________________________________________ > 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Feb. 14, 2010

Re: [Pharo-project] 16rff broke 16r8e7

by Nicolas Cellier

2010/2/14 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> >>> As you may know, with 16rff change, we cannot anymore use a radix >>> notation combined with an exponent notation. >>> At least for base > 14, the exponent letter is taken as an ordinary digit. >> >> do you know how this is handled in VW? >> >> Stef 16rff is accepted 2r1e31 raise an Error explicitely stating exponent can't be mixed with radix in VW >> >>> The options are: >>> >>> 1) revert the change >>> >>> 2) abandon combined radix+exponent notation >>> all the code for printing Float with different radix, and also for >>> scanning can be removed >>> Or I can provide a subclass of SqNumberParser for backward compatibility. >>> >>> 3) find a new syntax for radix+exponent >>> >>> For example, 16r7f_e6 16r7f^6 16r7f#6 >>> None of these is ambiguous with existing code. >>> >>> Or maybe use an uppercase R for uppercase only digits... >>> >>> 4) use q exponent to at least enable base 16 >>> This is hackish and not universal, but I guess hardly anybody ever >>> used a base > 16. >> >> what would be the example 16r7Fq6 >>> >>> ------------------------------------- >>> >>> What would squeak/pharo folks choose ? >>> >>> ------------------------------------- >>> Personnally, I'm OK with 1) and 2). >>> But 2) deserves a bit more discussion >>> After all this is a change of Squeak syntax. >>> I find Dan's notation educative and fun, especially for writing tests. >>> But it is a non portable Squeakish thing, rarely used, and it does not >>> really has much value for industrial usage, >> >> I read the mail than juan mentioned but I could not understand or I read another one :) He has preserved Dan's extension. 16rff forbidden 16r7Fe6 = 16r7F000000 >> >>> On the other hand, is it really necessary to parse 16rff ? >> >> sounds like? >> >>> I dislike 3) because I find my own propositions bad. >>> Also, if we remove Squeak-specific syntax for compatibility reasons, >>> why the hell adding a new uncompatible syntax? >> >> Yes >> what does our wonderful ANSI standard mentions? Base 2 to 36 with letter A to Z. Nothing about a-z. But nothing against it. In the rationale, 10e10 is not allowed (Squeak), nor 1.0q (VW) >> >>> Previous usage of e notation was far better because just extending an >>> existing syntax, not creating a new one. >>> Maybe you'll have other ideas... >> >> Stef > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 14, 2010

Re: [Pharo-project] 16rff broke 16r8e7

by StÃ©phane Ducasse

> > I'd go for 1). Squeak extends the ANSI standard one way, while VW does in > another. If you want portable code, use the standard compatible syntax: > 16rFF. probably. at least digitValue: was fixed in the process. > 2) is acceptable, but I wouldn't do it.

Feb. 14, 2010

Re: [Pharo-project] Fwd: [squeak-dev] Re: ScriptLoader loadFFI doesn't work anymore

by Yanni Chiu

The last word on Metacello, that I recall reading in this list, is that it is an experiment. Has that changed? I'm happy enough to changed my habits, if that is the case. In this case, my build script was loading Albatross, which had the dependency on FFI (so I was not directly interested in FFI). The script I had was pieced together somehow, long ago, and was using #loadFFI, which worked fine until a few days ago. BTW, since all FFI-Examples packages were removed from the FFI repository, even Metacello "versions" would fail because the package is no longer there. -- Yanni StÃ©phane Ducasse wrote: >> did you check the configurationOfFFI ??? >> Does it exist? >> >> Stef >> >> On Feb 14, 2010, at 7:45 AM, Yanni Chiu wrote: >> >>> Oops, this was on Pharo. I just checked Squeak3.11-9371-alpha.zip, and ScriptLoader>>loadFFI does not exist there. >>> >>> Anyhow, what is the proper way to load FFI? >>> >>> >>> Yanni Chiu wrote: >>>> "ScriptLoader loadFFI" now fails because the package FFI-Examples is no longer in the repository. >>>> Does ScriptLoader need to be updated, or was the package deleted accidentally?

Feb. 14, 2010

Re: [Pharo-project] 16rff broke 16r8e7

by Levente Uzonyi

On Sun, 14 Feb 2010, Nicolas Cellier wrote: > As you may know, with 16rff change, we cannot anymore use a radix > notation combined with an exponent notation. > At least for base > 14, the exponent letter is taken as an ordinary digit. > The options are: > > 1) revert the change > > 2) abandon combined radix+exponent notation > all the code for printing Float with different radix, and also for > scanning can be removed > Or I can provide a subclass of SqNumberParser for backward compatibility. > > 3) find a new syntax for radix+exponent > > For example, 16r7f_e6 16r7f^6 16r7f#6 > None of these is ambiguous with existing code. > > Or maybe use an uppercase R for uppercase only digits... > > 4) use q exponent to at least enable base 16 > This is hackish and not universal, but I guess hardly anybody ever > used a base > 16. > > ------------------------------------- > > What would squeak/pharo folks choose ? > > ------------------------------------- > Personnally, I'm OK with 1) and 2). > But 2) deserves a bit more discussion > After all this is a change of Squeak syntax. > I find Dan's notation educative and fun, especially for writing tests. > But it is a non portable Squeakish thing, rarely used, and it does not > really has much value for industrial usage, > On the other hand, is it really necessary to parse 16rff ? > > I dislike 3) because I find my own propositions bad. > Also, if we remove Squeak-specific syntax for compatibility reasons, > why the hell adding a new uncompatible syntax? > Previous usage of e notation was far better because just extending an > existing syntax, not creating a new one. > Maybe you'll have other ideas... I'd go for 1). Squeak extends the ANSI standard one way, while VW does in another. If you want portable code, use the standard compatible syntax: 16rFF. 2) is acceptable, but I wouldn't do it. Levente > > Nicolas > > ------------------------------------- > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 14, 2010

[Pharo-project] issue 1499 in PharoDev 1.0 ???

by Mariano Martinez Peck

Hi Frederic. I was looking for the packages to next PharoDev and I noticed to commited a new version of NewInspector (NewInspector-FredericPluquet.57) Do you know if this also work in 1.0 so that I can include the fix ? Thanks Mariano

Feb. 14, 2010