- Pharo-dev - lists.pharo.org

Re: [Pharo-project] [ann 1.1] pre-built #11068

by Adrian Lienhard

yea, at the time I wrote this, there were no known problems... I updated the text and added links to the two filtered lists of the tracker. Adrian On Dec 2, 2009, at 18:12 , Mariano Martinez Peck wrote: > yes, sorry, you are right....then what it says here is wrong > http://www.pharo-project.org/home > > "A first release candidate was published on October 20, 2009. All > tests in > the core image pass and there are currently no known critical > problems." > > Or...maybe they are not critical. I really don't know. > > Mariano > > > On Wed, Dec 2, 2009 at 6:06 PM, Adrian Lienhard <adi(a)netstyle.ch> > wrote: > >> We still have several open issues for 1.0 that need work: >> >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.0 >> http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.0-DevImage >> >> Most notably the Input problem (double paste) and some OB problems. >> >> Adrian >> >> On Dec 2, 2009, at 17:33 , Mariano Martinez Peck wrote: >> >>> Excellent!!! Demian or someone, do you know where we can build a >>> Pharo >>> image with this 1.1 core ? >>> >>> And another question....shouldn't we release 1.0 stable release ? >>> there are >>> no pending 1.0 issues and it is on the web for more than a month :) >>> >>> Cheers >>> >>> Mariano >>> >>> >>> On Wed, Dec 2, 2009 at 3:19 PM, Marcus Denker <denker(a)acm.org> >>> wrote: >>> >>>> >>>> >>>> >> http://gforge.inria.fr/frs/download.php/24963/PharoCore-1.1-11068-alpha.zip >>>> >>>> _______________________________________________ >>>> 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. 2, 2009

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

by Mariano Martinez Peck

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

Dec. 2, 2009

[Pharo-project] Committing resource files with Monticello or along Monticello packages

by Simon Denier

Hi there I would like to know if you people have some tricks or clever strategies to commit resource files (binary, icons, big text files) along monticello packages. And how do you load such files along monticello packages. My use case: I have a big text file with data, which I use as a model to run some tests. I don't want to store this information in the body of a method. -- Simon

Dec. 2, 2009

Re: [Pharo-project] [ann 1.1] pre-built #11068

by Damien Cassou

2009/12/2 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Excellent!!!Â Demian or someone, do you know where we can build a Pharo > image with this 1.1 core ? Sure, apply the script that is attached to all Pharo images I produce. -- Damien Cassou http://damiencassou.seasidehosting.st "Lambdas are relegated to relative obscurity until Java makes them popular by not having them." James Iry

Dec. 2, 2009

Re: [Pharo-project] [ann 1.1] pre-built #11068

by Mariano Martinez Peck

yes, sorry, you are right....then what it says here is wrong http://www.pharo-project.org/home "A first release candidate was published on October 20, 2009. All tests in the core image pass and there are currently no known critical problems." Or...maybe they are not critical. I really don't know. Mariano On Wed, Dec 2, 2009 at 6:06 PM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > We still have several open issues for 1.0 that need work: > > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.0 > http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.0-DevImage > > Most notably the Input problem (double paste) and some OB problems. > > Adrian > > On Dec 2, 2009, at 17:33 , Mariano Martinez Peck wrote: > > > Excellent!!! Demian or someone, do you know where we can build a > > Pharo > > image with this 1.1 core ? > > > > And another question....shouldn't we release 1.0 stable release ? > > there are > > no pending 1.0 issues and it is on the web for more than a month :) > > > > Cheers > > > > Mariano > > > > > > On Wed, Dec 2, 2009 at 3:19 PM, Marcus Denker <denker(a)acm.org> wrote: > > > >> > >> > >> > http://gforge.inria.fr/frs/download.php/24963/PharoCore-1.1-11068-alpha.zip > >> > >> _______________________________________________ > >> 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. 2, 2009

Re: [Pharo-project] Very tiny fonts

by Marcus Denker

On Dec 2, 2009, at 6:06 PM, Marcus Denker wrote: > Hi, > > While discussing Visualisations, we realized we want *really* tiny fonts... > > Here is a hand-drawn sub-pixel font that is just 5 pixels high... > > http://typophile.com/node/61920 > > > Now we need to make a font for Pharo... we should check in addition how good/bad freetype or the mac renderes tinty fonts from the standard truetype fonts. Marcus

Dec. 2, 2009

[Pharo-project] Very tiny fonts

by Marcus Denker

Hi, While discussing Visualisations, we realized we want *really* tiny fonts... Here is a hand-drawn sub-pixel font that is just 5 pixels high... http://typophile.com/node/61920 Now we need to make a font for Pharo... Marcus

Dec. 2, 2009

Re: [Pharo-project] [ann 1.1] pre-built #11068

by Adrian Lienhard

We still have several open issues for 1.0 that need work: http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.0 http://code.google.com/p/pharo/issues/list?can=2&q=milestone=1.0-DevImage Most notably the Input problem (double paste) and some OB problems. Adrian On Dec 2, 2009, at 17:33 , Mariano Martinez Peck wrote: > Excellent!!! Demian or someone, do you know where we can build a > Pharo > image with this 1.1 core ? > > And another question....shouldn't we release 1.0 stable release ? > there are > no pending 1.0 issues and it is on the web for more than a month :) > > Cheers > > Mariano > > > On Wed, Dec 2, 2009 at 3:19 PM, Marcus Denker <denker(a)acm.org> wrote: > >> >> >> http://gforge.inria.fr/frs/download.php/24963/PharoCore-1.1-11068-alpha.zip >> >> _______________________________________________ >> 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. 2, 2009

Re: [Pharo-project] [ann 1.1] pre-built #11068

by Lukas Renggli

> And another question....shouldn't we release 1.0 stable release ? there are > no pending 1.0 issues and it is on the web for more than a month :) The keyboard is still broken: http://code.google.com/p/pharo/issues/detail?id=1323 Lukas > > At least it needs the fixes for O2 discussed in another thread. > > Cheers > > Mariano > > > On Wed, Dec 2, 2009 at 3:19 PM, Marcus Denker <denker(a)acm.org> wrote: >> >> >> Â http://gforge.inria.fr/frs/download.php/24963/PharoCore-1.1-11068-alpha.zip >> >> _______________________________________________ >> 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 > -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 2, 2009

Re: [Pharo-project] [ann 1.1] pre-built #11068

by Simon Denier

On 2 dÃ©c. 2009, at 13:33, Mariano Martinez Peck wrote: > Excellent!!! Demian or someone, do you know where we can build a > Pharo image with this 1.1 core ? > > And another question....shouldn't we release 1.0 stable release ? > there are no pending 1.0 issues and it is on the web for more than a > month :) At least it needs the fixes for O2 discussed in another thread. > > Cheers > > Mariano > > > On Wed, Dec 2, 2009 at 3:19 PM, Marcus Denker <denker(a)acm.org> wrote: > > http://gforge.inria.fr/frs/download.php/24963/PharoCore-1.1-11068-alpha.zip > > _______________________________________________ > 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

Dec. 2, 2009