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

Re: [Pharo-project] Bug reports for all failing tests

by Marcus Denker

On 04.09.2009, at 19:23, Peter Hugosson-Miller wrote: > Hmmm, I've just got back from ESUG, and I thought I'd start on these > tonight, since I'm still a bit pumped from the fantastic conference > (thanks guys!!). :-) > BUT, when I started from a clean 10433 image, did a software update > (to 10435) saved the image and ran the TestRunner, I'm suddenly > getting 22 errors. All of the 20 new errors are to do with > PragmaCollector[...] or PragmaSetting[...]. > > Did I miss something, or is this a known temporary state that > someone is working on? There are a bunch of classes missing now > (probably from the Issue 1159 change), and maybe someone forgot to > delete the (now obsolete) tests? > Ups. I forgot to delete the tests of system-settings... will do. > I don't want to spend a couple of hours barking up the wrong tree, > so is it OK for me to carry on and expect this to be sorted out soon? > Should not be a problem to continue. The new errors are independend. Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Sept. 5, 2009

[Pharo-project] question about Issue 207: ImageSegment discoverActiveClasses strange error

by sheridan＠sheridan-mahoney.com

- retrying in plain text... Hello, I am new to Pharo, and so have been perusing the bug database, and reading the recent posts in this list in order to investigate how to become involved in this community.  So far, I am very impressed! and encouraged that such a technically expert and friendly, supportive group is coelescing on this work effort! I have found a report that seems quite interesting, and have done some digging into the issue described here: http://code.google.com/p/pharo/issues/detail?id=207 ( ImageSegment discoverActiveClasses strange error ) and now I have a few questions I was hoping to get feedback on. It seems that, after using this method, some follow-up is required in order to reset the image back to a usable state.  And there are several options as to how to do that: 1) ImageSegment discoverActiveClasses. ImageSegment activeClasses size printString , ' classes were active out of ' , Smalltalk allClasses size printString. - this type of statment order will reset things ok.         2) ImageSegment discoverActiveClasses. ImageSegment  recoverFromMDFault. ImageSegment activeClasses. - it appears you still need the activeClasses method to reset the image (which wasn't entirely clear from the method comments - further comments may be useful here), otherwise there are classes with methodDictionaries that are set to nil. 3) ImageSegment discoverActiveClasses. Smalltalk at: #MDFaultDict put: Dictionary new. ImageSegment  recoverFromMDFaultWithTrace. Smalltalk at: #MDFaultDict. - this sequence of statments will give the user a report of active classes along with a description of how they came to be used. Similar to above o/w. 4)ImageSegment discoverActiveClasses. ImageSegment swapOutInactiveClasses. - there are at least 2 problems with this sequence - a)  initial result is a DNU - ThreadSafeTranscript(Object)>>doesNotUnderstand: #print    b) when you comment out the Transcript print statements to avoid the DNUs you get: ByteString(Object)>errorImproperStore I will be looking further into this issue, but was just wondering, firstly, is this a useful area to be spending time, and secondly, would it be appropriate to start a new bug, or update the old one?  Many thanks for your comments, Sheridan Mahoney  

Sept. 5, 2009

[Pharo-project] question about Issue 207: ImageSegment discoverActiveClasses strange error

by sheridan＠sheridan-mahoney.com

Sept. 5, 2009

Re: [Pharo-project] Getting Pharo 1.0 released

by csrabak＠bol.com.br

Em 04/09/2009 20:11, Igor Stasenko < siguctua(a)gmail.com > escreveu: > 2009/9/3 StÃ©phane Ducasse : > > Hi all > > > > I suggest the following: we go over the bug tracker and move to > > 1.1 all the issues that are > > not showstopper and we declare pharo 1.0 done and we open pharo > > 1.1 alpha > > Does it make sense to you? > Can i suggest another strategy? Declare current image a pharo 1.0 > release candidate. > And after a month - make a release. But, during this month, punish > hard those who using older pharo images. :) > So until Pharo 1.0 release we'll stop unthaw the trouts? ;-)

