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

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

by Guido Stepken

Hi folks! I installed recent Pharo 1.0 and downloaded also the 1.1 alpha Image. Updating both fails finally. 1.1 stops updating at a certain point, 1.0 updates, but classbrowser finally doesn't work. Any ideas? tnx, Guido

Dec. 9, 2009

Re: [Pharo-project] package documentation viewer

by Simon Denier

On 9 dÃ©c. 2009, at 19:11, csrabak(a)bol.com.br wrote: > I also vote for having it running at Pharo website. > > However it gives another opportunity to my canvassing: it is imperative that the comments written (class and methods) be accurate and uptodate!! Can someone quickly run some query to see how bad it is? That is, how many classes without comment or with the generic template? > > -- > Cesar Rabak > > > Em 09/12/2009 11:06, Alexandre Bergel < alexandre(a)bergel.eu > escreveu: > > > Looks good. Maybe this could be part of the Pharo website no ? > > Alexandre > > > On 9 Dec 2009, at 07:49, laurent laffont wrote: > >> Hi, >> >> for fun and *for me*, I've made a small Seaside app to quickly >> browse all documentation in a Pharo image. >> It's package oriented, all classes and selectors comment on a >> single page, so I can use search and print functions of my web >> browser. >> >> Someone might have a use of it. It's here: http://www.squeaksource.com/SimpleWebDoc.html >> Screenshots: http://picasaweb.google.fr/laurent.laffont/Simplewebdoc >> >> Laurent >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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. 9, 2009

Re: [Pharo-project] getting rid of Symbol >> new: ?

by Mariano Martinez Peck

On Wed, Dec 9, 2009 at 9:40 AM, Adrian Lienhard <adi(a)netstyle.ch> wrote: > I don't have the VMMaker code at hand right now (or rather, don't have > time to look at it ;)), but I guess that after that piece of code you > pasted below there is a loop from the first field (BaseHeader+4) to > the last non-weak field (lastFieldOffset) in which the non-weak fields > are traced. Note, that if an object both fixed and indexable weak > fields the latter are always located after the former. You can see the > memory layout and object formats on the pages 9 and 10 of the slides > [1] (from a lecture about VMs I gave recently). > > Thanks for the explanation Adrian and the link Adrian...now, being a bit off-topic, I have the following situation about ImageSegment. I tried to reproduce it in a unit test, but I couldn't yet :( Suppose I create a segment with a tree of objects. Suppose inside of that tree I have an object that refers to an external object called XXX, thus it is put in the outPointers. Then I extract the segment, I write it to disk, and I put a nil to the segment variable. After that, for some reason, my object XXX is garbage collected from my image. Then I want to load again my segment (reading the file and installling it). What happens ? it fails? If true, suppose I have already "installed" some other objects, what happen with those objects? is this atomic ? Thanks a lot for anyone that can give me a hint. Mariano > Cheers, > Adrian > > [1] http://www.adrian-lienhard.ch/presentations > > On Dec 8, 2009, at 22:57 , Mariano Martinez Peck wrote: > > > On Tue, Dec 8, 2009 at 10:54 PM, Mariano Martinez Peck < > > marianopeck(a)gmail.com> wrote: > > > >> > >> > >> On Tue, Dec 8, 2009 at 5:07 PM, Adrian Lienhard <adi(a)netstyle.ch> > >> wrote: > >> > >>> > >>> On Dec 8, 2009, at 12:08 , Mariano Martinez Peck wrote: > >>> > >>>> On Fri, Dec 4, 2009 at 12:05 PM, Adrian Lienhard <adi(a)netstyle.ch> > >>>> wrote: > >>> > >>>> When you are creating your root of objects and you put symbols > >>>> inside, they > >>>> are not put in ourPointers but in ByteArray. > >>>> This is due to the fact that the only object who is pointing to > >>>> that > >>>> symbol > >>>> is inside the segment ? > >>> > >>> To be precise, the symbols are also pointed to by the symbol table, > >>> but only by weak references. Since image segments use the GC mark > >>> logic, these pointers are not considered. > >>> > >> > >> Ahhh ok. Now I see Symbol class >> rehash where it sets to > >> SymbolTable > >> := WeakSet > >> > >> Now...my finally question is, where in the code you can see the GC > >> only > >> mark "normal" objects and that week objects are not being taken into > >> account. Do you know ? I tried to search it but I didn't find it. > >> > >> > > Sorry, I forgot to said I found this in ObjectMemory >> markAndTrace: > > > > (self isWeakNonInt: oop) ifTrue: [ > > "Set lastFieldOffset before the weak fields in the receiver" > > lastFieldOffset := (self nonWeakFieldsOf: oop) << ShiftForWord. > > "And remember as weak root" > > weakRootCount := weakRootCount + 1. > > weakRoots at: weakRootCount put: oop. > > ] ifFalse: [ > > "Do it the usual way" > > lastFieldOffset := self lastPointerOf: oop. > > ]. > > > > > > But I don't know if this make sense or not. > > > > Thanks!! > > > > Mariano > > > > > >>>> What you do with this piece of code: > >>>> > >>>> symbolHolder := Symbol allSymbols. > >>>> > >>>> is to hold those symbols there. So, when ImageSegment uses the GC > >>>> techniques > >>>> to detect which objects are ONLY pointed from inside of the > >>>> segment, > >>>> the > >>>> symbols is not found (because it is accessible trough that test) > >>>> and > >>>> thus, > >>>> it goes to outPointers instead of ByteArray. > >>>> > >>>> And of course, if it is in outPointers instead of ByteArray when > >>>> the > >>>> segment > >>>> is loaded again, yo don't create a symbol again but use the same > >>>> object (the > >>>> one of the oop). > >>>> > >>>> I am correct? or I understood anything ? > >>> > >>> yes. > >>> > >>> Cheers, > >>> Adrian > >>> > >>> _______________________________________________ > >>> 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. 9, 2009

