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

Re: [Pharo-project] [squeak-dev] Cog+NativeBoost Linux32 binaries available

by Fernando olivero

>>>> Also, the missing class is NBGLCurveRenderer, which i moved to >>>> NBOpenGL-Rome package. >>>> I did a snapshot of it. But it depends on RomeCanvas class(es) , which >>>> is part of Athens.. >>>> But just ignore that for now and load it. For demo, you need only >>>> NBGLCurveRenderer which not rely on any Rome-specific stuff. >> >> Just for curiosity, why this dependance on Rome? To end up providing a Canvas were all the rendering is performed by OpenGL and you text rendering class ? > > > A NBGLCurveRenderer is actually an experiment, which should be a part > of something bigger (read Rome). > So, that's why i moved it there, breaking demo :) > The demo works just fine now! > I plan to implement an OpenGL backend for canvas, which implements > Rome protocol. > And then implement Morphic which using rome-canvas for rendering.. > And then implement brand-new zoomable UI in it.. > > (i have a big plans)... :) > I was hoping you did! Questions: 1.Once you have a NBOpenGLRomeCanvas , how do you plan to implement the zoomable UI? On which layer of abstraction? (Canvas or Morphic ?) Is there going to be a "camera" abstraction? ( just like Lumiere ) or who will know its current z transformation? 2. Regarding Text, will you reuse Paragraph and Editor already present in the system, or use an external library like Pango? I was looking at the True Type font rendering demo, and everything seems pretty much into place, and now the "paragraph" layer must be implemented. How can i help? (Eventually...) Fernando

Oct. 7, 2010

Re: [Pharo-project] [Pharo-users] Pharo Talk ESUG 2010

by Marcus Denker

On Oct 7, 2010, at 1:23 AM, GermÃ¡n Arduino wrote: > hehe, thanks! > > You will come to Smalltalks 2010 ? Yes, Mariano, Luc and me. > > I was thinking exactly in ask permit to use this one (and other > similars) to present Pharo in other contexts, for example in localgroups, etc. Normally all my talks are CC non-commercial share-alike... only that I often forget to put it in the slides... > That's perfectly allowed and even more, a ppt/keypoint template should be available. 2 days ago Marcus borrowed this one for my PhD first year evaliuation ;) Ok, I have put the keynote (zipped): http://marcusdenker.de/talks/10ESUG/ -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Oct. 7, 2010

[Pharo-project] Learning by download all the mcz files from a repository

by HwaJong Oh

I plan to study history of Metacello. For that I came up with an idea, what if i download all the mcz in the metacello repository on squeaksource. Then sort them by commit time stamp. installing very first version of Metacello to last version of Metacello-Help. Every moment of installation, see the difference by clicking "Changes" button of monticello browser. By doing it, i can grasp the idea, the indents of version and understand how the design has been changed and know the direction of change. What do you think of this idea? -HwaJong Oh- -- View this message in context: http://forum.world.st/Learning-by-download-all-the-mcz-files-from-a-reposit… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Oct. 7, 2010

Re: [Pharo-project] [Pharo-users] Pharo Talk ESUG 2010

by StÃ©phane Ducasse

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

Oct. 7, 2010

Re: [Pharo-project] MicroSqueak [was System Tracer]

by StÃ©phane Ducasse

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

Oct. 7, 2010

Re: [Pharo-project] Pointer types

by Igor Stasenko

