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

Re: [Pharo-project] [squeak-dev] [ANN] Magma 1.1r2

by Ramiro Diaz Trepat

This is great new, Thanks Chris 2010/7/30 Chris Muller <asqueaker(a)gmail.com> > > Good, I will base the configuration packages version number on this sar. > > It will be named 1.1r2 or will be 1.1r3 (due to the deletion of a test > > in the package you mentioned before, maybe isn't big enough to deserve a > > new release and it was a "hurry" release maybe can we consider this a > > typo and consider the sar the official 1.1r2 release) > > Yes, it was just the removal of one test, so please stay with 1.1r2. > I'm pretty certain it's not going to affect any of the millions of > folks who have downloaded Magma since yesterday... :) > _______________________________________________ > Magma mailing list > Magma(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma >

July 30, 2010

Re: [Pharo-project] SqueakSSL fails...

by Andrei Stebakov

Apparently #readInto:startingAt:count: is not supported by ReadStream Pharo 1.1... On Fri, Jul 30, 2010 at 5:46 PM, Andrei Stebakov <lispercat(a)gmail.com> wrote: > Well, I put it there when Pharo was running. Now that I restarted > Pharo I got a different error: > When I execute "WebClient httpGet: > 'https://www.google.com/search?q=squeak'." I got: > > ReadStream(Object)>>doesNotUnderstand: #readInto:startingAt:count: > SecureSocketStream>>receiveDataInto:startingAt: > SecureSocketStream>>receiveAvailableData > SecureSocketStream(SocketStream)>>upToAll: > WebResponse>>readFrom: > WebClient>>sendRequest:content:size: > WebClient>>sendRequest: > WebClient>>httpGet:do: > WebClient>>httpGet: > WebClient class>>httpGet: > UndefinedObject>>DoIt > Compiler>>evaluate:in:to:notifying:ifFail:logged: > [] in TextMorphForShoutEditor(ParagraphEditor)>>evaluateSelection > BlockClosure>>on:do: > TextMorphForShoutEditor(ParagraphEditor)>>evaluateSelection > TextMorphForShoutEditor(ParagraphEditor)>>doIt > [] in TextMorphForShoutEditor(ParagraphEditor)>>doIt: > TextMorphForShoutEditor(ParagraphEditor)>>terminateAndInitializeAround: > TextMorphForShoutEditor(ParagraphEditor)>>doIt: > TextMorphForShoutEditor(ParagraphEditor)>>dispatchOnKeyEvent:with: > > > > > On Fri, Jul 30, 2010 at 4:47 PM, Andrei Stebakov <lispercat(a)gmail.com> wrote: >> I've downloaded the SqueakSSL.dll plugin and put it in the root folder. >> Also I've downloaded >> SqueakSSL-Core >> SqueakSSL-Plugin >> SqueakSSL-Tests >> >> All tests passed. >> Now when I try to execute "SqueakSSL google: 'Squeak'." >> It fails creating the module in >> >> primitiveSSLCreate >> Â Â Â Â "Primitive. Creates and returns a new SSL handle" >> >> Â Â Â Â <primitive: 'primitiveCreate' module: 'SqueakSSL'> >> Â Â Â Â ^self primitiveFailed >> >> How can I fix it? >> >> Thank you, >> Andrei >> >

July 30, 2010

Re: [Pharo-project] SqueakSSL fails...

by Andrei Stebakov

Well, I put it there when Pharo was running. Now that I restarted Pharo I got a different error: When I execute "WebClient httpGet: 'https://www.google.com/search?q=squeak'." I got: ReadStream(Object)>>doesNotUnderstand: #readInto:startingAt:count: SecureSocketStream>>receiveDataInto:startingAt: SecureSocketStream>>receiveAvailableData SecureSocketStream(SocketStream)>>upToAll: WebResponse>>readFrom: WebClient>>sendRequest:content:size: WebClient>>sendRequest: WebClient>>httpGet:do: WebClient>>httpGet: WebClient class>>httpGet: UndefinedObject>>DoIt Compiler>>evaluate:in:to:notifying:ifFail:logged: [] in TextMorphForShoutEditor(ParagraphEditor)>>evaluateSelection BlockClosure>>on:do: TextMorphForShoutEditor(ParagraphEditor)>>evaluateSelection TextMorphForShoutEditor(ParagraphEditor)>>doIt [] in TextMorphForShoutEditor(ParagraphEditor)>>doIt: TextMorphForShoutEditor(ParagraphEditor)>>terminateAndInitializeAround: TextMorphForShoutEditor(ParagraphEditor)>>doIt: TextMorphForShoutEditor(ParagraphEditor)>>dispatchOnKeyEvent:with: On Fri, Jul 30, 2010 at 4:47 PM, Andrei Stebakov <lispercat(a)gmail.com> wrote: > I've downloaded the SqueakSSL.dll plugin and put it in the root folder. > Also I've downloaded > SqueakSSL-Core > SqueakSSL-Plugin > SqueakSSL-Tests > > All tests passed. > Now when I try to execute "SqueakSSL google: 'Squeak'." > It fails creating the module in > > primitiveSSLCreate > Â Â Â Â "Primitive. Creates and returns a new SSL handle" > > Â Â Â Â <primitive: 'primitiveCreate' module: 'SqueakSSL'> > Â Â Â Â ^self primitiveFailed > > How can I fix it? > > Thank you, > Andrei >

July 30, 2010

Re: [Pharo-project] [squeak-dev] [ANN] Magma 1.1r2

by Chris Muller

> Good, I will base the configuration packages version number on this sar. > It will be named 1.1r2 or will be 1.1r3 (due to the deletion of a test > in the package you mentioned before, maybe isn't big enough to deserve a > new release and it was a "hurry" release maybe can we consider this a > typo and consider the sar the official 1.1r2 release) Yes, it was just the removal of one test, so please stay with 1.1r2. I'm pretty certain it's not going to affect any of the millions of folks who have downloaded Magma since yesterday... :)

July 30, 2010

[Pharo-project] running Magma tests in 1.1

by Chris Muller

To run the test-suite for Magma 1.1r2 in Pharo: - Proceed past two warnings about "FlapTab" when loading Magma. - Revert FileDirectory>>#fileExists: to the prior version. - Remove #testClassSchemaUpgrades. - Load OSProcess. The second and third steps, above, I believe may be regressions in Pharo 1.1. In Pharo 1.1: FileDirectory default fileExists: '/bin/sh' "---> false" but the file does, indeed, exist as a soft-link. Squeak answers true and, I'll bet, so does Pharo 1.0, so I'm not sure if there is a problem here or not. #testClassSchemaUpgrades tests Magma's ability to keep up with class-schema changes in the image. Usually class-schemas change only in development, not production systems so maybe it's not a big deal. But still, it can be very convenient develop new class schemas while connected to a persistent Magma store. Magma makes use of the SystemChangeNotifier to do this. I don't know if Pharo cleaned something with SystemChangeNotifier or a regression happened, but I don't have time to debug it right now. Certainly, if there is a problem with Magma I will fix it, but I'm not convinced of that yet. - Chris

July 30, 2010

Re: [Pharo-project] [squeak-dev] [ANN] Magma 1.1r2

by Miguel Enrique CobÃ¡ MartÃnez

El vie, 30-07-2010 a las 15:55 -0500, Chris Muller escribiÃ³: > Hi, > > >> 'Ma files additions-cmm.13.mcz'. > > > > This is a new package. What other package depends on it? > > The #fullBackupTo: method in Magma server uses a MaClientProcess, a > Process-wrapper that can broadcasts its progress, among other things. > MaClientProcess is part of the "Ma contextual search" package, which > depends on "Ma files additions" for its use of the #directoryTreeDo: > method (for something else unrelated to Magma). The "Ma" suite of > packages do serve several projects, not just Magma, even if some > methods seem to be "unused" from Magma's perspective. Ok. I will update the dependency graph of the ConfigurationOfMagma with this info. > > > Why on MagmaTester? I thought that for released versions, they were > > always on Magma repository and that MagmaTester was for your beta and > > not released yet versions, isn't that true anymore? > > It is still true. My objective was to get something out as quickly as > possible to try to accommodate the Pharo release schedule. I always > start at "Magma tester" I have now copied them to the other > repository. Thanks for your continued assistance on the Pharo side of > things. > > BTW: note there is an updated version of Magma tester which removed > an old unused test. Perfect. I will release a new ConfigurationOfMagma with support for this new version 1.1r2 with packages taken all from Magma repo in squeaksource. > > > In repository squeaksource.com/WriteBarrier, there are packages: > > > > WriteBarrier-tbn.28.mcz > > WriteBarrier-cmm.27.mcz > > > > Then in MagmaTester repository there is > > > > WriteBarrier-cmm.28.mcz > > > > and in Magma there is > > > > WriteBarrier-pmm.26.mcz > > The correct one to use is WriteBarrier-cmm.28.mcz. I do not have > update access to the "WriteBarrier" project on SqueakSource. Perhaps > Phillip will let me have access or copy it there for me? Please Phillipe, +1 to adding Chris to the developers of WriteBarrier as Magma is a main user of WriteBarrier. This way the last version will be on WriteBarrier repo (authoritative) and copied also in Magma repo (in case WriteBarrier disappear someday). > > I had tried to use WriteBarrier-tbn.28.mcz but there were still > underscore assignments in there. Therefore, since I had to "do some > work" anyway, I went ahead and reverted back to cmm.27, got out the > trusty ol'e FixUnderscores package, since it works and also preserves > the accounting information which, as you know, is important to me. > > > So I don't understand either, what is the policy here. Is the package > > modified, and pushed to the original repo (WriteBarrier) and *then* > > copied to MagmaTester and Magma or > > The rate of Magma releases has slowed considerably because it has been > stable and I've been working on other projects that employ Magma > lately rather than working very much on Magma itself. So I might like > at some point to retire "MagmaTester"; delete it. Feedback is > appreciated. > I vote for deleting it, because every released version is on Magma repo (I think) so there is less noise and less mistakes having some packages in one repo and others in other that form a release. > > I have prepared an update to the configuration of Magma for 1.1r2 with > > the preferences corrected but I would like to have all the packages in > > WriteBarrier and in Magma (that I consider the releases repositories, or > > at least, everything on Magma so that the configuration doesn't refer to > > MagmaTester altogether). What do you think? > > OK, I've copied them to "Magma" too. I will upload the SAR file to > SqueakMap too, soonish. Good, I will base the configuration packages version number on this sar. It will be named 1.1r2 or will be 1.1r3 (due to the deletion of a test in the package you mentioned before, maybe isn't big enough to deserve a new release and it was a "hurry" release maybe can we consider this a typo and consider the sar the official 1.1r2 release) Thanks for the answers > > - Chris > _______________________________________________ > Magma mailing list > Magma(a)lists.squeakfoundation.org > http://lists.squeakfoundation.org/mailman/listinfo/magma -- Miguel CobÃ¡ http://miguel.leugim.com.mx

July 30, 2010

Re: [Pharo-project] [squeak-dev] [ANN] Magma 1.1r2

by Chris Muller

Hi, >> 'Ma files additions-cmm.13.mcz'. > > This is a new package. What other package depends on it? The #fullBackupTo: method in Magma server uses a MaClientProcess, a Process-wrapper that can broadcasts its progress, among other things. MaClientProcess is part of the "Ma contextual search" package, which depends on "Ma files additions" for its use of the #directoryTreeDo: method (for something else unrelated to Magma). The "Ma" suite of packages do serve several projects, not just Magma, even if some methods seem to be "unused" from Magma's perspective. > Why on MagmaTester? I thought that for released versions, they were > always on Magma repository and that MagmaTester was for your beta and > not released yet versions, isn't that true anymore? It is still true. My objective was to get something out as quickly as possible to try to accommodate the Pharo release schedule. I always start at "Magma tester" I have now copied them to the other repository. Thanks for your continued assistance on the Pharo side of things. BTW: note there is an updated version of Magma tester which removed an old unused test. > In repository squeaksource.com/WriteBarrier, there are packages: > > WriteBarrier-tbn.28.mcz > WriteBarrier-cmm.27.mcz > > Then in MagmaTester repository there is > > WriteBarrier-cmm.28.mcz > > and in Magma there is > > WriteBarrier-pmm.26.mcz The correct one to use is WriteBarrier-cmm.28.mcz. I do not have update access to the "WriteBarrier" project on SqueakSource. Perhaps Phillip will let me have access or copy it there for me? I had tried to use WriteBarrier-tbn.28.mcz but there were still underscore assignments in there. Therefore, since I had to "do some work" anyway, I went ahead and reverted back to cmm.27, got out the trusty ol'e FixUnderscores package, since it works and also preserves the accounting information which, as you know, is important to me. > So I don't understand either, what is the policy here. Is the package > modified, and pushed to the original repo (WriteBarrier) and *then* > copied to MagmaTester and Magma or The rate of Magma releases has slowed considerably because it has been stable and I've been working on other projects that employ Magma lately rather than working very much on Magma itself. So I might like at some point to retire "MagmaTester"; delete it. Feedback is appreciated. > I have prepared an update to the configuration of Magma for 1.1r2 with > the preferences corrected but I would like to have all the packages in > WriteBarrier and in Magma (that I consider the releases repositories, or > at least, everything on Magma so that the configuration doesn't refer to > MagmaTester altogether). What do you think? OK, I've copied them to "Magma" too. I will upload the SAR file to SqueakMap too, soonish. - Chris

July 30, 2010

[Pharo-project] SqueakSSL fails...

by Andrei Stebakov

I've downloaded the SqueakSSL.dll plugin and put it in the root folder. Also I've downloaded SqueakSSL-Core SqueakSSL-Plugin SqueakSSL-Tests All tests passed. Now when I try to execute "SqueakSSL google: 'Squeak'." It fails creating the module in primitiveSSLCreate "Primitive. Creates and returns a new SSL handle" <primitive: 'primitiveCreate' module: 'SqueakSSL'> ^self primitiveFailed How can I fix it? Thank you, Andrei

July 30, 2010

Re: [Pharo-project] help with Glamour

by Felipe Ignacio Valverde Campos

nice, that works :) ! we are using Glamour on AspectMaps (http://www.squeaksource.com/AspectMaps.html) for the main UI and another to import projects (Java and AspectJ) on Moose in order to visualize using Mondrian more information on http://pleiad.cl/research/software/aspectmaps thanks for the help and tips ! El jue, 29-07-2010 a las 07:58 +0200, Tudor Girba escribiÃ³: > Hi Felipe, > > The result of opening a browser is a window. > > So, you could use something like this: > > browser := GLMTabulator new. > ... > window := browser openOn: ... > window maximize. > ... > window delete. > > > Could I ask in what context you are using Glamour? Also, a better > forum for discussing these issues is the moose-dev mailing list: > - address: moose-dev(a)iam.unibe.ch > - registration: https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > Cheers, > Doru > > > On 28 Jul 2010, at 21:04, Alexandre Bergel wrote: > > > Hi Felipe, > > > > No idea, but this is good to see you here! > > > > Alexandre > > > > > > On 28 Jul 2010, at 18:47, Felipe Ignacio Valverde Campos wrote: > > > >> Hi, i'm beginner on this tools, so i need your help please :) > >> i have some doubts about Glamour, specificaly with GLMTabulator. > >> > >> how can i set the window size ? > >> and how can i close it without pressing the X ? > >> > >> thanks > >> -- > >> http://www.dcc.uchile.cl/~fvalverd/public_key.asc > >> Estudiante de IngenierÃa Civil en ComputaciÃ³n. > >> Facultad de Ciencias FÃsicas y MatemÃ¡ticas. > >> Universidad de Chile. > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > > Alexandre Bergel http://www.bergel.eu > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Reasonable is what we are accustomed with." > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- http://www.dcc.uchile.cl/~fvalverd/public_key.asc Estudiante de IngenierÃa Civil en ComputaciÃ³n. Facultad de Ciencias FÃsicas y MatemÃ¡ticas. Universidad de Chile.

July 30, 2010

Re: [Pharo-project] CogVM as official Pharo VM?

by Eliot Miranda

On Fri, Jul 30, 2010 at 11:55 AM, Martin McClure <martin(a)hand2mouse.com>wrote: > On 07/30/2010 11:28 AM, Eliot Miranda wrote: > > [...] > > > >> Excellent!! Just by curious, your idea, or what you did in VW, was >> to be able to put SmallFloats directly inside the address ? just >> like we do nowadays with SmallInteger ? >> >> >> Yes. The scheme provides IEEE double precision but with a smaller >> exponent so the range is the same as the 32-bit single-precision range. >> i.e. 3 bits are used as tag bits to distinguish SmallInteger >> SmallFloat Character and objects. That leaves 1 bit for sign, 52 bits >> for the mantissa and 8 bits for the exponent. The use of 3 tag bits >> comes from 64-bit pointers being 8-byte aligned and so having the least >> significant 3 bits 0. I don't want to defend that choice now just to >> give you a flavour of the representation: >> >> | 8-bit exponent | 52 bit mantissa | sign | tags | >> > > A few more words on the VW SmallDouble implementation: We also use this > representation in GemStone; it works very well. > > This representation exactly represents a subset of the possible IEEE > doubles. It's the "common" 1/8th of the total range, with the addition of > +-0.0. Non-zero numbers very close to zero or very far from zero overflow to > normal Float objects in a manner very similar to the way > SmallInteger/LargeInteger work. The infinities and NaNs also must be > represented as normal Floats. > > Because between SmallDouble and Float all IEEE doubles can be represented, > all floating-point computations give the correct (per IEEE) result, but you > save memory and computation is generally faster because you don't access as > many bytes in main memory. > and I should say that while I came up with the scheme it was Martin who very patiently debugged it. Without Martin's help it would have been a train wreck. Thanks again, Martin! > Regards, > > -Martin >

July 30, 2010