October 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] Noobie Browser question

by Tony Fleig

The Browser in Pharo Core and Pharo One-Click doesn't appear to have the features described in the Pharo By Example book in chapter 6. In particular, there is no History bar at the top. Clicking on the gray lozenge at the upper right of the browser window gives me the option of selecting the Browser or OBSystemBrowserAdaptor, neither of which seems to have the features shown in the book. Is there somewhere I can get the OmniBrowser described in the book, or has it been replaced with what appears to be a less-functional version? Thanks, TF

Oct. 27, 2010

Re: [Pharo-project] [update 1.2] #12217

by Tony Fleig

In my Pharo core image there is indeed a Software Update entry under System, but when I select it a window pops up that says "0 new update file(s) processed." In my Seaside One-Click Image, there is no Software Update entry at all. TF On Wed, Oct 27, 2010 at 10:32 AM, Peter Hugosson-Miller < oldmanlink(a)gmail.com> wrote: > It might be worth mentioning that you can get *all* the updates applied at > once by doing a "Software Update" from your current image. There's a menu > item to do that, but I can't currently remember which menu it sits on. I'm > sure someone else will be able to tell you. > > Good luck! > > -- > Cheers, > Peter. > > On 27 okt 2010, at 19:14, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > > > On Oct 27, 2010, at 5:51 PM, Tony Fleig wrote: > > > >> I am new to Pharo. This sounds like a change I would like to incorporate > in my environment. > >> > >> I assume 12217 is an identifier of something that might allow me to do > this, but what? Is there a noob document I should have read? > >> > > 12217 is the update number of version 1.2, which is the next unstable > release. (To be beta end of the month). > > > > Now if you want to cherry-pick a fix for your own development image > (which I guess is based on 1.1), > > the other numbers are more important. > > > > The Issues are numbers of Google bug tracker entries. > > > > http://code.google.com/p/pharo/issues/list > > > > (of course this just shows the open ones). > > > > Of the three issues, just one makes sense in 1.1: 2797 > > > > http://code.google.com/p/pharo/issues/detail?id=2797 > > > > there you find the code and description of the change. > > > >> > >> On Wed, Oct 27, 2010 at 1:28 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > >> > >> > >> Issue 3164: Fix find and seach all source > >> Issue 1801: Rescue Sophie Undo framework > >> Issue 2797: MIMEDocument class >> #guessTypeFromName: results in MNU > >> > > > > -- > > Marcus Denker -- http://www.marcusdenker.de > > INRIA Lille -- Nord Europe. Team RMoD. > > > > > > _______________________________________________ > > 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 >

Oct. 27, 2010

Re: [Pharo-project] [update 1.2] #12217

by Tony Fleig

Thanks Marcus. By reading the issue 2797, I can see what changes I need to make. I'm guessing there is no automated way to do this? TF On Wed, Oct 27, 2010 at 10:14 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Oct 27, 2010, at 5:51 PM, Tony Fleig wrote: > > > I am new to Pharo. This sounds like a change I would like to incorporate > in my environment. > > > > I assume 12217 is an identifier of something that might allow me to do > this, but what? Is there a noob document I should have read? > > > 12217 is the update number of version 1.2, which is the next unstable > release. (To be beta end of the month). > > Now if you want to cherry-pick a fix for your own development image (which > I guess is based on 1.1), > the other numbers are more important. > > The Issues are numbers of Google bug tracker entries. > > http://code.google.com/p/pharo/issues/list > > (of course this just shows the open ones). > > Of the three issues, just one makes sense in 1.1: 2797 > > http://code.google.com/p/pharo/issues/detail?id=2797 > > there you find the code and description of the change. > > > > > On Wed, Oct 27, 2010 at 1:28 AM, Marcus Denker <marcus.denker(a)inria.fr> > wrote: > > > > > > Issue 3164: Fix find and seach all source > > Issue 1801: Rescue Sophie Undo framework > > Issue 2797: MIMEDocument class >> #guessTypeFromName: results in MNU > > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 27, 2010

Re: [Pharo-project] [update 1.2] #12217

by Peter Hugosson-Miller