Sept. 5, 2009

[Pharo-project] Issue with DisplayText and InterpreterSimulator

by Andrey Larionov

I'm post an issue http://code.google.com/p/pharo/issues/detail?id=1173 Looks like call of aDisplayText form: in MorphicUIManage>>composeFormFor: is redundant Found during trying to run InterpreterSimulator (i realy want to help improve project). After i add accessor, i recieve an DNU of ByteSymbol>>coerceTo:sim: Is any have any idea. Is this method missing in VMMaker package or removed in Pharo.

Sept. 5, 2009

[Pharo-project] Bug-Tracker Status

by Marcus Denker

Reported Bugs: 1170 Closed: 926 Open: 244 1.0: 24 Marcus -- Marcus Denker - http://marcusdenker.de PLEIAD Lab - Computer Science Department (DCC) - University of Chile

Sept. 4, 2009

Re: [Pharo-project] Getting Pharo 1.0 released

by Peter Hugosson-Miller

On Sat, Sep 5, 2009 at 1:11 AM, Igor Stasenko <siguctua(a)gmail.com> wrote: > 2009/9/3 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > Hi all > > > > I suggest the following: > > we go over the bug tracker and move to 1.1 all the issues that are > > not showstopper > > and we declare pharo 1.0 done > > and we open pharo 1.1 alpha > > > > Does it make sense to you? > > Can i suggest another strategy? > Declare current image a > pharo 1.0 release candidate. > > And after a month - make a release. > But, during this month, punish hard those who using older pharo images. :) > > > > Stef > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > Sounds OK, but I still think it would be wrong to make a release until all tests are green (without cheating!) -- Cheers, Peter

Sept. 4, 2009

Re: [Pharo-project] Bug reports for all failing tests

by Peter Hugosson-Miller

On Fri, Sep 4, 2009 at 8:31 PM, Peter Hugosson-Miller <oldmanlink(a)gmail.com>wrote: > On 4 sep 2009, at 20.11, Marcus Denker <denker(a)acm.org> wrote: > > >> On 04.09.2009, at 13:48, Peter Hugosson-Miller wrote: >> >>> >>>> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.0 >>>> >>>> >>> I *love* fixing failing tests, so if any of those issues are going >>> begging, I'd be happy to take some :-) >>> >>> >> Yes, that would be cool! I fixed some, those I will now put into the >> next >> update. But some are left that would be nice if they are killed: >> >> 1167 >> 1165 >> 1164 >> >> Marcus >> >> >> >> >> -- >> Marcus Denker - http://marcusdenker.de >> PLEIAD Lab - Computer Science Department (DCC) - University of Chile >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > OK, I'll take those. > > -- > Cheers, > Peter > Hmmm, I've just got back from ESUG, and I thought I'd start on these tonight, since I'm still a bit pumped from the fantastic conference (thanks guys!!). BUT, when I started from a clean 10433 image, did a software update (to 10435) saved the image and ran the TestRunner, I'm suddenly getting 22 errors. All of the 20 new errors are to do with PragmaCollector[...] or PragmaSetting[...]. Did I miss something, or is this a known temporary state that someone is working on? There are a bunch of classes missing now (probably from the Issue 1159 change), and maybe someone forgot to delete the (now obsolete) tests? I don't want to spend a couple of hours barking up the wrong tree, so is it OK for me to carry on and expect this to be sorted out soon? -- Cheers, Peter

Sept. 4, 2009

Re: [Pharo-project] Impossible launc/use Lumiere

by nullPointer

