- Pharo-dev - lists.pharo.org

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

by Tudor Girba

Fuel works in 1.4 just fine. Doru On Wednesday, January 23, 2013, Edgar J. De Cleene wrote: > > > > On 1/23/13 6:25 AM, "Marcus Denker" <marcus.denker(a)inria.fr <javascript:;>> > 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 > > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 23, 2013

[Pharo-project] NativeBoost question

by GÃ¶ran Krampe

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? regards, GÃ¶ran

Jan. 23, 2013

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

by Camillo Bruni

This is exactly what I would expect as a headless test case for Athens ;) On 2013-01-23, at 12:06, 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(a)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

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

by Fernando Olivero

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(a)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

Re: [Pharo-project] NativeBoost and unions

by Ciprian Teodorov

On Jan 23, 2013 1:16 AM, "Camillo Bruni" <camillobruni(a)gmail.com> wrote: > > yes please! > > 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 :) +1 > > > > 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 > >> > > > >

Jan. 23, 2013

Re: [Pharo-project] DocTest

by Sven Van Caekenberghe

On 23 Jan 2013, at 11:34, Tudor Girba <tudor(a)tudorgirba.com> wrote: > FYI, we are already using Phexample in Moose since several years, and it just works out of the box next to Sunit. That is good to know. Moose is a really important project for Pharo. It feels good to know that such a big code base is pushing forward like that. BTW, is work already being done bring Moose to Pharo 2.0 ? > Doru > > On Wednesday, January 23, 2013, Sven Van Caekenberghe wrote: > Yes we #should ;-) > > It is beautiful. > > On 23 Jan 2013, at 11:04, Camillo Bruni <camillobruni(a)gmail.com> wrote: > > > check the project page for all examples and explanations: > > > > http://smalltalkthoughts.blogspot.ch/2009/11/phexample-because-examples-exp… > > http://www.iam.unibe.ch/~akuhn/blog/2009/shoulda-use-this-in-pharo > > > > to me this feels more like Smalltalk and less like Java ;) > > > > On 2013-01-23, at 08:47, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: > >> Who should assert then? > >> From a certain POV, it does not seem that awfully unlogical to > >> delegate this responsability to a TestCase. > >> A TestCase is here to assert some rule. > >> > >> Nicolas > >> > >> 2013/1/23 Camillo Bruni <camillobruni(a)gmail.com>: > >>> for that we already have a fully working Phexample: > >>> > >>> http://www.squeaksource.com/phexample.html > >>> > >>> which I will push in 3.0, cause I never really liked #assert: and friends being > >>> sent to self. Furthermore we could finally build up decent messages! > >>> > >>> On 2013-01-22, at 18:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > >>> > >>>> it would be nice to introduce the same syntax than Sunit > >>>> > >>>> exp assert: exp2 > >>>> > >>>> [ exp ] shouldraise: > >>>> > >>>> Stef > >>>> > >>>> > >>>> On Jan 21, 2013, at 4:41 AM, Benjamin wrote: > >>>> > >>>>> Hi guys, > >>>>> > >>>>> I am attending a python lecture and discovered DocTest[1], and I was wondering if such a tool exists for Pharo ? :) > >>>>> > >>>>> > >>>>> Ben > >>>>> > >>>>> [1]http://docs.python.org/2/library/doctest.html > >>>>> > >>>>> > >>>> > >>>> > >>> > >>> > >> > > > > > > > > > -- > www.tudorgirba.com > > "Every thing has its own flow" >

Jan. 23, 2013

Re: [Pharo-project] DocTest

by Tudor Girba

FYI, we are already using Phexample in Moose since several years, and it just works out of the box next to Sunit. Doru On Wednesday, January 23, 2013, Sven Van Caekenberghe wrote: > Yes we #should ;-) > > It is beautiful. > > On 23 Jan 2013, at 11:04, Camillo Bruni <camillobruni(a)gmail.com<javascript:;>> > wrote: > > > check the project page for all examples and explanations: > > > > > http://smalltalkthoughts.blogspot.ch/2009/11/phexample-because-examples-exp… > > http://www.iam.unibe.ch/~akuhn/blog/2009/shoulda-use-this-in-pharo > > > > to me this feels more like Smalltalk and less like Java ;) > > > > On 2013-01-23, at 08:47, Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com <javascript:;>> wrote: > >> Who should assert then? > >> From a certain POV, it does not seem that awfully unlogical to > >> delegate this responsability to a TestCase. > >> A TestCase is here to assert some rule. > >> > >> Nicolas > >> > >> 2013/1/23 Camillo Bruni <camillobruni(a)gmail.com <javascript:;>>: > >>> for that we already have a fully working Phexample: > >>> > >>> http://www.squeaksource.com/phexample.html > >>> > >>> which I will push in 3.0, cause I never really liked #assert: and > friends being > >>> sent to self. Furthermore we could finally build up decent messages! > >>> > >>> On 2013-01-22, at 18:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr<javascript:;>> > wrote: > >>> > >>>> it would be nice to introduce the same syntax than Sunit > >>>> > >>>> exp assert: exp2 > >>>> > >>>> [ exp ] shouldraise: > >>>> > >>>> Stef > >>>> > >>>> > >>>> On Jan 21, 2013, at 4:41 AM, Benjamin wrote: > >>>> > >>>>> Hi guys, > >>>>> > >>>>> I am attending a python lecture and discovered DocTest[1], and I was > wondering if such a tool exists for Pharo ? :) > >>>>> > >>>>> > >>>>> Ben > >>>>> > >>>>> [1]http://docs.python.org/2/library/doctest.html > >>>>> > >>>>> > >>>> > >>>> > >>> > >>> > >> > > > > > > > -- www.tudorgirba.com "Every thing has its own flow"

