January 2013 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] about Loom profiler

by Alexandre Bergel

Hi! Sorry for the late reply. > how Loom compares with the fixes that andreas added to the default profiler. I am not sure about Andreas' fixes. Loom tells you for each thread running in the VM the amount of CPU it consumes. Some screenshots should be self explaining: http://objectprofile.com/loom-screenshots.html > I do not know if the code is in squeak because this code was licensed under GPL. Loom is MIT. > But I would like to know if your profiler takes into account the problems solved by andreas. Any ref about this? > I did not see an announce of Loom (by the way Loom is the name of large oo memory developed by the original smalltalk team > a while ago). > > http://objectprofile.com/loom-download.html > > I'm know that some people got problem with our profiler and I would like to see how we > can improve it. We haven't announced Loom because the Pharo version is not yet ready. Although usable, it has a very poor graphical user interface. The first goal is to have Loom replace the standard process browser. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Jan. 23, 2013

Re: [Pharo-project] NativeBoost and unions

by Igor Stasenko

On 23 January 2013 01:16, Camillo Bruni <camillobruni(a)gmail.com> wrote: > yes please! > Yes. The only question is where to go: - on git - on smalltalkhub - on ss3 ? > On 2013-01-22, at 19:10, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > >> as all the core packages for pharo (and NB is one of them), it should be in smalltalkhub :) >> >> On Jan 22, 2013, at 5:29 PM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >>> >>> On Jan 22, 2013, at 5:26 PM, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> wrote: >>> >>>> Hi Igor, >>>> >>>> as usual after squeaksource restart, i lost my commit rights on the NativeBoost repository... >>>> >>> >>> Could NativeBoost move away from SqueakSource? SqueakSource is not stable. >>> >>>> This time I have a small refactoring in the NBExternalStruct/NBExternalStructFields to enable union support. >>>> >>>> Besides that, c unions, I have implemented a first prototype, and now my question for you is: Should I add it in nativeboost (its rightful place in my opinion), >>>> or should I keep it only as support code for my TalkFFI project(in TalkFFI-runtime)? What do you think? >>>> >>>> Cheers, >>>> Ciprian >>>> -- >>>> Dr. Ciprian TEODOROV >>>> IngÃ©nieur DÃ©veloppement CAO >>>> >>>> tÃ©l : 06 08 54 73 48 >>>> mail : ciprian.teodorov(a)gmail.com >>>> www.teodorov.ro >>> >> > > -- Best regards, Igor Stasenko.

Jan. 23, 2013

Re: [Pharo-project] NativeBoost and unions

by Igor Stasenko

On 21 January 2013 19:55, Ciprian Teodorov <ciprian.teodorov(a)gmail.com> wrote: > Hi Igor, > > as usual after squeaksource restart, i lost my commit rights on the > NativeBoost repository... added again. > > This time I have a small refactoring in the > NBExternalStruct/NBExternalStructFields to enable union support. > > Besides that, c unions, I have implemented a first prototype, and now my > question for you is: Should I add it in nativeboost (its rightful place in > my opinion), > or should I keep it only as support code for my TalkFFI project(in > TalkFFI-runtime)? What do you think? > I think unions will be good addition to NBExternalStruct :) > Cheers, > Ciprian > -- > Dr. Ciprian TEODOROV > IngÃ©nieur DÃ©veloppement CAO > > tÃ©l : 06 08 54 73 48 > mail : ciprian.teodorov(a)gmail.com > www.teodorov.ro -- Best regards, Igor Stasenko.

Jan. 23, 2013

Re: [Pharo-project] Athens replacement for ImageReadWriter?

by Igor Stasenko

On 23 January 2013 14:34, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > On Jan 23, 2013, at 2:23 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > >> On 23 January 2013 12:58, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >>> Hi Fernando, >>> >>> I don't want a Form... quitte the opposite! :) >>> What I want is to have something equivalent to athens to what now is covered >>> in morphic with ImageReadWriter. >>> >>> Or, better explained, I want an AthensImageReadWriter who answers me a >>> surface (or something that I can draw with an athens canvas) with the image >>> from a file :) >>> >> You know that you can convert between forms and athens surface? > > I know, but I want to get rid off morphic :) > >> Forms is actually not that bad, they simply contain bits. > > I know, but then we will keep them even if we remove morphic? > Why not? You will still need something which represents the bitmap bits, which you can directly manipulate (if you want to). >> The bit format information is a bit obscure (comparing to OpenGL, for instance), >> but its enough. >> So, i suggest you to use form and ImageReadWriter. > > ok, I will use it. > -- Best regards, Igor Stasenko.

