June 2011 - Pharo-users - lists.pharo.org

Re: [Pharo-users] [COTDC] 72 - TMorphTreeModel

by Alain Plantec

I define the basic behaviors of a MorphTreeMorph model. The main intention is not clear at all. In fact this trait is not useful and all its methods should be directly added in MorphTreeModel. Alain Le 14/06/2011 19:42, laurent laffont a Ã©crit : > > On Wed, Jun 8, 2011 at 10:14 PM, laurent laffont > <laurent.laffont(a)gmail.com <mailto:laurent.laffont@gmail.com>> wrote: > > Today: TMorphTreeModel > > > > I define basic behaviors that every Model for a TreeMorph would > implements. ? > > Not sure about the main intention behind that.... > > IMO messages like #selection, #chunkSize should be added like: > > chunkSize > self explicitRequirement. > > Laurent. > > > > > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best > comment will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent > >

June 14, 2011

Re: [Pharo-users] [COTDC] 72 - TMorphTreeModel

by laurent laffont

On Wed, Jun 8, 2011 at 10:14 PM, laurent laffont <laurent.laffont(a)gmail.com>wrote: > Today: TMorphTreeModel > I define basic behaviors that every Model for a TreeMorph would implements. ? Not sure about the main intention behind that.... IMO messages like #selection, #chunkSize should be added like: chunkSize self explicitRequirement. Laurent. > Comment Of The Day Contest - One Day One Comment > Rules: > #1: Each day a not commented class is elected. Each day the best comment > will be integrated with name of the author(s). > #2: If you cannot comment it, deprecate it. > Results: http://code.google.com/p/pharo/wiki/CommentOfTheDayContest > > Laurent >

June 14, 2011

Re: [Pharo-users] Change an existing method from another project

by Marcus Denker

On Jun 14, 2011, at 9:41 AM, laurent laffont wrote: > On Tue, Jun 14, 2011 at 9:33 AM, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On Jun 14, 2011, at 9:30 AM, laurent laffont wrote: > > > On Tue, Jun 14, 2011 at 9:06 AM, Miguel Moquillon <miguel.moquillon(a)gmail.com> wrote: > > Le 13/06/2011 17:57, StÃ©phane Ducasse a Ã©crit : > > > > > > On Jun 13, 2011, at 9:09 AM, Miguel Moquillon wrote: > > > > Ok, > > > > I will extend SUnit to integrate my extensions. > > (It is unfortunate because there is just only one or two methods to change.) > > > > so be ready that your code will not work when the next version of Sunit show up. > > I really think that this is better to fork one version where we can do what we want. > > Thus I have two possible solutions: > > - provide a direct contribution to the SUnit project with my code, > > - or fork SUnit to a new project (PharoUnit?) so that anybody can enhance the unit test framework for Pharo. > > > > In fact, I don't know if the Pragma implementation in Pharo is specific to the Squeak/Pharo smalltalk dialect. In that case, I think it would be better to fork SUnit as my changes will be based upon pragmas. > > > > > > Indeed http://squeaksource.com/SUnit is global Read / Write, creator/admin = Marcus Denker, so I suppose you can submit a package/branch in this repo safely. > > > But keep in mind that the SUnit from Pharo is not regularly saved there... maybe it should? But than, without automatisation this is too much work. > > ok. Miguel, the right process may be: > - fork SUnit in your own repo. You can use the existing repo for that... no problem. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 14, 2011

Re: [Pharo-users] Change an existing method from another project

by laurent laffont

On Tue, Jun 14, 2011 at 9:33 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On Jun 14, 2011, at 9:30 AM, laurent laffont wrote: > > > On Tue, Jun 14, 2011 at 9:06 AM, Miguel Moquillon < > miguel.moquillon(a)gmail.com> wrote: > > Le 13/06/2011 17:57, StÃ©phane Ducasse a Ã©crit : > > > > > > On Jun 13, 2011, at 9:09 AM, Miguel Moquillon wrote: > > > > Ok, > > > > I will extend SUnit to integrate my extensions. > > (It is unfortunate because there is just only one or two methods to > change.) > > > > so be ready that your code will not work when the next version of Sunit > show up. > > I really think that this is better to fork one version where we can do > what we want. > > Thus I have two possible solutions: > > - provide a direct contribution to the SUnit project with my code, > > - or fork SUnit to a new project (PharoUnit?) so that anybody can enhance > the unit test framework for Pharo. > > > > In fact, I don't know if the Pragma implementation in Pharo is specific > to the Squeak/Pharo smalltalk dialect. In that case, I think it would be > better to fork SUnit as my changes will be based upon pragmas. > > > > > > Indeed http://squeaksource.com/SUnit is global Read / Write, > creator/admin = Marcus Denker, so I suppose you can submit a package/branch > in this repo safely. > > > But keep in mind that the SUnit from Pharo is not regularly saved there... > maybe it should? But than, without automatisation this is too much work. > ok. Miguel, the right process may be: - fork SUnit in your own repo. - develop - once satisfied - open an issue - merge your SUnit in PharoCore - submit the slice in PharoInbox ? Laurent > > > -- > Marcus Denker -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > >

June 14, 2011

Re: [Pharo-users] Change an existing method from another project

by Marcus Denker

