- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Inspector broken ...

by Guido Stepken

Ahhh! Works fine! Happy again! That Menu "All Instances" when inspecting a integer value in 'Shout Workspace' doesn't really make sense and causes Pharao to hang a few minutes. That really should be improved :) tnx, keep up the good work! regards, Guido Stepken Frederic Pluquet-3 wrote: > > You can retreive the childs 'Class', 'Methods' and 'Possible types': go to > the preferences browser, go to the category 'Inspector' and enable what > you > need. > > FrÃ©d > ---- > FrÃ©dÃ©ric Pluquet > UniversitÃ© Libre de Bruxelles (ULB) > Assistant > http://www.ulb.ac.be/di/fpluquet > > > On Thu, Dec 10, 2009 at 5:59 PM, Damien Cassou > <damien.cassou(a)gmail.com>wrote: > >> On Thu, Dec 10, 2009 at 4:47 PM, Guido Stepken <gstepken(a)googlemail.com> >> wrote: >> > When i open up "Shout Browser", type in "2" and inspect that number >> with >> > Inspector "alt-i" ... it won't show the features of that object any >> > longer in 1.1 alpha and - thats new - also in 1.0! (newest version, all >> > updated installed) ... >> >> what do you mean by "features"? The methods have been removed from the >> inspector view to avoid clutering it. >> >> -- >> Damien Cassou >> http://damiencassou.seasidehosting.st >> >> "Lambdas are relegated to relative obscurity until Java makes them >> popular by not having them." James Iry >> >> _______________________________________________ >> 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 > -- View this message in context: http://n2.nabble.com/Inspector-broken-tp4146029p4149169.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Dec. 11, 2009

Re: [Pharo-project] Gofer git

by Adrian Kuhn

StÃ©phane Ducasse <stephane.ducasse@...> writes: > I do not know if you noticed that with the latest version > of Gofer you can get a full git behavior > > Tx lukas > Lukas, this is just plain awesome! --AA

Dec. 10, 2009

[Pharo-project] MetacelloRepository (was [ANN] ConfigurationOfAlgernon on MonticelloRepository)

by Esteban Lorenzano

Ouch, I meant "MetacelloRepository"... is late here... I'm tired ;) On 2009-12-10 19:26:02 -0300, Esteban Lorenzano <estebanlm(a)gmail.com> said: > Hi, > For all the Algernon lovers (right now, Mariano and my self), I want to > announce a configuration available to Algernon on MetacelloRepository. > This version uses just monticello packages and metacello configuration > (I mean: no universes needed). > As always, you can install it by executing: > > ConfigurationOfAlgernon project latestVersion load. > > Enjoy! > Esteban

Dec. 10, 2009

[Pharo-project] [ANN] ConfigurationOfAlgernon on MonticelloRepository

by Esteban Lorenzano

Hi, For all the Algernon lovers (right now, Mariano and my self), I want to announce a configuration available to Algernon on MetacelloRepository. This version uses just monticello packages and metacello configuration (I mean: no universes needed). As always, you can install it by executing: ConfigurationOfAlgernon project latestVersion load. Enjoy! Esteban

Dec. 10, 2009

Re: [Pharo-project] [Fwd: Issue 1571: automaticPlatformSettings preference]

by Henrik Sperre Johansen

Is there any time you do *not* want things set automatically for you based on platform if it's needed? I vote remove it. Cheers, Henry On 10.12.2009 22:18, StÃ©phane Ducasse wrote: > may be we should use it :) > or we remove it. > > Stef > > On Dec 10, 2009, at 9:59 PM, Alain Plantec wrote: > > >> >> From: Alain Plantec<alain.plantec(a)univ-brest.fr> >> Date: December 10, 2009 9:58:30 PM GMT+01:00 >> To: Pharo-project(a)lists.gforge.inria.fr >> Subject: Issue 1571: automaticPlatformSettings preference >> Reply-To: alain.plantec(a)univ-brest.fr >> >> >> this preference is only used by SmalltalkImage>>setPlatformPreferences. >> It was here to set some preferences depending on the platform. >> It has not effect anymore since #soundStopWhenDone and #soundQuickStart are >> completely ignored. >> I suggest to remove automaticPlatformSettings preference. >> >> What do you think ? >> >> Alain >> >> >> >> setPlatformPreferences >> "Set some platform specific preferences on system startup" >> | platform specs | >> Preferences automaticPlatformSettings ifFalse: [^self]. >> platform := self platformName. >> specs := #( >> (soundStopWhenDone false) >> (soundQuickStart false) >> ). >> platform = 'Win32' ifTrue:[ >> specs := #( >> (soundStopWhenDone true) >> (soundQuickStart false) >> )]. >> platform = 'Mac OS' ifTrue:[ >> specs := #( >> (soundStopWhenDone false) >> (soundQuickStart true) >> )]. >> specs do:[:tuple| >> Preferences setPreference: tuple first toValue: (tuple last == true). >> ]. >> >> >> >> >> >> >> _______________________________________________ >> 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. 10, 2009