Jan. 23, 2013

Re: [Pharo-project] [Pharo-users] Pharo 2.0 - System Error Handling Failed

by Marcus Denker

On Jan 23, 2013, at 10:52 AM, Sven Van Caekenberghe <sven(a)stfx.eu> wrote: > I really think that for the process of polishing 2.0 from beta to release we need a new label for issues. > > Bugs like the one below are really important, they might be silly or easy to fix, but they leave a bad impression. We want as many people as possible to help, but UX failures like this will scare away many users, most won't be as helpful as Andy to even report the issue. We as developers know that 2.0 is OK because we use it every day, but occasional users who just try 2.0 for the first time can't know that. > > So not HorribleErrorBlockingEverything but maybe HorribleUXQualityBugScaringAwayNormalPeople as label ? > :-) yes. Marcus

Jan. 23, 2013

Re: [Pharo-project] DocTest

by Sven Van Caekenberghe

Yes we #should ;-) It is beautiful. On 23 Jan 2013, at 11:04, Camillo Bruni <camillobruni(a)gmail.com> wrote: > check the project page for all examples and explanations: > > http://smalltalkthoughts.blogspot.ch/2009/11/phexample-because-examples-exp… > http://www.iam.unibe.ch/~akuhn/blog/2009/shoulda-use-this-in-pharo > > to me this feels more like Smalltalk and less like Java ;) > > On 2013-01-23, at 08:47, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> Who should assert then? >> From a certain POV, it does not seem that awfully unlogical to >> delegate this responsability to a TestCase. >> A TestCase is here to assert some rule. >> >> Nicolas >> >> 2013/1/23 Camillo Bruni <camillobruni(a)gmail.com>: >>> for that we already have a fully working Phexample: >>> >>> http://www.squeaksource.com/phexample.html >>> >>> which I will push in 3.0, cause I never really liked #assert: and friends being >>> sent to self. Furthermore we could finally build up decent messages! >>> >>> On 2013-01-22, at 18:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>> it would be nice to introduce the same syntax than Sunit >>>> >>>> exp assert: exp2 >>>> >>>> [ exp ] shouldraise: >>>> >>>> Stef >>>> >>>> >>>> On Jan 21, 2013, at 4:41 AM, Benjamin wrote: >>>> >>>>> Hi guys, >>>>> >>>>> I am attending a python lecture and discovered DocTest[1], and I was wondering if such a tool exists for Pharo ? :) >>>>> >>>>> >>>>> Ben >>>>> >>>>> [1]http://docs.python.org/2/library/doctest.html >>>>> >>>>> >>>> >>>> >>> >>> >> > >

Jan. 23, 2013

Re: [Pharo-project] DocTest

by Frank Shearar

Well, of course, JUnit feels that way because of SUnit, but sure. RSpec-like testing languages read much more easily than #assert:, in my not so humble opinion. frank On 23 January 2013 10:04, Camillo Bruni <camillobruni(a)gmail.com> wrote: > check the project page for all examples and explanations: > > http://smalltalkthoughts.blogspot.ch/2009/11/phexample-because-examples-exp… > http://www.iam.unibe.ch/~akuhn/blog/2009/shoulda-use-this-in-pharo > > to me this feels more like Smalltalk and less like Java ;) > > On 2013-01-23, at 08:47, Nicolas Cellier <nicolas.cellier.aka.nice(a)gmail.com> wrote: >> Who should assert then? >> From a certain POV, it does not seem that awfully unlogical to >> delegate this responsability to a TestCase. >> A TestCase is here to assert some rule. >> >> Nicolas >> >> 2013/1/23 Camillo Bruni <camillobruni(a)gmail.com>: >>> for that we already have a fully working Phexample: >>> >>> http://www.squeaksource.com/phexample.html >>> >>> which I will push in 3.0, cause I never really liked #assert: and friends being >>> sent to self. Furthermore we could finally build up decent messages! >>> >>> On 2013-01-22, at 18:24, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: >>> >>>> it would be nice to introduce the same syntax than Sunit >>>> >>>> exp assert: exp2 >>>> >>>> [ exp ] shouldraise: >>>> >>>> Stef >>>> >>>> >>>> On Jan 21, 2013, at 4:41 AM, Benjamin wrote: >>>> >>>>> Hi guys, >>>>> >>>>> I am attending a python lecture and discovered DocTest[1], and I was wondering if such a tool exists for Pharo ? :) >>>>> >>>>> >>>>> Ben >>>>> >>>>> [1]http://docs.python.org/2/library/doctest.html >>>>> >>>>> >>>> >>>> >>> >>> >> > >

Jan. 23, 2013