On Jun 14, 2011, at 9:30 AM, laurent laffont wrote: > On Tue, Jun 14, 2011 at 9:06 AM, Miguel Moquillon <miguel.moquillon(a)gmail.com> wrote: > Le 13/06/2011 17:57, StÃ©phane Ducasse a Ã©crit : > > > On Jun 13, 2011, at 9:09 AM, Miguel Moquillon wrote: > > Ok, > > I will extend SUnit to integrate my extensions. > (It is unfortunate because there is just only one or two methods to change.) > > so be ready that your code will not work when the next version of Sunit show up. > I really think that this is better to fork one version where we can do what we want. > Thus I have two possible solutions: > - provide a direct contribution to the SUnit project with my code, > - or fork SUnit to a new project (PharoUnit?) so that anybody can enhance the unit test framework for Pharo. > > In fact, I don't know if the Pragma implementation in Pharo is specific to the Squeak/Pharo smalltalk dialect. In that case, I think it would be better to fork SUnit as my changes will be based upon pragmas. > > > Indeed http://squeaksource.com/SUnit is global Read / Write, creator/admin = Marcus Denker, so I suppose you can submit a package/branch in this repo safely. > But keep in mind that the SUnit from Pharo is not regularly saved there... maybe it should? But than, without automatisation this is too much work. -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 14, 2011

Re: [Pharo-users] Change an existing method from another project

by laurent laffont

On Tue, Jun 14, 2011 at 9:06 AM, Miguel Moquillon < miguel.moquillon(a)gmail.com> wrote: > Le 13/06/2011 17:57, StÃ©phane Ducasse a Ã©crit : > > >> On Jun 13, 2011, at 9:09 AM, Miguel Moquillon wrote: >> >> Ok, >>> >>> I will extend SUnit to integrate my extensions. >>> (It is unfortunate because there is just only one or two methods to >>> change.) >>> >> >> so be ready that your code will not work when the next version of Sunit >> show up. >> I really think that this is better to fork one version where we can do >> what we want. >> > Thus I have two possible solutions: > - provide a direct contribution to the SUnit project with my code, > - or fork SUnit to a new project (PharoUnit?) so that anybody can enhance > the unit test framework for Pharo. > > In fact, I don't know if the Pragma implementation in Pharo is specific to > the Squeak/Pharo smalltalk dialect. In that case, I think it would be better > to fork SUnit as my changes will be based upon pragmas. > > Indeed http://squeaksource.com/SUnit is global Read / Write, creator/admin = Marcus Denker, so I suppose you can submit a package/branch in this repo safely. Laurent > Mig > >

June 14, 2011

Re: [Pharo-users] Change an existing method from another project

by Miguel Moquillon

Le 13/06/2011 17:57, StÃ©phane Ducasse a Ã©crit : > > On Jun 13, 2011, at 9:09 AM, Miguel Moquillon wrote: > >> Ok, >> >> I will extend SUnit to integrate my extensions. >> (It is unfortunate because there is just only one or two methods to change.) > > so be ready that your code will not work when the next version of Sunit show up. > I really think that this is better to fork one version where we can do what we want. Thus I have two possible solutions: - provide a direct contribution to the SUnit project with my code, - or fork SUnit to a new project (PharoUnit?) so that anybody can enhance the unit test framework for Pharo. In fact, I don't know if the Pragma implementation in Pharo is specific to the Squeak/Pharo smalltalk dialect. In that case, I think it would be better to fork SUnit as my changes will be based upon pragmas. Mig

June 14, 2011

Re: [Pharo-users] Change an existing method from another project

by StÃ©phane Ducasse

On Jun 13, 2011, at 9:09 AM, Miguel Moquillon wrote: > Ok, > > I will extend SUnit to integrate my extensions. > (It is unfortunate because there is just only one or two methods to change.) so be ready that your code will not work when the next version of Sunit show up. I really think that this is better to fork one version where we can do what we want. Stef > > Le 11/06/2011 19:17, StÃ©phane Ducasse a Ã©crit : >> Miguel >> >> please do the following: >> - Fork and copy and past SUnit and extend it >> - In the past I modified SUnit and after people complained that it was not the right version and my extensions got >> lost when we reloaded the latest version of SUnit. >> So let us invent some new way to write tests :). >> >> Stef >> >> >>> Hi, >>> >>> I'm going to provide a new way to write unit tests without having prefixed test methods with the word 'test'. As I don't want to write another unit test framework, I need to change some methods of SUnit (as well of Autotest). >>> Is there any way to do that from an external project without creating a specific fork of theses projects? >>> >>> Mig >>> >> >> > >

June 13, 2011

Job offer in Luxembourg

by StÃ©phane Ducasse

Hi guys There is a job offer in Luxembourg. Please contact hayley directly. I hope that this will help you. Position: C++ Developer with Smalltalk Term: 3 Months extendable Location: Luxembourg Rate: Negotiable C++ Smalltalk Developer my client a leading banking institution is looking for a C++ Smalltalk Developer with good knowledge of SQL. You will be asked to help develop the technical design, coding, unit testing for a number of projects within the bank. This will be a long term contract. Stef

June 13, 2011

Re: [Pharo-users] Change an existing method from another project

by laurent laffont

On Mon, Jun 13, 2011 at 9:09 AM, Miguel Moquillon < miguel.moquillon(a)gmail.com> wrote: > Ok, > > I will extend SUnit to integrate my extensions. > (It is unfortunate because there is just only one or two methods to > change.) > Or just open an issue and publish a slice. Laurent. > > Le 11/06/2011 19:17, StÃ©phane Ducasse a Ã©crit : > > Miguel >> >> please do the following: >> - Fork and copy and past SUnit and extend it >> - In the past I modified SUnit and after people complained that it >> was not the right version and my extensions got >> lost when we reloaded the latest version of SUnit. >> So let us invent some new way to write tests :). >> >> Stef >> >> >> Hi, >>> >>> I'm going to provide a new way to write unit tests without having >>> prefixed test methods with the word 'test'. As I don't want to write another >>> unit test framework, I need to change some methods of SUnit (as well of >>> Autotest). >>> Is there any way to do that from an external project without creating a >>> specific fork of theses projects? >>> >>> Mig >>> >>> >> >> > >

June 13, 2011