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

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

by Adrian Lienhard

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 > <tamackinnon(a)gmail.com> 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

Dec. 8, 2009

[Pharo-project] [ANN] pre-built 1.1#11078

by Marcus Denker

http://gforge.inria.fr/frs/download.php/24983/PharoCore-1.1-11078-alpha.zip Marcus

Dec. 8, 2009

Re: [Pharo-project] TheWorldMainDockingBar

by Adrian Lienhard

+1 On Dec 8, 2009, at 09:17 , Marcus Denker wrote: > > On Dec 8, 2009, at 9:10 AM, alain.plantec(a)free.fr wrote: > >> Hi all, >> While migrating a preference for it I noticed that >> at least, it is not very well integrated in pharo... >> Before I open an issue (if none already opened) I would like to >> know what >> people think about it. >> Personally I would not be very sad to see it killed :) > > I would say kill it. > > Marcus > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 8, 2009

Re: [Pharo-project] Issue 1554

by Adrian Lienhard

Hi Danny, Thanks for your contribution. Your change is in the package Ocompletion, which is outside Pharo- core. This package is maintained by Romain. I added Romain to CC so he can merge your fix into the main branch of Ocompletion. Cheers, Adrian On Dec 8, 2009, at 09:09 , Danny Chan wrote: > Hi! > > I just uploaded my first fix (or so I hope) for Pharo to the Inbox as > Ocompletion-DannyChan.44, following the instructions on the wiki for > contributions. > > When selecting a text in a workspace including the first character in > the window and hitting backspace, an exception will be thrown by > ocompletion, because the smartBackspace method will try to look at the > character before the current position of the caret, which is 0 in this > case. > > The instructions on the wiki say to put the status of the bug report > to > fixed, but I saw no way to do this. Did I miss something? > > By the way, I want to thank all of you for the great work you put into > Pharo. I am no software developer myself, but I really hope to be able > to use it for all the little tools I need all the time at work. > > Danny > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 8, 2009

Re: [Pharo-project] Scriptloader class>>loadFFI

by Mariano Martinez Peck

On Tue, Dec 8, 2009 at 12:44 AM, David T. Lewis <lewis(a)mail.msen.com> wrote: > On Mon, Dec 07, 2009 at 11:31:01PM +0100, Mariano Martinez Peck wrote: > > This is wrong. It is FFI-Pools not FFI-Pool. But I am sure I tested > > it. So, it seems > > Andreas has changed it again. So, it must be: > > > > ScriptLoader>>loadFFI > > self new installer monticello http: 'source.squeakfoundation.org'; > > project: 'FFI'; > > install: 'FFI-Pools'; > > install: 'FFI-Kernel'; > > install: 'FFI-Tests'; > > install: 'FFI-Examples'. > > (Smalltalk at: #ExternalType) initialize. > > (Smalltalk at: #ExternalStructure) compileAllFields. > > Smalltalk recreateSpecialObjectsArray. > > FYI, Andreas did not change it again. The change was only made once, and > the > reason was to allow the FFI pools to be a separate package that could be > loaded into VMMaker without requiring all the rest of FFI. > Weird....I am sure I tested with FFI-Pool and in addition most people put the fix with FFI-Pool. But now that package does not exists, and it is FFI-Pools. But anyway, I am not saying Andres is guilty. I am in favor of the continuous refactor :) > > I did something similar when I put Speech on SqueakSource, so we can have > only the necessary dependencies for VMMaker. Near term it is confusing to > change packages, but gradually we are getting more modular :) > > Excellent!! I totally agree with you :) > Dave > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Dec. 8, 2009

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

by Damien Cassou

Hi Tim, On Tue, Dec 8, 2009 at 12:51 AM, Tim Mackinnon <tamackinnon(a)gmail.com> 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

Dec. 8, 2009

Re: [Pharo-project] Issue 1551: possible to create 2 ByteSymbols with the same sequence of characters( WAS: getting rid of Symbol >> new: ?)

by Adrian Lienhard

I added you as a project committer. Cheers, Adrian On Dec 7, 2009, at 22:55 , Sheridan Mahoney wrote: > > The address for my Google account is: > > smagooey(a)yahoo.com > > I just sent Stef an email attachment with the license agreement, and > will be > putting a hard copy in the mail. > > Cheers, > Sheri > > > > Adrian Lienhard wrote: >> >> Hi Sheri, >> >> Thanks for the contribution! >> >> Please send me the mail address you use for the Google account. I'll >> add you to the list of developers. >> >> BTW, have you signed the license agreement? >> >> Cheers, >> Adrian >> >> >> On Dec 7, 2009, at 21:14 , Sheridan Mahoney wrote: >> >>> >>> and, forgot to mention, I did an image check, and did not find any >>> uses of >>> Symbol >> new: once we changed Symbol >> intern: . >>> >>> Also, does something need to be enabled in order to be able to >>> modify the >>> description fields in the issue tracker? Not having much luck in my >>> searches... >> >>> Thanks, >>> Sheri >>> >>> >>> >>> Sheridan Mahoney wrote: >>>> >>>> This is just to let the people of the list know I have reported the >>>> above >>>> bug (Issue 1551) and >>>> submitted a fix and tests to PharoInbox. It is called: >>>> SLICE-disallow-Symbol-new-SheridanMahoney.2 >>>> >>>> I didn't see a way to change the status to "Fixed", so it is just >>>> listed >>>> as "New". >>>> >>>> Cheers, >>>> Sheri >>>> >>>> >>>> >>>> Adrian Lienhard wrote: >>>>> >>>>> Hi Sheri, >>>>> >>>>> Sounds ok to make new: raise an exception if you adjust the tests >>>>> (and >>>>> any code that exists in the image using new: (but I assume there >>>>> is >>>>> none)). >>>>> >>>>> >>>> >>>> >>> >>> -- >>> View this message in context: >>> http://n2.nabble.com/Re-getting-rid-of-Symbol-new-tp4109230p4128207.html >>> Sent from the Pharo Smalltalk mailing list archive at Nabble.com. >>> >>> _______________________________________________ >>> 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/Re-getting-rid-of-Symbol-new-tp4109230p4128749.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Dec. 8, 2009

Re: [Pharo-project] TheWorldMainDockingBar

by Marcus Denker

On Dec 8, 2009, at 9:10 AM, alain.plantec(a)free.fr wrote: > Hi all, > While migrating a preference for it I noticed that > at least, it is not very well integrated in pharo... > Before I open an issue (if none already opened) I would like to know what > people think about it. > Personally I would not be very sad to see it killed :) I would say kill it. Marcus

Dec. 8, 2009

[Pharo-project] TheWorldMainDockingBar

by alain.plantec＠free.fr

Hi all, While migrating a preference for it I noticed that at least, it is not very well integrated in pharo... Before I open an issue (if none already opened) I would like to know what people think about it. Personally I would not be very sad to see it killed :) Thanks Alain

Dec. 8, 2009

[Pharo-project] Issue 1554

by Danny Chan

Hi! I just uploaded my first fix (or so I hope) for Pharo to the Inbox as Ocompletion-DannyChan.44, following the instructions on the wiki for contributions. When selecting a text in a workspace including the first character in the window and hitting backspace, an exception will be thrown by ocompletion, because the smartBackspace method will try to look at the character before the current position of the caret, which is 0 in this case. The instructions on the wiki say to put the status of the bug report to fixed, but I saw no way to do this. Did I miss something? By the way, I want to thank all of you for the great work you put into Pharo. I am no software developer myself, but I really hope to be able to use it for all the little tools I need all the time at work. Danny

Dec. 8, 2009