It might be worth mentioning that you can get *all* the updates applied at once by doing a "Software Update" from your current image. There's a menu item to do that, but I can't currently remember which menu it sits on. I'm sure someone else will be able to tell you. Good luck! -- Cheers, Peter. On 27 okt 2010, at 19:14, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Oct 27, 2010, at 5:51 PM, Tony Fleig wrote: > >> I am new to Pharo. This sounds like a change I would like to incorporate in my environment. >> >> I assume 12217 is an identifier of something that might allow me to do this, but what? Is there a noob document I should have read? >> > 12217 is the update number of version 1.2, which is the next unstable release. (To be beta end of the month). > > Now if you want to cherry-pick a fix for your own development image (which I guess is based on 1.1), > the other numbers are more important. > > The Issues are numbers of Google bug tracker entries. > > http://code.google.com/p/pharo/issues/list > > (of course this just shows the open ones). > > Of the three issues, just one makes sense in 1.1: 2797 > > http://code.google.com/p/pharo/issues/detail?id=2797 > > there you find the code and description of the change. > >> >> On Wed, Oct 27, 2010 at 1:28 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> >> Issue 3164: Fix find and seach all source >> Issue 1801: Rescue Sophie Undo framework >> Issue 2797: MIMEDocument class >> #guessTypeFromName: results in MNU >> > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 27, 2010

Re: [Pharo-project] Pharo sprint at Smalltalk 2010?

by StÃ©phane Ducasse

> Yes, I am in :-) Lukas I I'm quite sure that lot of people would like to pair program with you.

Oct. 27, 2010

Re: [Pharo-project] posting etiquette - please post new text at the *top* of your email

by Ramon Leon

On 10/27/2010 7:16 AM, Douglas Brebner wrote: > Or even better, cut out the irrelevant quoted text :) Yes please, as top posting is *not* good etiquette, but that's an old flame war. -- Ramon Leon http://onsmalltalk.com

Oct. 27, 2010

Re: [Pharo-project] Pharo sprint at Smalltalk 2010?

by StÃ©phane Ducasse

> +1000 > > Stef, > > is it ok to have Markus or someone else receiving Licence Agreements? Or must be sent to you? the way you want. Stef

Oct. 27, 2010

Re: [Pharo-project] [update 1.2] #12217

by Marcus Denker

On Oct 27, 2010, at 5:51 PM, Tony Fleig wrote: > I am new to Pharo. This sounds like a change I would like to incorporate in my environment. > > I assume 12217 is an identifier of something that might allow me to do this, but what? Is there a noob document I should have read? > 12217 is the update number of version 1.2, which is the next unstable release. (To be beta end of the month). Now if you want to cherry-pick a fix for your own development image (which I guess is based on 1.1), the other numbers are more important. The Issues are numbers of Google bug tracker entries. http://code.google.com/p/pharo/issues/list (of course this just shows the open ones). Of the three issues, just one makes sense in 1.1: 2797 http://code.google.com/p/pharo/issues/detail?id=2797 there you find the code and description of the change. > > On Wed, Oct 27, 2010 at 1:28 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > > Issue 3164: Fix find and seach all source > Issue 1801: Rescue Sophie Undo framework > Issue 2797: MIMEDocument class >> #guessTypeFromName: results in MNU > -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Oct. 27, 2010

Re: [Pharo-project] Pharo sprint at Smalltalk 2010?

by Marcus Denker

On Oct 27, 2010, at 5:41 PM, Francisco Ortiz PeÃ±aloza wrote: > +1000 > > Stef, > > is it ok to have Markus or someone else receiving Licence Agreements? Or must be sent to you? > I can take it, too. Marcus -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

Oct. 27, 2010

Re: [Pharo-project] [update 1.2] #12217

by Tony Fleig

I am new to Pharo. This sounds like a change I would like to incorporate in my environment. I assume 12217 is an identifier of something that might allow me to do this, but what? Is there a noob document I should have read? Thanks, TF On Wed, Oct 27, 2010 at 1:28 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > 12217 > ----- > > Issue 3164: Fix find and seach all source > Issue 1801: Rescue Sophie Undo framework > Issue 2797: MIMEDocument class >> #guessTypeFromName: results in MNU > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 27, 2010