December 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] [Moose-dev] Re: for mondrian designers

by StÃ©phane Ducasse

why don't you read the pharo list. I mentioned that I extracted the packages from Sophie and published them in PharoTaskForces. Stef On Dec 4, 2009, at 2:20 PM, Alexandre Bergel wrote: > Hi! > > I just give a try to load Cairo. > First, I went to http://www.squeaksource.com/Rome.html and downloaded what is suggested. > Then I went to http://www.cairographics.org and downloaded cairo, and used my unix skills to compile it properly. Some of the Rome demo works, but most of them need the RomePlugin is apparently needed. Unfortunately, I cannot find this plugin. > > Cheers, > Alexandre > > > On 4 Dec 2009, at 07:18, Tudor Girba wrote: > >> Hi, >> >>>>> So consider to have a look at the cairo package in PharoTaskForces because it will not come to you alone :) >> >> What exactly should I load from PharoTaskForces to get Cairo? >> >> I see several Rome related packages, but which ones are needed? Is there a load script? >> >> Cheers, >> Doru >> >> -- >> www.tudorgirba.com >> >> "There are no old things, there are only old ways of looking at them." >> >> >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Dec. 4, 2009

Re: [Pharo-project] Email notifications from issue tracker?

by Johan Fabry

Agree with Simon, I saw on the new 'how to submit a bug' webpage that after the bug submission the user is supposed to manually send the same info to the mailing list. It would be better to automate this, no? On 04 Dec 2009, at 09:54, Simon Denier wrote: > Hi > > I wonder why activity from the issue tracker do not get posted on the > mailing list? Is it a conscious decision? Because it seems like there > are two places for discussion right now: the mailing list and the > issues comments. > > -- > Simon > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Johan Fabry jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Dec. 4, 2009

Re: [Pharo-project] code coverage?

by Alexandre Bergel

>>> does your spy support spy itself or detect that and does not spy >>> dangerous >>> guys. >> >> So far no. >> I would love to have Reflectivity for this... >> > > Yes, will be available, uhm, at some point... Let us know, I would love to give a try Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 4, 2009

[Pharo-project] Trouble with using Rome

by Alexandre Bergel

Hi! There is the file RomePlugin.bundle in one folder of the 4.2.1 VM. When I execute "RomeDemo drawCar", I have a rollback saying a primitive has failed. The guilty call is: -=-=-=-=-=-=-=-=-=-=-=-= RomePluginCanvas>>primOpen <primitive: 'primitiveOpen' module: 'RomePlugin'> ^self primitiveFailed -=-=-=-=-=-=-=-=-=-=-=-= The following is displayed in the xterm: Squeak-Rome: canvas oop invalid! Anyone can help? Cheer, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 4, 2009

Re: [Pharo-project] [Moose-dev] Re: for mondrian designers

by Alexandre Bergel

Hi! I just give a try to load Cairo. First, I went to http://www.squeaksource.com/Rome.html and downloaded what is suggested. Then I went to http://www.cairographics.org and downloaded cairo, and used my unix skills to compile it properly. Some of the Rome demo works, but most of them need the RomePlugin is apparently needed. Unfortunately, I cannot find this plugin. Cheers, Alexandre On 4 Dec 2009, at 07:18, Tudor Girba wrote: > Hi, > >>>> So consider to have a look at the cairo package in >>>> PharoTaskForces because it will not come to you alone :) > > What exactly should I load from PharoTaskForces to get Cairo? > > I see several Rome related packages, but which ones are needed? Is > there a load script? > > Cheers, > Doru > > -- > www.tudorgirba.com > > "There are no old things, there are only old ways of looking at them." > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 4, 2009

Re: [Pharo-project] code coverage?

by Marcus Denker

On Dec 3, 2009, at 11:18 PM, Alexandre Bergel wrote: >> does your spy support spy itself or detect that and does not spy >> dangerous >> guys. > > So far no. > I would love to have Reflectivity for this... > Yes, will be available, uhm, at some point... Marcus

Dec. 4, 2009

[Pharo-project] Email notifications from issue tracker?

by Simon Denier

Hi I wonder why activity from the issue tracker do not get posted on the mailing list? Is it a conscious decision? Because it seems like there are two places for discussion right now: the mailing list and the issues comments. -- Simon

