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

[Pharo-project] source.lukas-renggli.ch is down

by laurent laffont

So ConfigurationOfPharo / ConfigurationOfOmniBrowser fail :( Laurent

Dec. 28, 2010

Re: [Pharo-project] Pharo 1.2 - default packages

by Mariano Martinez Peck

On Tue, Dec 28, 2010 at 6:24 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > OK. I'm working on it now. > > Should I update beta2 or create beta3 ? > > As you wish. We are still in development and we are free to do what you want. I would use beta2 still :) Remember that you can do this by yourself and see if works: "Dev image" Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. (Smalltalk at: #ConfigurationOfPharo) project lastVersion load I'm also adding Shortcuts-Help. > > Excellent!! > Laurent > > > On Tue, Dec 28, 2010 at 2:20 PM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Ahh Laurent, don't forget to add those projects also to the group: 'Dev >> Tools' in ConfigurationOfPharo >> >> Cheers >> >> Mariano >> >> >> >> On Tue, Dec 28, 2010 at 11:28 AM, Mariano Martinez Peck < >> marianopeck(a)gmail.com> wrote: >> >>> >>> >>> On Mon, Dec 27, 2010 at 12:45 PM, laurent laffont < >>> laurent.laffont(a)gmail.com> wrote: >>> >>>> On Sun, Dec 26, 2010 at 10:59 PM, Mariano Martinez Peck < >>>> marianopeck(a)gmail.com> wrote: >>>> >>>>> >>>>> >>>>> On Fri, Dec 17, 2010 at 9:04 AM, laurent laffont < >>>>> laurent.laffont(a)gmail.com> wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> >>>>>> What do you think about adding these packages as default in Pharo 1.2: >>>>>> - ConfigurationOfMocketry >>>>>> - ConfigurationOfXMLSupport >>>>>> - ConfigurationOfCryptography (does'nt exist yet, planned to be >>>>>> created in a local coding-dojo on Tuesday). >>>>>> >>>>>> Motivations: >>>>>> - XMLSupport and Cryptography are often needed to consume web services >>>>>> - Mocketry because I want to write tests using Mocks and it's easier >>>>>> to work when tools are in standard Pharo (and then newcomers can see >>>>>> Mocketry examples). >>>>>> >>>>>> >>>>>> I will update ConfigurationOfPharo 1.2 (beta3 ?) if people agree. >>>>>> >>>>>> >>>>> Hi Laurent. I agree it would be nice to include those 3 projects in >>>>> PharoDev. Do they have tests? are they all green in pharo 1.2? >>>>> >>>> >>>> >>>> - ConfigurationOfMocketry has 479 tests, all green now in Pharo 1.2 + >>>> HelpSystem help. >>>> - ConfigurationOfXMLSupport version: '1.0.2' has 32 tests, all green >>>> (but blessing is #development so I don't know if we can include it). version >>>> 1.0.0 has 8 tests, green. >>>> - ConfigurationOfAutotest: 27 tests green + HelpSystem help. >>>> >>>> >>> Hi Laurent. I think both kind of tools are important for doing business >>> in Pharo: test and XML support. Both have been asked several times in the >>> mailing list. Having them in the dev image would be easier for this point of >>> view, and users can help detecting bugs, using it, etc. >>> >>> I would include those 3 projects in the PharoDev. So, go ahead and add it >>> in ConfigurationOfPharo. We can always go back. >>> >>> For Autotest, what I suggest is to have it in the image, but not enable >>> by default. THose who want to use it, just open the settings browser and >>> enable it. >>> >>> >>>> For Cryptography I've started to look at it but there's some work to be >>>> done: there's only one packages with all algorithms + tests + core. So it >>>> should be splitted. You are right about MD5 (splitting should resolve this). >>>> Actually 10 tests out of 102 fail. >>>> >>>> >>> For the Cryptography I would wait a bit, as you say. Because in pharo >>> core we already have the package System-Hashing ... so I am not sure how to >>> deal with it. >>> >>> Cheers >>> >>> Mariano >>> >>> >>>> Laurent >>>> >>>> >>>> >>>> >>>> >>>>> >>>>> If true, and people agree, please feel free to update >>>>> ConfigurationOfPharo >>>>> >>>>> I didn't check ConfigurationOfCryptography but I remember that MD5 and >>>>> few other classes where already integrated in PharoCore. We should avoid >>>>> collisions. Are those classes still alive in the Cryptography package? >>>>> >>>>> cheers >>>>> >>>>> mariano >>>>> >>>>> >>>>>> Cheers, >>>>>> >>>>>> Laurent Laffont >>>>>> >>>>> >>>>> >>>> >>> >> >