Jan. 23, 2013

Re: [Pharo-project] Athens replacement for ImageReadWriter?

by Esteban Lorenzano

On Jan 23, 2013, at 2:23 PM, Igor Stasenko <siguctua(a)gmail.com> wrote: > On 23 January 2013 12:58, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: >> Hi Fernando, >> >> I don't want a Form... quitte the opposite! :) >> What I want is to have something equivalent to athens to what now is covered >> in morphic with ImageReadWriter. >> >> Or, better explained, I want an AthensImageReadWriter who answers me a >> surface (or something that I can draw with an athens canvas) with the image >> from a file :) >> > You know that you can convert between forms and athens surface? I know, but I want to get rid off morphic :) > Forms is actually not that bad, they simply contain bits. I know, but then we will keep them even if we remove morphic? > The bit format information is a bit obscure (comparing to OpenGL, for instance), > but its enough. > So, i suggest you to use form and ImageReadWriter. ok, I will use it. > >> Esteban >> >> On Jan 23, 2013, at 12:06 PM, Fernando Olivero <fernando.olivero(a)usi.ch> >> wrote: >> >> What you can with Athens and the Cairo backend is: >> >> 1) create a surface in memory >> 2) draw to the surface >> 3) export that surface to a png >> 4) import that png into a form >> >> >> The main point is step 3, cairo can export any surface to a png. Then within >> Pharo, any form can be created from a png. >> > But that is private to cairo library. > >> Also, if you interested in drawing from Athens into a form directly, look at >> the AthensDemoExamples, and Igor's magic trick of matching the bits of the >> surface (step 1), directly to the bits of an "external" form. to avoid steps >> 3 and 4. He used the surface plugin for that. >> > >> Hope i answered all your questions, though not sure because i've never used >> ImageReadWriter. >> >> Fernando >> >> >> >> > > > -- > Best regards, > Igor Stasenko. >

Jan. 23, 2013

Re: [Pharo-project] NativeBoost question

by Igor Stasenko

On 23 January 2013 12:23, GÃ¶ran Krampe <goran(a)krampe.se> wrote: > Hey! > > I have a struct something like this: > > struct { > const char * attribute; > int size; > int datatype; > } > > > ...and I am trying something like this to match an NBExternalStructure: > > fieldsDesc > ^#( > String attribute; > int size; > int datatype; > ) > > ...or even this: > > ^#( > NBExternalString attribute; > int size; > int datatype; > ) > > All these give me some DNU (nil) for #asAJOperand when emitting code. > > The only one that works is when I use NBExternalAddress as can be seen in > action in NBTestStructure2. Is this by design or am I simply an early > adopter and support for String etc isn't there yet? > I think it is not working because NBExternalString is quite special when it about handling the values. For structure, i think, you'd better use 'char *' , or 'void*'.. and then to read string you can do: struct attribute readString > regards, GÃ¶ran -- Best regards, Igor Stasenko.

Jan. 23, 2013

Re: [Pharo-project] Athens replacement for ImageReadWriter?

by Igor Stasenko

On 23 January 2013 12:58, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi Fernando, > > I don't want a Form... quitte the opposite! :) > What I want is to have something equivalent to athens to what now is covered > in morphic with ImageReadWriter. > > Or, better explained, I want an AthensImageReadWriter who answers me a > surface (or something that I can draw with an athens canvas) with the image > from a file :) > You know that you can convert between forms and athens surface? Forms is actually not that bad, they simply contain bits. The bit format information is a bit obscure (comparing to OpenGL, for instance), but its enough. So, i suggest you to use form and ImageReadWriter. > Esteban > > On Jan 23, 2013, at 12:06 PM, Fernando Olivero <fernando.olivero(a)usi.ch> > wrote: > > What you can with Athens and the Cairo backend is: > > 1) create a surface in memory > 2) draw to the surface > 3) export that surface to a png > 4) import that png into a form > > > The main point is step 3, cairo can export any surface to a png. Then within > Pharo, any form can be created from a png. > But that is private to cairo library. > Also, if you interested in drawing from Athens into a form directly, look at > the AthensDemoExamples, and Igor's magic trick of matching the bits of the > surface (step 1), directly to the bits of an "external" form. to avoid steps > 3 and 4. He used the surface plugin for that. > > Hope i answered all your questions, though not sure because i've never used > ImageReadWriter. > > Fernando > > > > -- Best regards, Igor Stasenko.