Dec. 4, 2009

[Pharo-project] Fwd: [squeak-dev] macintosh cocoa 32/64bit & 64/64bit VM goes BETA

by StÃ©phane Ducasse

> john needs beta testers....Do not forget > I know that we are all terribly busy. > > > Begin forwarded message: > >> From: John M McIntosh <johnmci(a)smalltalkconsulting.com> >> Date: December 2, 2009 11:57:43 PM GMT+01:00 >> To: Squeak Virtual Machine Development Discussion <vm-dev(a)lists.squeakfoundation.org>, The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org>, "Pharo-project(a)lists.gforge.inria.fr Development" <pharo-project(a)lists.gforge.inria.fr> >> Subject: [squeak-dev] macintosh cocoa 32/64bit & 64/64bit VM goes BETA >> Reply-To: johnmci(a)smalltalkconsulting.com, The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> >> >> Ok, it's time for the community to do some testing. >> >> ESUG provided me with some funding to take the existing iPhone VM source and extend that to >> build a new hosting platform using Cocoa on the macintosh and to enable the VM to run in 32 or 64 bit >> mode and work with a 32 or 64bit image. >> >> I have placed two Alpha test VM s in the experimental folder sub-folder COCOA >> found in the usual places via >> >> http://smalltalkconsulting.com/squeak.html >> >> There are two VM's >> >> (a) a 32/64 bit VM that runs 32bit squeak images in 32bit (powerpc, intel) or 64bit (intel) mode. >> (b) a 64/64 bit VM that runs 64bit squeak images in 64bit (intel). >> >> >> The VM currently runs on 10.5.x and 10.6.x Support for 10.4.x might happen, we will see. >> >> Until I sort out the re-integration of the source code into the squeakvm.org SVN tree you will >> find the source at isqueak.org >> >> Issues, Oh lots. It's a fairly high mountain of material that needs to be tested. >> >> Things that should work. >> >> (a) access to files and directories UTF8 support only. >> (b) Full screen support >> (c) Sockets >> (d) Basic Sound (better than in the 3.x/4.x VMs) >> (e) jpegplugin2 >> (f) cut/copy/paste of text data (from/to) squeak and respect UTF8 chars >> (g) drag and drop of files into squeak >> >> Right now it does not: >> >> (a) Support a internet browser as a browser plugin. >> (b) The 64bit VM has no plugins at the moment. >> (b2) I've not included any plugins with the 32/64bit VM. >> Existing plugins might work if the VM is running as "Open in 32bit mode" >> someone can confirm that. >> >> (c) No macintosh host menus, or serial port support >> (d) No Areithfa Ffenestri multiple-window support >> (e) No 1, 2, 4, 8, 16 bit appearance support. >> >> Things I know about. >> (a) double clicking *.images when the 5.x VM is running sometimes does not open a new VM. >> (b) tossing a 32 image at the 64/64 bit VM or a 64 image at the 32/64 VM doesn't give visual feedback that it won't open the image. >> (c) Full screen grabs all the screens, yes that will change >> >> Thoughts on internal plugins. Hint we should have TEST cases so we can confirm if all this stuff works. >> It would be extremely helpful if someone wanted to work on that. No doubt someone *could* run all the >> current tests for a 32bit image and see what breaks. However you'll need to explain where and what, versus >> Oh it just crashed... >> >> ADPCMCodecPlugin, untested. >> Squeak3D, Likely busted due to use of (int) data types in 64bit mode. >> B2DPlugin, untested. >> BitBltPlugin, untested. >> BMPReadWriterPlugin, untested. >> ZipPlugin, untested. >> DSAPrims, untested. >> SqueakFFIPrims, untested. >> FFTPlugin, untested. >> FloatArrayPlugin, untested. >> GeniePlugin, untested. >> HostWindowPlugin, No support yet >> JPEGReaderPlugin, untested. >> Klatt, untested. >> LargeIntegers, untested. >> Matrix2x3Plugin, untested. >> MiscPrimitivePlugin, untested. >> ObjectiveCPlugin, untested. >> RePlugin, Likely busted due to use of (int) data types in 64bit mode. >> SecurityPlugin, untested. >> SoundCodecPrims, Likely busted due to use of (int) data types in 64bit mode. >> SoundGenerationPlugin, Likely busted due to use of (int) data types in 64bit mode. >> StarSqueakPlugin, untested. >> SurfacePlugin, untested. >> UUIDPlugin untested. >> >> Possibly Large Integers may have a problem in 64bit image mode, but we have to have some >> discussion if the (unsigned int *) used by one routine is on purpose or an oversight. >> >> 64 bit images. >> >> We need to built a 64bit Closure image. **** I've no time to do that. *** >> >> David T Lewis provided a somewhat current Squeak.image which you'll find on the ftp site. >> >> If you build a 64bit image you need to do that on a PowerPC, or make a copy of your VM on macIntel >> and flip the "Open in 32-bit mode" and the "Open in Rosetta" to on. You will only see the "Open in 32bit mode" if it's a 64bit VM, >> and the "Open in Rosetta on os-x for 10.5 or 10.6 (if you installed it) >> Follow the obvious instructions. >> >> No doubt some is required to take the code and build a MC change set for Pharo or Squeak Thrunk use so that >> anyone can convert an existing image. >> >> Also see >> http://bugs.squeak.org/view.php?id=5239 >> http://bugs.squeak.org/view.php?id=5240 >> >> Building your own VM? >> >> Hopefully someone will attempt this so I can see if I checked in all the changes. >> >> 32bit image VM pick SqueakPureObjc and set >> #define SQ_VI_BYTES_PER_WORD 4 >> for a >> 64bit image reading VM pick SqueakPureObjc64*64 and set >> #define SQ_VI_BYTES_PER_WORD 8 >> in the required places. >> >> PS You'll find that building a 32/64 VM using GNU's tool chain will give you lousy performance >> when running as a 64bit VM, more on this later. >> >> ---------------------------------------------- >> Oh and lastly I'm looking for some paid work (smalltalk or objective-c (mac/iPhone) If anyone >> requires a Smalltalk consultant, or an iPhone app built, please email me. >> >> -- >> =========================================================================== >> John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882 >> Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com >> =========================================================================== >> >> >> >> >> > > > >