Re: [Pharo-project] Problems with updates 1.0 & 1.1 on XP ...

by Henrik Sperre Johansen

"Fixed" in the sense it doesn't happen often, and likely requires a VM-level rather than image-level fix, yes. ;) Cheers, Henry On 10.12.2009 21:05, StÃ©phane Ducasse wrote: > so this is fixed :) > lol > software.... well we have (as a community to make progress on tests, documentation and tools to produce reliable software) > Stef > > On Dec 10, 2009, at 6:26 PM, Henrik Johansen wrote: > > >> I got it once last night, on Windows 7 RC1, updating the core image from 11080 to 11082(or3). >> There was a primitive failure mentioned in the error dialog, I stupidly closed the message to examine the log, but none had been written :/ >> >> Tried updating the same image 3 times after that, and got no crashes... >> >> Cheers, >> Henry >> >> On Dec 10, 2009, at 3:49 52PM, laurent laffont wrote: >> >> >>> Hi, >>> >>> I've also tested on XP Pro SP3, with windows installers. No errors for both rc1 and alpha.. 1.1 alpha took 20mn to update to #11083. >>> >>> What is you configuration ? >>> >>> Laurent >>> _______________________________________________ >>> 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. 10, 2009

Re: [Pharo-project] [Fwd: Issue 1571: automaticPlatformSettings preference]

by StÃ©phane Ducasse

may be we should use it :) or we remove it. Stef On Dec 10, 2009, at 9:59 PM, Alain Plantec wrote: > > > From: Alain Plantec <alain.plantec(a)univ-brest.fr> > Date: December 10, 2009 9:58:30 PM GMT+01:00 > To: Pharo-project(a)lists.gforge.inria.fr > Subject: Issue 1571: automaticPlatformSettings preference > Reply-To: alain.plantec(a)univ-brest.fr > > > this preference is only used by SmalltalkImage>>setPlatformPreferences. > It was here to set some preferences depending on the platform. > It has not effect anymore since #soundStopWhenDone and #soundQuickStart are > completely ignored. > I suggest to remove automaticPlatformSettings preference. > > What do you think ? > > Alain > > > > setPlatformPreferences > "Set some platform specific preferences on system startup" > | platform specs | > Preferences automaticPlatformSettings ifFalse: [^self]. > platform := self platformName. > specs := #( > (soundStopWhenDone false) > (soundQuickStart false) > ). > platform = 'Win32' ifTrue:[ > specs := #( > (soundStopWhenDone true) > (soundQuickStart false) > )]. > platform = 'Mac OS' ifTrue:[ > specs := #( > (soundStopWhenDone false) > (soundQuickStart true) > )]. > specs do:[:tuple| > Preferences setPreference: tuple first toValue: (tuple last == true). > ]. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 10, 2009

[Pharo-project] [update 1.1] #11086

by StÃ©phane Ducasse

11086 ----- - Issue 1457: CharacterSet removeAll CharacterSet - Refactorings from trunk - Part1 - cache byteArrayMap of WideCharacterSet - boost WideCharacterSet do: (using a ByteArray instead of WordArray to avoid Large Integers) - implement remove:ifAbsent: to fulfill subclassResponsibility This part1 has an initialize method to mutate WideCharacterSet instances to the new internal format. This support code will be removed in part2 - Issue 1568: Preferences migration part7 * remove TheWorldMainDockingBar * migrate "morphic" "fileout" and "button" groups next tomorrow :) Good night Stef

Dec. 10, 2009

[Pharo-project] [Fwd: Issue 1571: automaticPlatformSettings preference]

by Alain Plantec

Dec. 10, 2009

Re: [Pharo-project] How to report a bug ? [WAS] lukas-renggli.ch down, mirrors exists ?

by Adrian Lienhard