Jan. 23, 2013

Re: [Pharo-project] OrderedCollections and File I/O

by Edgar J. De Cleene

On 1/23/13 8:47 AM, "Mariano Martinez Peck" <marianopeck(a)gmail.com> wrote: > > On Wed, Jan 23, 2013 at 6:39 AM, Edgar J. De Cleene <edgardec2005(a)gmail.com> > wrote: >> >> >> >> On 1/23/13 6:25 AM, "Marcus Denker" <marcus.denker(a)inria.fr> wrote: >> >>> > Keep in mind that ReferenceStream is deprecated in 2.0 >>> > >>> > The nice thing about Fuel is: >>> > >>> > -> Very much faster >>> > -> output more compact >>> > -> you can store *any* kind of objects. >>> > Â Â Â Â Â Â (even the one you are sure you can't, like the Context (stack >>> > frame)) >>> > >>> > Marcus >> >> Yes , I know Fuel is a great advance, but he ask about simple thing. >> And also I said Pharo 1.4 and not Pharo 2.0. >> >> Thanks to Mariano and others , wish Fuel become Squeak citizen soon, for >> Cuis guess should wait longer. >> >> >> Edgar see new release:Â http://forum.world.st/ANN-Fuel-1-8-1-td4661609.html >> Supported and tested images:Â >> Pharo 1.1.1, 1.1.2, 1.2, 1.3, 1.4, 2.0Â >> Squeak 4.1, 4.2, 4.3, 4.4Â >> Â >>> Edgar >>> > > Mariano, yo se eso. > Pareciera que por tratar de ayudar a un nuevo con dos lineas de codigo estoy > desconociendo tu trabajo y el de todos los demas que estan trabajando con > Fuel. > No hay una unica receta, mis amigos de Pharo. > > Edgar

Jan. 23, 2013

Re: [Pharo-project] pharotaskforces broken on squeaksource

by StÃ©phane Ducasse

No idea but we should fix it. Stef > Hi, > > It seems that the http://www.squeaksource.com/PharoTaskForces repository is broken. > > When I try to connect to it via Monticello, I get a "SubscriptOutOfBounds: 0". The problem seems to be that the repository somehow has a file called '.mcz' (which is obviously wrong): > > (MCHttpRepository > location: 'http://www.squeaksource.com/PharoTaskForces' > user: '' > password: '') readableFileNames select: [:each | each beginsWith: '.'] > > > Anyone know why this happened? Or how to fix this? > > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "It's not how it is, it is how we see it." > > > > >

Jan. 23, 2013

Re: [Pharo-project] Athens replacement for ImageReadWriter?

by Esteban Lorenzano

Hi Fernando, I don't want a Form... quitte the opposite! :) What I want is to have something equivalent to athens to what now is covered in morphic with ImageReadWriter. Or, better explained, I want an AthensImageReadWriter who answers me a surface (or something that I can draw with an athens canvas) with the image from a file :) Esteban On Jan 23, 2013, at 12:06 PM, Fernando Olivero <fernando.olivero(a)usi.ch> wrote: > What you can with Athens and the Cairo backend is: > > 1) create a surface in memory > 2) draw to the surface > 3) export that surface to a png > 4) import that png into a form > > > The main point is step 3, cairo can export any surface to a png. Then within Pharo, any form can be created from a png. > > Also, if you interested in drawing from Athens into a form directly, look at the AthensDemoExamples, and Igor's magic trick of matching the bits of the surface (step 1), directly to the bits of an "external" form. to avoid steps 3 and 4. He used the surface plugin for that. > > Hope i answered all your questions, though not sure because i've never used ImageReadWriter. > > Fernando > > > > > On Wed, Jan 23, 2013 at 6:38 AM, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > I have same question :)) > > 2013/1/23 Esteban Lorenzano <estebanlm(a)gmail.com<mailto:estebanlm@gmail.com>> > Hi, > > So, ImageReadWriter currently reads image files and retrieve Form objects, who can be displayed in world... > anybody knows (cough, cough, Igor) what would be the Athens replacement for that? > > thanks, > Esteban > > > >

Jan. 23, 2013