Dec. 4, 2009

Re: [Pharo-project] newinspector?

by Adrian Lienhard

Great, thanks! Adrian On Dec 4, 2009, at 13:07 , Frederic Pluquet wrote: > Hello Adrian, > > I deleted the Elements child in CompiledMethod (it had no sense in > CompiledMethod). > I added also added a literals child to inspect CompiledMethod literals > easily. > > FrÃ©d > ---- > FrÃ©dÃ©ric Pluquet > UniversitÃ© Libre de Bruxelles (ULB) > Assistant > http://www.ulb.ac.be/di/fpluquet > > > On Thu, Dec 3, 2009 at 9:44 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: > >> Hi Frederic, >> >> I just run into a problem: clicking on Elements of a NewInspector >> on a >> CompiledMethod gives an error: 'CompiledMethods may only be created >> with >> newMethod:header:' >> >> Shall I create an issue in the Pharo tracker? >> >> Adrian >> >> >> On Nov 26, 2009, at 19:40 , Adrian Lienhard wrote: >> >> Just yesterday, I asked Frederic to remove the class and method >>> entries that add a lot of the noise and are most often not needed. >>> He >>> committed a new version with these changes. >>> >>> But from Stef's analysis it seems there is a bit more needed to make >>> this inspector fly... And a really good inspector is key! >>> >>> Another item to add to Stef's list: what is the point of the item >>> "Keys"? I can see the keys of the dictionary already by opening >>> "Elements". So this seems superfluous. >>> >>> I wonder why inspecting a dictionary could not be reduced to the >>> information that is actually of interest, namely the keys and their >>> values. So when opening a dictionary, the subtree would directly >>> display the keys in the left pane (no array, tally, Keys, Elements). >>> If a key is selected, its value is printed in the right pane. >>> Expanding a key would dive into its associated value. Actually, I >>> think what I described here is more or less the behavior of the old >>> explore tool. >>> >>> Cheers, >>> Adrian >>> >>> >>> On Nov 26, 2009, at 18:39 , StÃ©phane Ducasse wrote: >>> >>> Hi guys >>>> >>>> again I did a demo of smalltalk and the newInspecotr got in my way. >>>> I tried to analyze what did not work: >>>> - apparently the refresh does not work. Does change in >>>> instance >>>> variables get refreshed in the inspector? >>>> >>>> I try to understand what get in my way in general. >>>> - when an object has few instance variable I think that it >>>> is lost >>>> in the sea of trees. >>>> >>>> - I think that the |> class is not useful at the top level. >>>> May be just having Class: and the class Name is enough no >>>> need for >>>> the |> >>>> May be the Class : ByteString should appear after the >>>> Elements: >>>> >>>> - the |> methods to be useful should be sorted by category >>>> >>>> in the screenshot >>>> Why do I see the instance variable of the dictionary >>>> (array and >>>> tally) I find that confusing? >>>> Because I get elements and at the same time the instance >>>> variables. >>>> >>>> I do not understand why some lines are bold and other blue >>>> >>>> When we click on connectInfo I see on the right pane >>>> - size : 5 >>>> [#host] : a SocketAddress (size: 24) >>>> [#loginMethod] : #zork >>>> [#password] : nil >>>> [#port] : 110 >>>> [#user] : 'stephane.ducasse' >>>> But I cannot modify anything. >>>> >>>> What is the point to have Elements expanded in the left >>>> pane when >>>> I >>>> get the contents by clicking on the instance >>>> variable and getting the contents on the right. >>>> >>>> Then Keys should probably close to Elements. >>>> >>>> I do not see the point to have |> for individual method >>>> I do not understand why we see Elements and ByteCode >>>> I get a DNU when I click on Elements of a method BTW >>>> >>>> >>>> <Screen shot 2009-11-26 at 6.14.31 >>>> PM.png>_______________________________________________ >>>> 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 >>> >> >>