Fine with me. We should just be consistent. On the website we have only used Pharo-core (www.pharo-project.org/?search=pharo-core) but I can change that. Adrian On Dec 10, 2009, at 20:53 , StÃ©phane Ducasse wrote: > indeed :) > PharoCore is cooler :) > > On Dec 10, 2009, at 5:13 PM, Miguel CobÃ¡ wrote: > >> Wasn't the names Pharo and PharoCore? >> >> http://gforge.inria.fr/frs/download.php/24983/PharoCore-1.1-11078-alpha.zip >> http://gforge.inria.fr/frs/download.php/24963/PharoCore-1.1-11068-alpha.zip >> >> http://gforge.inria.fr/frs/download.php/24991/PharoCore-1.0-10501rc1.zip >> http://gforge.inria.fr/frs/download.php/24363/PharoCore-1.0-10491rc1.zip >> >> IMHO, PharoCore looks better than Pharo-core, but the board has the >> last word. >> >> Cheers >> >> On Thu, Dec 10, 2009 at 2:16 AM, Adrian Lienhard <adi(a)netstyle.ch> >> wrote: >>> Thanks for pointing this out. I fixed the template. It should be >>> either "Pharo" or "Pharo-core". >>> >>> Adrian >>> >>> On Dec 9, 2009, at 19:45 , Michael Roberts wrote: >>> >>>> Hi, I like the template! >>>> >>>> However, we are mixing our brand up a bit. I thought we agreed we >>>> would not call the pharo image a dev image? or did I miss >>>> something? >>>> So we are in this state where some things (e.g the installers, the >>>> pharo images) have dev in their name/filename, and sometimes we >>>> just >>>> call it Pharo in our documentation and conversation. We should try >>>> and be consistent, or rethink the branding. It's caused by us >>>> having >>>> one artifact without a suffix, whereas the rest do. (pharo, >>>> pharo-core, pharo-web). >>>> >>>> thanks, >>>> Mike >>>> >>>> On Thu, Dec 3, 2009 at 12:55 PM, Adrian Lienhard <adi(a)netstyle.ch> >>>> wrote: >>>>> Thanks, I updated the template. >>>>> >>>>> Adrian >>>>> >>>>> On Dec 3, 2009, at 11:26 , laurent laffont wrote: >>>>> >>>>>> A first template: >>>>>> >>>>>> >>>>>> If you fill an issue for the first time, please read "How to >>>>>> report >>>>>> bugs" >>>>>> at http://www.pharo-project.org/community/issue-tracking >>>>>> >>>>>> Pharo image: <core, dev or web> >>>>>> Pharo core version: <copy from World/System/About> >>>>>> Virtual machine used: <ex: pharo-vm-0.15.2f-linux> >>>>>> Class browser used if applicable: <ex: O2PackageBrowserAdaptor. >>>>>> If >>>>>> you don't >>>>>> know, print "SystemBrowser default"> >>>>>> >>>>>> Steps to reproduce: >>>>>> 1. >>>>>> 2. >>>>>> 3. >>>>>> >>>>>> >>>>>> Paste or attach stack trace if applicable (look at the file >>>>>> PharoDebug.log >>>>>> located in the same directory as your image): >>>>>> >>>>>> Thank you ! >>>>>> >>>>>> Laurent >>>>>> >>>>>> 2009/12/3 Mariano Martinez Peck <marianopeck(a)gmail.com> >>>>>> >>>>>>> Adrian: Thanks for your changes! It looks much better :) >>>>>>> >>>>>>> Laufert: yes, that's a cool idea. I wasn't aware neither. >>>>>>> >>>>>>> Could someone write a template? Then we just add the link to the >>>>>>> new page. >>>>>>> >>>>>>> Cheers >>>>>>> >>>>>>> Mariano >>>>>>> >>>>>>> >>>>>>> On Thu, Dec 3, 2009 at 10:44 AM, Adrian Lienhard <adi(a)netstyle.ch >>>>>>> > >>>>>>> wrote: >>>>>>> >>>>>>>> ah, I didn't know that is possible. Good idea! >>>>>>>> >>>>>>>> Adrian >>>>>>>> >>>>>>>> On Dec 3, 2009, at 10:34 , laurent laffont wrote: >>>>>>>> >>>>>>>>> May be you should fill the issue templates on google code >>>>>>>>> issue >>>>>>>>> tracker. >>>>>>>>> Like this: http://code.google.com/p/chromium/issues/entry >>>>>>>>> >>>>>>>>> Laurent >>>>>>>>> >>>>>>>>> >>>>>>>>> On Thu, Dec 3, 2009 at 10:18 AM, Adrian Lienhard >>>>>>>>> <adi(a)netstyle.ch> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Thanks Mariano. I have condensed your text a bit and put it >>>>>>>>>> online at >>>>>>>>>> http://www.pharo-project.org/community/issue-tracking >>>>>>>>>> >>>>>>>>>> Cheers, >>>>>>>>>> Adrian >>>>>>>>>> >>>>>>>>>> BTW, I also added the milestones for version 1.1 on the home >>>>>>>>>> page. >>>>>>>>>> >>>>>>>>>> On Dec 2, 2009, at 18:43 , Mariano Martinez Peck wrote: >>>>>>>>>> >>>>>>>>>>> I think it is really a good idea to create a page in the >>>>>>>>>>> Pharo >>>>>>>>>>> website about >>>>>>>>>>> how to report a bug. I think that only the link to the >>>>>>>>>>> google >>>>>>>>>>> page >>>>>>>>>>> is not >>>>>>>>>>> enough. Maybe it is a good idea to explain it a bit more, >>>>>>>>>>> and >>>>>>>>>>> in >>>>>>>>>>> addition, >>>>>>>>>>> give some tips. I would write something like the text >>>>>>>>>>> above in >>>>>>>>>>> that >>>>>>>>>>> page. I >>>>>>>>>>> would replace everywhere where it is a link to >>>>>>>>>>> http://code.google.com/p/pharo/issues/list to this new >>>>>>>>>>> page. >>>>>>>>>>> I saw >>>>>>>>>>> there >>>>>>>>>>> are these >>>>>>>>>>> >>>>>>>>>>> http://www.pharo-project.org/home (on the right) >>>>>>>>>>> http://www.pharo-project.org/documentation/faq (in the >>>>>>>>>>> question >>>>>>>>>>> "Where do I >>>>>>>>>>> report Pharo bugs?") >>>>>>>>>>> >>>>>>>>>>> My English is not the best at all, so any feedback is more >>>>>>>>>>> than >>>>>>>>>>> welcome. In >>>>>>>>>>> addition, maybe you don't agree with me. >>>>>>>>>>> >>>>>>>>>>> My main purpose is to help newcomers to submit issues. >>>>>>>>>>> >>>>>>>>>>> So....here it is >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> " >>>>>>>>>>> An issue, also known as ticket, represents many things. >>>>>>>>>>> It can >>>>>>>>>>> be a >>>>>>>>>>> bug, a >>>>>>>>>>> enchantment, packages, projects or commits to check, etc. >>>>>>>>>>> For the Pharo project, we use the Google Code issue tracker >>>>>>>>>>> which is >>>>>>>>>>> in >>>>>>>>>>> http://code.google.com/p/pharo/issues/list. >>>>>>>>>>> >>>>>>>>>>> - Before submitting you may take into account the following >>>>>>>>>>> tips: >>>>>>>>>>> >>>>>>>>>>> 1) Search in the existent issue list if there is something >>>>>>>>>>> similar. >>>>>>>>>>> In the >>>>>>>>>>> issue tracker you will find a "search" button to do that. Be >>>>>>>>>>> aware >>>>>>>>>>> that >>>>>>>>>>> there is a list of options and the default one is "Open >>>>>>>>>>> ticket". It >>>>>>>>>>> is very >>>>>>>>>>> common you need to search in "All issues". >>>>>>>>>>> >>>>>>>>>>> 2) If the ticket is a bug, and there is a problem with >>>>>>>>>>> certain >>>>>>>>>>> method, >>>>>>>>>>> search for that method or even for that class. It is very >>>>>>>>>>> common to >>>>>>>>>>> have >>>>>>>>>>> "MessageNotUnderstood". So, in this case you can search for >>>>>>>>>>> that >>>>>>>>>>> method. For >>>>>>>>>>> example, if you evaluate: >>>>>>>>>>> >>>>>>>>>>> TestCase nonExistentMethod: something other: another >>>>>>>>>>> >>>>>>>>>>> You will get "MessageNotUnderstood: TestCase >>>>>>>>>>> class>>nonExistentMethod:other:" >>>>>>>>>>> >>>>>>>>>>> So, here you can search for "nonExistentMethod:other:" for >>>>>>>>>>> exampe. >>>>>>>>>>> >>>>>>>>>>> 3) Do the same of 1) and 2) but on the mailing list. If >>>>>>>>>>> you are >>>>>>>>>>> new >>>>>>>>>>> or even >>>>>>>>>>> if you are not subscribed, you can see and search in the >>>>>>>>>>> mailing >>>>>>>>>>> list here: >>>>>>>>>>> http://n2.nabble.com/Pharo-Smalltalk-f2305563.html >>>>>>>>>>> >>>>>>>>>>> Sometimes some tickets are reported only in mailing list >>>>>>>>>>> (that's too >>>>>>>>>>> bad!!!). And maybe, that happened before you get >>>>>>>>>>> subscribed in >>>>>>>>>>> the >>>>>>>>>>> mailing >>>>>>>>>>> list. This way you are sure you are searching also in the >>>>>>>>>>> mailing >>>>>>>>>>> list. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> - When you are submitting an issue there are also some >>>>>>>>>>> tips you >>>>>>>>>>> should take >>>>>>>>>>> into account: >>>>>>>>>>> >>>>>>>>>>> 1) If the issue is related to ClassBrowser, refactor or >>>>>>>>>>> similar, >>>>>>>>>>> please tell >>>>>>>>>>> us which browser are you using. If you don't know it, just >>>>>>>>>>> evaluate >>>>>>>>>>> and see >>>>>>>>>>> the results of "SystemBrowser default". >>>>>>>>>>> >>>>>>>>>>> 2) ALWAYS say which version of VM, image (not only if it >>>>>>>>>>> is a >>>>>>>>>>> core >>>>>>>>>>> or pharo >>>>>>>>>>> image but also exactly the version) and OS are you using. >>>>>>>>>>> >>>>>>>>>>> 3) If the bug is reproducible, please explain how to do it >>>>>>>>>>> step >>>>>>>>>>> by >>>>>>>>>>> step. If >>>>>>>>>>> we have to use a particular VM, OS, or image, say it. >>>>>>>>>>> >>>>>>>>>>> 4) If the bug brings a debugger popup, it would be very >>>>>>>>>>> useful if >>>>>>>>>>> you could >>>>>>>>>>> put in the issue entry the full stacktrace. To get this >>>>>>>>>>> stacktrace, >>>>>>>>>>> there >>>>>>>>>>> are 2 ways: >>>>>>>>>>> >>>>>>>>>>> 4.a) Search for the generated PharoDebug.log which is in the >>>>>>>>>>> same >>>>>>>>>>> directory >>>>>>>>>>> where if image is and attached in the issue. In that file >>>>>>>>>>> there >>>>>>>>>>> is >>>>>>>>>>> not only >>>>>>>>>>> the full stacktrace but also some information about the >>>>>>>>>>> version >>>>>>>>>>> of >>>>>>>>>>> the VM, >>>>>>>>>>> OS and image you were using at that moment, etc. >>>>>>>>>>> >>>>>>>>>>> 4.b) In the debugger, open the contextual menu and there >>>>>>>>>>> is an >>>>>>>>>>> item >>>>>>>>>>> 'mail >>>>>>>>>>> out bug report' to directly send the stack trace with VM >>>>>>>>>>> version etc >>>>>>>>>>> to the >>>>>>>>>>> pharo list (or whoever you want to, but by default it's the >>>>>>>>>>> Pharo >>>>>>>>>>> ml). Of >>>>>>>>>>> course you can edit the message to describe your problem for >>>>>>>>>>> example. >>>>>>>>>>> >>>>>>>>>>> 5) If you are not a newcomer and you know a bit you can put >>>>>>>>>>> labels >>>>>>>>>>> to the >>>>>>>>>>> issue. For example if it should be Milestone 1.0 or Type- >>>>>>>>>>> Closure, or >>>>>>>>>>> TypeOB, >>>>>>>>>>> etc. >>>>>>>>>>> >>>>>>>>>>> 6) If you are not a newcomer and you know a bit you can copy >>>>>>>>>>> people >>>>>>>>>>> with the >>>>>>>>>>> "Cc:" option. This is very useful when you know that the >>>>>>>>>>> issue is >>>>>>>>>>> in a >>>>>>>>>>> certain package for example and you know who is >>>>>>>>>>> responsible or >>>>>>>>>>> maintainer of >>>>>>>>>>> it. >>>>>>>>>>> >>>>>>>>>>> 7) After submitting the issue, you must send and email to >>>>>>>>>>> the >>>>>>>>>>> mailing list >>>>>>>>>>> with the link. What you can do also is to copy and paste the >>>>>>>>>>> details >>>>>>>>>>> of the >>>>>>>>>>> issue in the body of the email. With this, all the people >>>>>>>>>>> know >>>>>>>>>>> about >>>>>>>>>>> it. >>>>>>>>>>> >>>>>>>>>>> 8) If the ticket is a MNU it would be very useful to put >>>>>>>>>>> that >>>>>>>>>>> message (in >>>>>>>>>>> our example "MessageNotUnderstood: TestCase >>>>>>>>>>> class>>nonExistentMethod:other:") in the description of the >>>>>>>>>>> ticket >>>>>>>>>>> or even >>>>>>>>>>> in the title of the issue and the subject of the email. With >>>>>>>>>>> this we >>>>>>>>>>> can >>>>>>>>>>> take advantage of the Google search engine. >>>>>>>>>>> >>>>>>>>>>> 9) If you have a fix remember you must sign the MIT license >>>>>>>>>>> first. >>>>>>>>>>> For more >>>>>>>>>>> information read http://www.pharo-project.org/license >>>>>>>>>>> >>>>>>>>>>> " >>>>>>>>>>> >>>>>>>>>>> On 2 dÃ©c. 2009, at 08:05, Mariano Martinez Peck wrote: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> 2009/12/2 laurent laffont <laurent.laffont(a)gmail.com> >>>>>>>>>>> >>>>>>>>>>>> Hello, >>>>>>>>>>>> >>>>>>>>>>>> I want to check if there's updates to Slime package as I >>>>>>>>>>>> faces >>>>>>>>>>>> several bugs >>>>>>>>>>>> but sources.lukas-renggli.ch seems to be down. Is there a >>>>>>>>>>>> mirror ? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> About the bugs (Slime-lr.24,current pharo rc1 web image), >>>>>>>>>>>> when I >>>>>>>>>>>> select >>>>>>>>>>>> refactor > code critics: >>>>>>>>>>>> >>>>>>>>>>>> - it seems that ParserTreeSearcher has been renamed to >>>>>>>>>>>> RBParserTreeSearcher. Thus there's several errors like >>>>>>>>>>>> WAChangesStateWhileRenderingRule>>initialize >>>>>>>>>>>> (ParseTreeSearcher is >>>>>>>>>>>> Undeclared) >>>>>>>>>>>> >>>>>>>>>>>> - this done, I have the error: >>>>>>>>>>>> AnObsoleteParseTreeSearcher(Object)>>doesNotUnderstand: >>>>>>>>>>>> #executeTree:initialAnswer: (from >>>>>>>>>>>> RBAssignmentIfTrueRule>>checkMethod:) >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> How do I save a stack trace to a text file (or clipboard) >>>>>>>>>>>> from >>>>>>>>>>>> the >>>>>>>>>>>> debugger >>>>>>>>>>>> ? >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Look for the file called PharoDebug.log which is in the >>>>>>>>>>> directory >>>>>>>>>>> where the >>>>>>>>>>> image is. It will have not only the stacktrace but also much >>>>>>>>>>> more >>>>>>>>>>> information, as VM version, OS, etc. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> or.... >>>>>>>>>>> >>>>>>>>>>> In the debugger, open the contextual menu and there is an >>>>>>>>>>> item >>>>>>>>>>> 'mail >>>>>>>>>>> out bug >>>>>>>>>>> report' to directly send the stack trace with VM version >>>>>>>>>>> etc to >>>>>>>>>>> the >>>>>>>>>>> pharo >>>>>>>>>>> list (or whoever you want to, but by default it's the Pharo >>>>>>>>>>> ml). Of >>>>>>>>>>> course >>>>>>>>>>> you can edit the message to make it shorter (we dont need >>>>>>>>>>> the >>>>>>>>>>> full >>>>>>>>>>> stack in >>>>>>>>>>> general) and describe your problem etc. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Best, >>>>>>>>>>> >>>>>>>>>>> Mariano >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> Regards, >>>>>>>>>>>> >>>>>>>>>>>> Laurent Laffont >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> 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 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> Simon >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> 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 >>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> 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 >>>>> >>>> >>>> _______________________________________________ >>>> 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. 10, 2009