- Pharo-dev - lists.pharo.org

[Pharo-project] [update 1.2] #12186
by Marcus Denker Oct. 7, 2010

Oct. 7, 2010

12186 ----- Issue 3071: fixing timestamp tests Issue 3068: Non portable SmalltalkImage>>platformName deprecationWarning Issue 3063: removing explain Issue 3039: There should not be any configuration on Core -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [ANN 1.2] #12173-12185 was: Re: Cog+NativeBoost Linux32 binaries available
by Marcus Denker Oct. 7, 2010

Oct. 7, 2010

On Oct 6, 2010, at 12:38 PM, StÃ©phane Ducasse wrote: > Cool > > Marcus will integrate your changes. I'm off for a full day meeting wuithout good internet connection until > thursday evening :( > Done. update #12173-12185 Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

[Pharo-project] [ANN 1.2] new pre-built core#12172
by Marcus Denker Oct. 7, 2010

Oct. 7, 2010

https://gforge.inria.fr/frs/download.php/27578/PharoCore-1.2-12172.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

1 0

Re: [Pharo-project] [Pharo-users] Pharo Talk ESUG 2010
by StÃ©phane Ducasse Oct. 7, 2010

Oct. 7, 2010

yes On Oct 7, 2010, at 12:50 AM, Mariano Martinez Peck wrote: > What do you think about having these presentations and videos available from the website?? maybe under Community or under a new section "Media" or even inside documentation. > > Adrian? > > On Wed, Oct 6, 2010 at 12:13 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > Hi, > > Now online: > > Slides Slideshare: http://www.slideshare.net/esug/pharo > Slides Download: http://www.marcusdenker.de/talks/10ESUG/2010PharoESUG.pdf > Video Web: http://esug2010.objectfusion.fr/tuesday.html > (part of all the Tuesday Videos) > Video for Download: > flv: http://www.marcusdenker.de/talks/10ESUG/esug2010_0914_denker.flv > mp4: http://www.marcusdenker.de/talks/10ESUG/esug2010_0914_denker.mp4 > > Marcus > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-users mailing list > Pharo-users(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-users > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: [Pharo-project] MicroSqueak [was System Tracer]
by StÃ©phane Ducasse Oct. 7, 2010

Oct. 7, 2010

On Oct 7, 2010, at 1:22 AM, Eliot Miranda wrote: > FInd attached. You want MicroSqueak-colonequal.st and the various MSqueak-.st files. This produces a 57k image. John's also given me a 2.0 development image which will run on a 3.8 VM. Let me know if you want that. Yes. I collect them. We studied a bootstrap of a subset of GNUST, chacharas and pharokernel > For me this is a proof of concept. What's needed is to define a headless core that contains the compiler, good error reporting to standard out, the core collection and numeric libraries and file support. Then we try and load packages into it and build up a headful image. Yes we are trying that with nicolas paez and gabriel barbuto (will stop in December). And in the process we are fixing everything we can. Stef

1 0

[Pharo-project] Morphic and the Player class in Pharo
by Robert Hawley Oct. 7, 2010

Oct. 7, 2010

