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

Re: [Pharo-project] [Moose-dev] Re: duplication between default: and version40beta2:?

by Marcus Denker

On Dec 3, 2009, at 1:40 PM, Laval Jannik wrote: > Yeh, > > Now, I understand the process... (I am slow :) ) > > But, in this process we must specify versions and maintain it. > Is there a solution (in monticello maybe) to say a version of a package is stable. > So in this case, we can say "I want last stable version of my package" and we do not need to maintain ConfigurationOf. > The problem is that it's not one package... your system will be 20 packges. You can say " load the latest of all, that works". But: now I want to load the version that worked so great last month. Which set of packages exactly where that? Tagging single packages as "release" will not help, as you don't have the info which released package works with which other released package. Marcus

Dec. 3, 2009

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

by Adrian Lienhard

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

Dec. 3, 2009

Re: [Pharo-project] [Moose-dev] Re: duplication between default: and version40beta2:?

by Laval Jannik

Yeh, Now, I understand the process... (I am slow :) ) But, in this process we must specify versions and maintain it. Is there a solution (in monticello maybe) to say a version of a package is stable. So in this case, we can say "I want last stable version of my package" and we do not need to maintain ConfigurationOf. Maybe this discussion is more global than moose community, So I copy it in pharo mailing list. Jannik On Dec 3, 2009, at 13:15 , Tudor Girba wrote: > Hi Stef, > > As I mentioned before, default represents the work in progress. It can happen that the work in progress is the same as the previously released version, and that is why you will see duplication. > > Another possibility would be to reuse the previous configuration and just mention the delta (of adding new packages), but I am not sure this would scale in the long run. > > So, the current process is: > - work on default > - when we release, we copy the method in a new baselineXXX > - we create a hardcoded version in versionXXX > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "We cannot reach the flow of things unless we let go." > > > > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)iam.unibe.ch > https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Dec. 3, 2009

Re: [Pharo-project] small pharo success story

by Marcus Denker

On Sat, Sep 5, 2009 at 3:01 PM, Marcus Denker <denker(a)acm.org> wrote: > Hi, > > 2Denker now has it's first iPhone app deployed and in the store that uses a > Pharo backend: > > Â Â Â Â http://2denker.de/findabike Â (german only) > > The app shows the bikes of DB (German Railway Company): > http://en.wikipedia.org/wiki/Call_a_Bike > > The small success got a bit larger (in terms of users....). An improved version of our app is now the official app of DB (and as such free of charge): http://2denker.de/callabike Pharo continues to be used on the server side for this version. Marcus -- Marcus Denker -- marcus(a)2denker.de http://www.2denker.de 2denker UG (haftungsbeschrÃ¤nkt) Sitz KÃ¶ln Amtsgericht - Registergericht - KÃ¶ln, HRB 65065 GeschÃ¤ftsfÃ¼hrer: Christian Denker und Dr. Marcus Denker

Dec. 3, 2009

[Pharo-project] Slime at work

by laurent laffont

Hi, I'm reading Dynamic Web Development with Seaside. I'm lost on how to open Slime on a specific package in Pharo, as described here: http://book.seaside.st/book/components/slime/at-work Regards, Laurent

Dec. 3, 2009

Re: [Pharo-project] ParserTreeSearcher problem (lukas can you check)

by laurent laffont

> > > dont worry.\Tell us more what is the problem you fix because it is probably > something for lukas :) > > What I've done: 1. open refactor > code critics. Change every ParserTreeSearcher to RBParserTreeSearcher when debugger signals an error. 2. do "RBTransformationRule initializeRecursiveSelfRule" to initialize RBTransformationRule RecursiveSelfRule class variable (hihi I've learned to play with the debugger to find this one :) Laurent

Dec. 3, 2009

Re: [Pharo-project] StandardFonts vs Preferences

by Alain Plantec

Henrik Johansen a Ã©crit : > Alain, could you deprecate (and remove entires from Parameters) all the set... and get... font-messages in Preferences? > Would make it somewhat easier to make the transition from codebits using the Preferences methods for setting, which currently (in most cases) gives no feedback except not changing the fonts. (Like, say, the System Fonts-menu) > ok, sorry for that. I'm about to deliver another part of preferences migration (with deprecation of old preference methods) > Also, consider if the setDefaultFonts: / restoreDefaultFonts methods would be useful. > of course, the goal is to completely remove the Preferences class... Thanks for your feedbacks Cheers Alain > > Cheers, > Henry > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

Dec. 3, 2009

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

by laurent laffont

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 >

Dec. 3, 2009

[Pharo-project] StandardFonts vs Preferences

by Henrik Johansen

Alain, could you deprecate (and remove entires from Parameters) all the set... and get... font-messages in Preferences? Would make it somewhat easier to make the transition from codebits using the Preferences methods for setting, which currently (in most cases) gives no feedback except not changing the fonts. (Like, say, the System Fonts-menu) Also, consider if the setDefaultFonts: / restoreDefaultFonts methods would be useful. Cheers, Henry

Dec. 3, 2009

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

by Mariano Martinez Peck

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 >

Dec. 3, 2009