[Pharo-project] New configurations in MetacelloRepository

by Dale Henrichs

I've added the following configurations to the MetacelloRepository: ConfigurationOfKomHttpServer ConfigurationOfSPort2 ConfigurationOfSwazoo2 and updated ConfigurationOfSeaside30 updated to use the above configurations. Dale

Dec. 9, 2009

Re: [Pharo-project] package documentation viewer

by Alexandre Bergel

> However it gives another opportunity to my canvassing: it is > imperative that the comments written (class and methods) be accurate > and uptodate!! Indeed Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Dec. 9, 2009

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

by Michael Roberts

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 >

Dec. 9, 2009

Re: [Pharo-project] New User Experience Suggestion for 1.0

by csrabak＠bol.com.br

Adrian, I understand there is some reluctance in adding a "long text" (for the arbitrary definition of 'long'). As a counter argument, I would say that Squeak images are less laconic and two other Smalltalks I'm aware of (VW and ST/X) also carry a more thorough introduction for people who are trying first time. As some others that report working in trains or other places with limited (or none conectivity), it would be nice if we could have an image where the initial tour could be done without need to web access. More often than not, we download a lot of stuff to try it while waiting in some glass doors, airports, etc.! In retrospect, I think the way as Squeak had a welcome.txt or readme.txt that could even be read before launching the application would be a fine addition to our tools to make Pharo more (new) user friendly. my 0.01999... -- Cesar Rabak Em 08/12/2009 06:39, Adrian Lienhard <adi(a)netstyle.ch> escreveu: Please note that there is an issue in the tracker that discusses this. I've suggested to add a workspace but do not add a long text and code but link to the pages on the web that contain it so that we can more easily make updates. http://code.google.com/p/pharo/issues/detail?id=1479 Tim, would that be helpful for new users of Pharo? Cheers, Adrian On Dec 8, 2009, at 09:23 , Damien Cassou wrote: > Hi Tim, > > On Tue, Dec 8, 2009 at 12:51 AM, Tim Mackinnon > wrote: >> Guys - do you think you might consider bringing back the little >> Readme Workspace in the final 1.0 image (or maybe 1.1)? > > there is no technical difficulty. Could you please provide a text? I > will take care of putting it in a workspace. There may be something in > the Pharo wiki already. > > Thank you > > -- > 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

Dec. 9, 2009

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

by Michael Roberts

ok that's useful to know. it's a poor test case, i could not recreate it! would be good to add the fixes to the tracker. cheers, Mike On Wed, Dec 9, 2009 at 1:05 PM, Marcus Denker <denker(a)acm.org> wrote: > Hi, > > This "image need a while after update" is normal.

Dec. 9, 2009

Re: [Pharo-project] package documentation viewer

by csrabak＠bol.com.br

I also vote for having it running at Pharo website. However it gives another opportunity to my canvassing: it is imperative that the comments written (class and methods) be accurate and uptodate!! -- Cesar Rabak Em 09/12/2009 11:06, Alexandre Bergel < alexandre(a)bergel.eu > escreveu: Looks good. Maybe this could be part of the Pharo website no ? Alexandre On 9 Dec 2009, at 07:49, laurent laffont wrote: > Hi, > > for fun and *for me*, I've made a small Seaside app to quickly > browse all documentation in a Pharo image. > It's package oriented, all classes and selectors comment on a > single page, so I can use search and print functions of my web > browser. > > Someone might have a use of it. It's here: http://www.squeaksource.com/SimpleWebDoc.html > Screenshots: http://picasaweb.google.fr/laurent.laffont/Simplewebdoc > > Laurent > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 9, 2009

Re: [Pharo-project] Gofer git

by Lukas Renggli

> I do not know if you noticed that with the latest version of Gofer you can get a full git behavior Not full, but at least it mimics that Git syncs the local and remote repositories. > Gofer new > Â Â Â Â squeaksource: 'PharoTaskForces'; > Â Â Â Â addPackage: 'RPackage'; > Â Â Â Â pull This operation is called #fetch in the latest Gofer, I renamed it recently. This is how it is called originally in Git and it downloads all versions to the local package cache. > to pull all the packages pubslihed and fill up your local cache > > Gofer new > Â Â Â Â squeaksource: 'PharoTaskForces'; > Â Â Â Â addPackage: 'RPackage'; > Â Â Â Â push > > to push your local saved versions to the repository.... There is updated documentation in the class comment and on my blog article at <http://www.lukas-renggli.ch/blog/gofer>. > Of course it means that you can build a database and when you run your script > the cache is checked first.... so yes you can work in the train :) The reason why I didn't announce this, is because the current implementation has serious problems that need to be fixed. For example, reading from a remote repository that is not available silently fails. Furthermore, to determine the latest version all available versions from all repositories are merged, that is often not desired. I probably need to introduce some kind of a repository object where the user can specify these things (consider cache or not, fail silently or not, ...). Also there are no tests for any of this, so use it at your own risk. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Dec. 9, 2009