Dec. 28, 2010

Re: [Pharo-project] Pharo 1.2 - default packages

by laurent laffont

OK. I'm working on it now. Should I update beta2 or create beta3 ? I'm also adding Shortcuts-Help. Laurent On Tue, Dec 28, 2010 at 2:20 PM, Mariano Martinez Peck < marianopeck(a)gmail.com> wrote: > Ahh Laurent, don't forget to add those projects also to the group: 'Dev > Tools' in ConfigurationOfPharo > > Cheers > > Mariano > > > > On Tue, Dec 28, 2010 at 11:28 AM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> >> >> On Mon, Dec 27, 2010 at 12:45 PM, laurent laffont < >> laurent.laffont(a)gmail.com> wrote: >> >>> On Sun, Dec 26, 2010 at 10:59 PM, Mariano Martinez Peck < >>> marianopeck(a)gmail.com> wrote: >>> >>>> >>>> >>>> On Fri, Dec 17, 2010 at 9:04 AM, laurent laffont < >>>> laurent.laffont(a)gmail.com> wrote: >>>> >>>>> Hi, >>>>> >>>>> >>>>> What do you think about adding these packages as default in Pharo 1.2: >>>>> - ConfigurationOfMocketry >>>>> - ConfigurationOfXMLSupport >>>>> - ConfigurationOfCryptography (does'nt exist yet, planned to be >>>>> created in a local coding-dojo on Tuesday). >>>>> >>>>> Motivations: >>>>> - XMLSupport and Cryptography are often needed to consume web services >>>>> - Mocketry because I want to write tests using Mocks and it's easier to >>>>> work when tools are in standard Pharo (and then newcomers can see Mocketry >>>>> examples). >>>>> >>>>> >>>>> I will update ConfigurationOfPharo 1.2 (beta3 ?) if people agree. >>>>> >>>>> >>>> Hi Laurent. I agree it would be nice to include those 3 projects in >>>> PharoDev. Do they have tests? are they all green in pharo 1.2? >>>> >>> >>> >>> - ConfigurationOfMocketry has 479 tests, all green now in Pharo 1.2 + >>> HelpSystem help. >>> - ConfigurationOfXMLSupport version: '1.0.2' has 32 tests, all green (but >>> blessing is #development so I don't know if we can include it). version >>> 1.0.0 has 8 tests, green. >>> - ConfigurationOfAutotest: 27 tests green + HelpSystem help. >>> >>> >> Hi Laurent. I think both kind of tools are important for doing business in >> Pharo: test and XML support. Both have been asked several times in the >> mailing list. Having them in the dev image would be easier for this point of >> view, and users can help detecting bugs, using it, etc. >> >> I would include those 3 projects in the PharoDev. So, go ahead and add it >> in ConfigurationOfPharo. We can always go back. >> >> For Autotest, what I suggest is to have it in the image, but not enable by >> default. THose who want to use it, just open the settings browser and enable >> it. >> >> >>> For Cryptography I've started to look at it but there's some work to be >>> done: there's only one packages with all algorithms + tests + core. So it >>> should be splitted. You are right about MD5 (splitting should resolve this). >>> Actually 10 tests out of 102 fail. >>> >>> >> For the Cryptography I would wait a bit, as you say. Because in pharo >> core we already have the package System-Hashing ... so I am not sure how to >> deal with it. >> >> Cheers >> >> Mariano >> >> >>> Laurent >>> >>> >>> >>> >>> >>>> >>>> If true, and people agree, please feel free to update >>>> ConfigurationOfPharo >>>> >>>> I didn't check ConfigurationOfCryptography but I remember that MD5 and >>>> few other classes where already integrated in PharoCore. We should avoid >>>> collisions. Are those classes still alive in the Cryptography package? >>>> >>>> cheers >>>> >>>> mariano >>>> >>>> >>>>> Cheers, >>>>> >>>>> Laurent Laffont >>>>> >>>> >>>> >>> >> >