Dec. 4, 2009

Re: [Pharo-project] How do I know which issues are resolved in each new release?

by Marcus Denker

Hello, Yes, we should improve information on what changed.... I would want to have a changelog for any image that is downloaded. And we should use the Blog. And Twitter. And. And. We will do all that, but not today :-) Marcus On Dec 1, 2009, at 3:19 PM, Tim Mackinnon wrote: > So can can I see this somewhere? I was expecting on the download page there would be a link to show me what changes have been fixed in that release. ( even a list so that I can filter on 9.11.4 - and then see that #11504,11523... is included etc. would be fine). > > Maybe in the future there might be some way to do something like the Trac guys do - where they have the convention that their SVN commit comments (I guess this could be MCZ comments or naming convention) include the ticket id number of the bug/feature they are fixing - they can then generate a list of whats in a build - and when you do a release, whats in the release. e.g. look at the following page on their website: http://trac.edgewall.org/wiki/TracL10N (press the edit button and see how they are querying out the outstanding tickets for a release). Is this what Mason and the things mentioned do? > > The best system I have seen running was Trac with Hudson - however all these things are doable in any system (the ones mentioned here sound interesting). > > I would just like to see something concrete so I can try and help in some way to make sure that V1.0 is stable and as bug free as possible. > > > Tim > > On 1 Dec 2009, at 12:35, StÃ©phane Ducasse wrote: > >> this is what we do also. >> >> On Dec 1, 2009, at 2:03 AM, Dale Henrichs wrote: >> >>> In the google issues list, one can add a column called "Fixed" and a version can be supplied for the value of that field (like Version or Milestone) when the bug is fixed ... I think this is what Tim is getting at. I've just done this for Metacello, since I think it is a good idea:) >>> >>> Dale >>> ----- "Tim Mackinnon" <tamackinnon(a)gmail.com> wrote: >>> >>> | Hi guys - I noticed there was a new 9.11.4 release since buenos aires >>> | - and I got to wondering what issues have been resolved in it (as I am >>> | trying to follow Pharo by example - I am trying to test out features >>> | to see if they work as I progress through the material). >>> | >>> | Anyway - is there a list of issues fixed marked against each new >>> | version? I can see the list at: >>> | http://code.google.com/p/pharo/issues/list# - but it doesn't list any >>> | build numbers - just milestone 1.1? >>> | >>> | Tim >>> | _______________________________________________ >>> | 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

Dec. 4, 2009