I understand that Pharo has Etoys taken out of it, however, 'real' Morphic requires costume-player pairs. Can we have the Player class back in, or is there an alternative mechanism to take on the role of Player (maybe I've missed it)? This would be to enable coding of scripts using Smalltalk syntax (not to be confused with the Etoys tiled scripts).

1 0

[Pharo-project] FFI with 15+ args and Smallapack in Pharo
by Nicolas Cellier Oct. 6, 2010

Oct. 6, 2010

So, even if Bill did not help me a lot, and even if it does not help him neither, I finally did it. you can now test FFI calls with many arguments in latest Pharo 1.2 12172 The package is at http://www.squeaksource.com/Smallapack/Compiler-nicePharo12.245.mcz This also give anybody a chance to load Smallapack packages - if interested in debugging at machine code level ;) Nicolas ---------------------------------------------- Name: Compiler-nicePharo12.245 Author: nice Time: 7 October 2010, 12:39:29 am UUID: 9f3a6b0f-f25f-4510-b373-4dc99f39f3f6 Ancestors: Compiler-MarcusDenker.244 A version of Compiler with support for methods with many arguments including external FFI calls - For inclusion in Pharo 1.2

2 1

Oct. 6, 2010

have a look at the configuration you can pick noWeb. Stef On Oct 6, 2010, at 7:17 PM, Schwab,Wilhelm K wrote: > Damien, > > FWIW, I use Citezen but not Pier etc. I need a good BibTeX parser (which you provide) to parse incoming entries (typically originating from Google Scholar). I then add fields for my own comments (which get edited as I work) and a URL to full text and save the result to intermediate storage. To limit the scope of damage and because it does no harm otherwise, I store each BibTeX entry in a separate file and, on demand, glue them together into a largely unreadable mess (bibtex does fine with it) that I put adjacent to the offending manuscript as a .bib file. > > The way most journals of interest to me release full text articles, the workflow is awful. To not go afoul of copyright law, I store the articles out of public view (and not merely by obscurity). Worse than that, I have to make a local copy of the article and then upload it to the Seaside app, after which things start to work as I intended. I would much prefer to give the Seaside app a URL to the article, but things don't work that way. It's clunky, but the result is very useful to me. > > In short, Citezen is useful by itself, and you have at least one such user. The biggest problem I have had to date was that ConfigurationOfCitezen originally loaded Seaside,which was prematurely forcing 3.0 on me; the current configuration works great. I suspect I won't even notice the change to FileSystem. > > Thanks for a good tool!! > > Bill > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Damien Pollet [damien.pollet(a)inria.fr] > Sent: Wednesday, October 06, 2010 9:02 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Tests broken with Citezen > > On Wed, Oct 6, 2010 at 14:53, Alexandre Bergel <alexandre(a)bergel.eu> wrote: >> There is no implementor of #fieldKeysToRemove > > yes, probably a missing constant method. > I should also remove the dependency to Rio and use Filesystem instead, > but my next preoccupation is to get the scripting/validation to work. > You're free to hack on the Pier stuff. > > -- > Damien Pollet > type less, do more [ | ] http://people.untyped.org/damien.pollet > > _______________________________________________ > 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

2 1

Oct. 6, 2010

This is why the image does not use Smalltalk at: but the at: method is still defined in SmalltalkImage. > Stef, > > You raise a good point about helping to improve code, and I would MUCH rather see us try "aClass environment" for a while before introducing name spaces. Dolphin started leaning toward environments a long time ago, and suddenly "class names" were messages to the environment, and I was completely blown away by the potential power of it. I started in 2002 to remove hardcoded Smalltalk at: and replace them by self class environment for the reason that having the possibility to have different systemDictionary instance can help us for: bootstrapping the compiler, building atomic laoding like VW for example. > > So, I'm very open to the idea. However, I don't see any harm in ( Smalltalk at:#SomethingNotYetInstalled ), which I have had to use extensively in Migrate's image building code. Is there a better way to do the same thing? > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Igor Stasenko [siguctua(a)gmail.com] > Sent: Wednesday, October 06, 2010 12:31 PM > To: The general-purpose Squeak developers list > Cc: Pharo Development > Subject: Re: [Pharo-project] [squeak-dev] Re: Smalltalk at: #Foo - needs clarification > > On 6 October 2010 19:08, Andreas Raab <andreas.raab(a)gmx.de> wrote: >> On 10/6/2010 6:58 AM, Igor Stasenko wrote: >>> >>> Hello, >>> >>> just wanna ask, is this part of API will be deprecated in future? >>> (in Pharo, it put under 'to clean later' category). >>> >>> And if yes, then what will be correct (dialect-agnostic) way to access >>> globals? >>> >>> Smalltalk globals at: #Foo ? >>> >>> I thought that #at: #at:put: (and some others) >>> historically is a part of Smalltalk protocol, and should stay there to >>> support legacy code and cross-dialect code. >>> >>> >>> What you thoughts about it? >> >> The base dictionary access methods (#at:, #at:put:, #at:ifAbsent:) should >> remain in Smalltalk for compatibility. Then it's a matter of where that >> request is being delegated. >> > > Yes, i am also thinking that for compatibility it should stay. > > > Then i think in modern code, a most future-proof way is > > self class environment at: #Foo > > since it completely avoids any kind of early-binding. > > >> Cheers, >> - Andreas >> >> > > > > -- > Best regards, > Igor Stasenko AKA sig. > > _______________________________________________ > 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

2 1

Oct. 6, 2010

On Oct 6, 2010, at 7:18 PM, Eliot Miranda wrote: > > > On Wed, Oct 6, 2010 at 7:31 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > generate a new image. > > But that's not what it does. Yes I know gnerates = clone in my mail. > t merely clones an image, which is a long way form building an image form source. *That*'s a useful project. John Maloney's lovely MicroSqueak is a good starting point for ideas (basically have a copy of a kernel subset of the system in a namespace and generate a fresh image from that). Do you have a pointer on the code of john. We are looking at bootstrap code right now. > > On Oct 6, 2010, at 2:23 PM, Alexandre Bergel wrote: > > > Hi! > > > > What do you want to achieve? > > > > Cheers, > > Alexandre > > > > > > On 6 Oct 2010, at 05:36, Gabriel HernÃ¡n Barbuto wrote: > > > >> Hi > >> > >> Does anyone know where I can find the system tracer that is currently > >> in use in Pharo? > >> > >> Bests > >> Gabriel > >> > >> _______________________________________________ > >> 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 > > > _______________________________________________ > 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

1 0