On 7 October 2010 01:27, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: > Sig, > > Am I correct in taking this as a description of how to solve it with NB, not Squeak/Pharo FFI? Â That's ok, just want to know if there is an applicable lesson on FFI to be extracted. > > You say the NB callout generator knows nothing about types. Â Is that how it should be? Â The scenario I have in mind is a bogus type and whether that can/should be flagged at compile time vs. runtime. Â Maybe all it takes is a scan for a suitable handler before or after the method is compiled. Â I ask because I hit a related snag with FFI runtime errors being reported as coercion errors when in fact I had used errant types in the callout definitions. Â IIRC, Andreas patched the compiler to report the bogus types. > > > "Or, if you want make double* type to use it as a DoubleArray, then you can add an alias: > > MyClass>>externalTypeAlias: aTypeName > Â aTypeName = 'double*' ifTrue: [ ^ #DoubleArray ]. > Â ^ nil > > Then, any method which contains an FFI callout in MyClass, will use that alias." > > What is MyClass in the above? Â Is it the class holding the callout method, or it elsewhere in the chain? Â I ask because it could be a sore spot for maintenance/pluggability. Â I'm wondering how you and I would independently add such instructions. Â If it goes in the external type subclass, then it is probably fine; if it goes in a class that makes the call, we might stomp on each other. Â Make sense? Â My hunch is that you have it handled. > Its in an any class, which using FFI callouts. We can stomp on each other if you define aliases in Object class :) But this won't be a good idea, isnt? NBExternalType subclasses defining coercions between ST oops and concrete C type, they are not for defining aliases. > > 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: Monday, October 04, 2010 7:36 AM > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Re: [Pharo-project] Pointer types > > On 4 October 2010 06:15, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu> wrote: >> Sig, >> >> You mentioned something that might be useful, depending on where it lives. Â Our ability to use underscores now leaves me thinking I really should rework some things that suffered mightily: there are some external things that are named assuming underscores, and in mixed case, they turn into an unreadable mess. Â Along with this, I have a large number of FFI calls that take double pointers, and I have for some time been demoralized into (or stupid enough to<g>) expressing them as void pointers to allow me to pass byte arrays into them. >> >> Is there a way that I can get FFI to recognize DOUBLEArray (which uses a ByteArray to hold its data) as something that should be acceptable for a double* call? Â If not FFI, how does NB handle it? >> > > In NB, there is a type system, which implements C<->Smalltalk coercions. > The responsibility of type coercions taken by a subclasses of NBExternalType, > so NB callout code generator actually knows nothing about types and > how to coerce them. > > To create own custom type, you need to subclass from NBExternalType > and override methods which responsible for coercions. > There you can define any kind of operations , what needs to be done in > order to push value on stack, or > convert it to some smalltalk object. > > Then, in your DoubleArray class, simply implement a message on a class side: > > asNBExternalType: gen > > Â Â Â Â ^ MyDoubleArrayExternalType new > > > And then, in FFI callouts you can use a class name directly: > > DoubleArray foo (DoubleArray arr, DoubleArray * arrPtr) > > etc. > > Or, if you want make double* type to use it as a DoubleArray, then you > can add an alias: > > MyClass>>externalTypeAlias: aTypeName > Â aTypeName = 'double*' ifTrue: [ ^ #DoubleArray ]. > Â ^ nil > > Then, any method which contains an FFI callout in MyClass, > will use that alias. So, you can write callout as: > > double* foo (double *arr, double ** arrPtrPtr) > > but it will be understood as: > > DoubleArray foo (DoubleArray arr, DoubleArray * arrPtr) > > > About handling pointers.. well for smalltalk there is no pointers, just objects. > So, in NB NBExternalType keeps two things: > Â - a value type > Â - a pointer arity > > > So, for example, when you specifying type, like: > char *** > > a value type will be char > and pointer arity will be 3. > > It is up to NBExternalType subclass how to push values whose pointer arity > 0. > By default, if pointerArity > 0, then it is treated as a pointer, > which can be either: - nil, ByteArray, or NBExternalAddress > > >> Bill >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > > > -- > 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 > -- Best regards, Igor Stasenko AKA sig.

Oct. 7, 2010

Re: [Pharo-project] bad bracket autocompletion in Pharo Core 1.2

by Guillermo Polito

Yes, the issue can be reduced to: open parenthesis (or brackets), then something else (anywhere in the editor). 2010/10/6 Mariano Martinez Peck <marianopeck(a)gmail.com> > I detected a similar problem: > > once you type an opening parenthesis, and then something else, it adds a > new one at the END of the code > > check http://code.google.com/p/pharo/issues/detail?id=2939 > > 2010/10/6 Guillermo Polito <guillermopolito(a)gmail.com> > >> http://code.google.com/p/pharo/issues/detail?id=3069 >> >> if you type: >> >> [] -> []] >> >> () -> ()) >> >> {} -> {}} >> >> >> >> Bye! >> >> _______________________________________________ >> 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 >

Oct. 7, 2010

[Pharo-project] Morphic and the Player class in Pharo

by Robert Hawley

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).

Oct. 7, 2010

Re: [Pharo-project] FFI with 15+ args and Smallapack in Pharo

by Schwab,Wilhelm K

Nicolas, Did I not get any help? Sadly, there was so much bickering that it was hard to tell. I think yours was the reply that I had in mind to revisit. What I will do now, absent unforeseen time pressure, is put the offending calls on hold until 1.2 and then add them to the package. Another one that I don't think I've mentioned here is color mapping to create pseudo colored images. That will need some C support to run at decent speed, at least for what I have in mind. Thanks!! Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Nicolas Cellier [nicolas.cellier.aka.nice(a)gmail.com] Sent: Wednesday, October 06, 2010 6:56 PM To: Pharo Development Subject: [Pharo-project] FFI with 15+ args and Smallapack in Pharo 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 _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 6, 2010

Re: [Pharo-project] MicroSqueak [was System Tracer]

by Eliot Miranda

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. 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. On Wed, Oct 6, 2010 at 3:03 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>wrote: > > 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 > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 6, 2010