Dec. 28, 2010

Re: [Pharo-project] Issue 3224 in pharo: Migrating MethodReference to MethodReferenceWithSource

by pharo＠googlecode.com

Comment #8 on issue 3224 by stephane.ducasse: Migrating MethodReference to MethodReferenceWithSource http://code.google.com/p/pharo/issues/detail?id=3224 The problem is that MethodReference was also used to just be an object that represent a class name and a selector. In addition it was also used to wrap a compiledMethod and as such a compiledMethod got a sourcePointer (I image).

Dec. 28, 2010

Re: [Pharo-project] Issue 3224 in pharo: Migrating MethodReference to MethodReferenceWithSource

by pharo＠googlecode.com

Comment #7 on issue 3224 by stephane.ducasse: Migrating MethodReference to MethodReferenceWithSource http://code.google.com/p/pharo/issues/detail?id=3224 The problem is that MethodReference was also used to just be an object that represent a class name and a selector. In addition it was also used to wrap a compiledMethod and as such a compiledMethod got a sourcePointer (I image).

Dec. 28, 2010

Re: [Pharo-project] Issue 3486 in pharo: RecentMessageList problem with PluggableTextMorph

by pharo＠googlecode.com

Comment #5 on issue 3486 by Benjamin.VanRyseghem.Pharo: RecentMessageList problem with PluggableTextMorph http://code.google.com/p/pharo/issues/detail?id=3486 It's long because there is the packages STStyler80 and STParser, but I do not remember if I have done some changes in it or if it was just for tests â¦

Dec. 28, 2010

Re: [Pharo-project] Issue 3414 in pharo: CompilerEvaluationTest>>#testEvaluationOfSelfSend fails

by pharo＠googlecode.com

Comment #2 on issue 3414 by stephane.ducasse: CompilerEvaluationTest>>#testEvaluationOfSelfSend fails http://code.google.com/p/pharo/issues/detail?id=3414 I need help on this one because I got completely confused. So I probably missed something obvious.

Dec. 28, 2010

Re: [Pharo-project] Issue 3414 in pharo: CompilerEvaluationTest>>#testEvaluationOfSelfSend fails

by pharo＠googlecode.com

Comment #1 on issue 3414 by stephane.ducasse: CompilerEvaluationTest>>#testEvaluationOfSelfSend fails http://code.google.com/p/pharo/issues/detail?id=3414 I need help on this one because I got completely confused. So I probably missed something obvious.

Dec. 28, 2010

Re: [Pharo-project] Issue 3458 in pharo: bug in the class MultiByteFileStream when Pharo running under Windows

by pharo＠googlecode.com

Comment #3 on issue 3458 by stephane.ducasse: bug in the class MultiByteFileStream when Pharo running under Windows http://code.google.com/p/pharo/issues/detail?id=3458 Could somebody with a Windows confirm and provide a changeset?

Dec. 28, 2010

Re: [Pharo-project] Issue 3458 in pharo: bug in the class MultiByteFileStream when Pharo running under Windows

by pharo＠googlecode.com

Comment #2 on issue 3458 by stephane.ducasse: bug in the class MultiByteFileStream when Pharo running under Windows http://code.google.com/p/pharo/issues/detail?id=3458 Could somebody with a Windows confirm and provide a changeset?

Dec. 28, 2010