My knowledges of OpenGL is very poor. For you answer i see not is possible use Lumiere/OpenGL for the thing than i have in mind. Regards. Igor Stasenko wrote: > > 2009/9/4 nullPointer <epicfan(a)gmail.com>: >> >> but could be possible in Lumiere, for example, use external widgets libs >> of >> OpenGL? >> the problem for me is the widgets. Exists only a few basic widgets in >> Morphic/Polymorph, and be hard of do for me. Or create a new set of >> widgets >> in Morphic or use something do it external. The problem for me not is the >> way of Morphic is drawed, else the way of Morphic is do it. Im developing >> a >> UIBuilder and the main problem is unify all events and properties of >> differents widgets in a same public interface (via Traits). Perhaps that >> Â it >> is not worth the pain and is best create a set of widgets from start; and >> if >> is possible use OpenGL still better. >> > Sorry, maybe i don't understand something... > But how OpenGL could help you with having a richer set of widgets? > An OpenGL is a very basic drawing library, where you can draw the > simplest primitives: > - points, lines, triangles. > Yes, you can do many tricks with OpenGL, but still all you have is > basically points, lines and triangles. > >> Regards, and thanks for the help. >> >> And excuse me for my poor english :)) >> >> >> Igor Stasenko wrote: >>> >>> 2009/9/4 nullPointer <epicfan(a)gmail.com>: >>>> >>>> I try use Lumiere >>>> >>>> http://vst.ensm-douai.fr/ESUG2009Media/uploads/1/lumiereIWST-2.pdf >>>> >>>> Â for show a sample OpenGL window but donÂ´t works. I dont know what i >>>> doing >>>> bad.What is needed for use OpenGL in Pharo? >>>> >>>> Is a stupid idea use OpenGL under Pharo for create 2d UIs ? Â My idea is >>>> use >>>> Lumiere for build UIs embedded in a morphic window, but with OpenGL >>>> widgets, >>>> buttons, textboxes etc Â s Â is a possible idea? Â I could for example use >>>> OpenGL external widgets libs for use in Lumiere? Will be fantastic do a >>>> UIBuilder using that. If Lumiere dont works for that exists another lib >>>> o >>>> posibility? >>> >>> yes, there is. Called GLMorphic. see at squeaksource. And its already >>> drawing all morphic UI using opengl calls. >>> Lumiere is more about rendering 3d scenery, not 2d UI. >>> But it contains the full OpenGL bindings (using Alien), so, nothing >>> prevents you from writing own stuff & doing anything with it. >>> There is also OpenVG binding API, which i bound recently to Squeak/Pharo >>> it is for drawing 2d vector graphics using different kinds of shapes, >>> fills etc. It resembles pretty much >>> of the same functionality as in Adobe Flash - gradients, fills, >>> strokes, patterns, images etc etc. >>> It is waiting for you to explore :) >>> Unfortunately the OpenVG plugin iz available for windoze only. >>> >>>> >>>> Regards >>>> -- >>>> View this message in context: >>>> http://n2.nabble.com/Impossible-launc-use-Lumiere-tp3582501p3582501.html >>>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>>> >>>> _______________________________________________ >>>> 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 >>> >> >> -- >> View this message in context: >> http://n2.nabble.com/Impossible-launc-use-Lumiere-tp3582501p3583015.html >> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >> >> _______________________________________________ >> 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 > -- View this message in context: http://n2.nabble.com/Impossible-launc-use-Lumiere-tp3582501p3583062.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Sept. 4, 2009

Re: [Pharo-project] Getting Pharo 1.0 released

by Igor Stasenko

2009/9/3 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > Hi all > > I suggest the following: > Â Â Â Â we go over the bug tracker and move to 1.1 all the issues that are > not showstopper > Â Â Â Â and we declare pharo 1.0 done > Â Â Â Â and we open pharo 1.1 alpha > > Does it make sense to you? Can i suggest another strategy? Declare current image a pharo 1.0 release candidate. And after a month - make a release. But, during this month, punish hard those who using older pharo images. :) > Stef > > _______________________________________________ > 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.

Sept. 4, 2009