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

[Pharo-project] Looking for ImageSegment tests

by StÃ©phane Ducasse

Hi all if by any chance you have some code that could be turned into tests, or some tests or some time to write tests for image segments this would be great because etoy is really deep inside image segment and I would really like to keep this beautiful idea working :) You see not everything is bad in Squeak :) Stef

Oct. 21, 2008

Re: [Pharo-project] OldSocket removal

by StÃ©phane Ducasse

please! On Oct 21, 2008, at 3:17 PM, Dan Corneanu wrote: > While playing with the OldSocket class>>clientServerTestUDP method I > found out that a call to Socket>>discardReceivedData is blocking and > this is not what happened with OldSocket>>discardReceivedData. An > extra test for available data is missing. > > I could help with moving the methods from OldSocket class examples to > a new SocketTest class. > > On Tue, Oct 21, 2008 at 10:14 AM, Damien Cassou <damien.cassou(a)gmail.com > > wrote: >> I've started working on OldSocket removal: >> http://code.google.com/p/pharo/issues/detail?id=275. I need someone >> to >> review my first changes. >> >> -- >> Damien Cassou >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> >> _______________________________________________ >> 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. 21, 2008

Re: [Pharo-project] PluggableMultiSelectList, ListStub (SUnitToolBuilder)

by StÃ©phane Ducasse

and thanks for your contribution. stef On Oct 21, 2008, at 3:24 PM, John Thornborrow wrote: > Hi, sorry for delay, I've just prepared the changes but before I > commit > to pharoinbox, how do I sign the agreement? Do I just add my name to > the > "Signed" section on the page? What is the "Pending" section for? > > Thanks, > John. > > StÃ©phane Ducasse wrote: >> thanks mike this is 100% correct >> >> On Oct 14, 2008, at 10:57 PM, Michael Roberts wrote: >> >>> http://code.google.com/p/pharo/wiki/HowToContribute >>> >>> which is roughly >>> 1) Sign the agreement 2) Check the issue tracker, you could also >>> check >>> Mantis 3) Create an entry on the issue tracker if you want to, >>> either >>> with a CS or reference to a SLICE in the PharoInbox, 4) discuss here >>> or watch what people comment on the tracker >> >> discussing it here is important >> >> Stef >>> >>> >>> cheers, >>> >>> Mike >>> >>> _______________________________________________ >>> 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 >> >> >> >> > > > ****************************************************************************************************************************************** > This email is from Pinesoft Limited. Its contents are confidential > to the intended recipient(s) at the email address(es) to which it > has been addressed. It may not be disclosed to or used by anyone > other than the addressee(s), nor may it be copied in anyway. If > received in error, please contact the sender, then delete it from > your system. Although this email and attachments are believed to be > free of virus, or any other defect which might affect any computer > or IT system into which they are received and opened, it is the > responsibility of the recipient to ensure that they are virus free > and no responsibility is accepted by Pinesoft for any loss or damage > arising in any way from receipt or use thereof. > ******************************************************************************************************************************************* > > > Pinesoft Limited are registered in England, Registered number: > 2914825. Registered office: 266-268 High Street, Waltham Cross, > Herts, EN8 7EA > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 21, 2008

Re: [Pharo-project] PluggableMultiSelectList, ListStub (SUnitToolBuilder)

by StÃ©phane Ducasse

Hi john if you can print, fill up and send to me either by fax or surface mail the following http://pharo.gforge.inria.fr/licenseDocuments/ Then this is ok normally just releasing to the PharoInBox makes sure that you release your changes under MIT. We collect the license agrreement in addition in case of. Stef On Oct 21, 2008, at 3:24 PM, John Thornborrow wrote: > Hi, sorry for delay, I've just prepared the changes but before I > commit > to pharoinbox, how do I sign the agreement? Do I just add my name to > the > "Signed" section on the page? What is the "Pending" section for? > > Thanks, > John. > > StÃ©phane Ducasse wrote: >> thanks mike this is 100% correct >> >> On Oct 14, 2008, at 10:57 PM, Michael Roberts wrote: >> >>> http://code.google.com/p/pharo/wiki/HowToContribute >>> >>> which is roughly >>> 1) Sign the agreement 2) Check the issue tracker, you could also >>> check >>> Mantis 3) Create an entry on the issue tracker if you want to, >>> either >>> with a CS or reference to a SLICE in the PharoInbox, 4) discuss here >>> or watch what people comment on the tracker >> >> discussing it here is important >> >> Stef >>> >>> >>> cheers, >>> >>> Mike >>> >>> _______________________________________________ >>> 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 >> >> >> >> > > > ****************************************************************************************************************************************** > This email is from Pinesoft Limited. Its contents are confidential > to the intended recipient(s) at the email address(es) to which it > has been addressed. It may not be disclosed to or used by anyone > other than the addressee(s), nor may it be copied in anyway. If > received in error, please contact the sender, then delete it from > your system. Although this email and attachments are believed to be > free of virus, or any other defect which might affect any computer > or IT system into which they are received and opened, it is the > responsibility of the recipient to ensure that they are virus free > and no responsibility is accepted by Pinesoft for any loss or damage > arising in any way from receipt or use thereof. > ******************************************************************************************************************************************* > > > Pinesoft Limited are registered in England, Registered number: > 2914825. Registered office: 266-268 High Street, Waltham Cross, > Herts, EN8 7EA > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 21, 2008

Re: [Pharo-project] 10095: questions

by StÃ©phane Ducasse

you have recover lost changes but I imagine that you can get back the one you miss. Stef On Oct 21, 2008, at 3:14 PM, Lukas Renggli wrote: > Another thing I missed in recent versions is the possibility to open a > changes-list on the recently logged changes. This is an absolutely > crucial feature for an image based system, to be able to restore after > a crash. > > Cheers, > Lukas > > On Tue, Oct 21, 2008 at 1:24 PM, Alexandre Bergel > <alexandre(a)bergel.eu> wrote: >> Excellent! >> >> Cheers, >> Alexandre >> >> >> On 21 Oct 2008, at 13:13, Damien Cassou wrote: >> >>> On Tue, Oct 21, 2008 at 1:02 PM, Alexandre Bergel >>> <Alexandre.Bergel(a)inria.fr> wrote: >>>> >>>> Why is there only a simple change browser. Why not the double >>>> one? I >>>> always >>>> found the simple one less useful. >>> >>> I think Adrian is aware of that and will replace the single one by >>> the >>> double one. In the meantime, you can still: DualChangeSorter open >>> >>>> How can I update Pharo ? Before the 'load update' in the left- >>>> hand flap >>>> provided it. >>> >>> World menu->system->uptade >>> >>> -- >>> Damien Cassou >>> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >>> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >>> _______________________________________________ >>> 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 >> > > > > -- > Lukas Renggli > http://www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 21, 2008

Re: [Pharo-project] OldSocket removal

by Damien Cassou

On Tue, Oct 21, 2008 at 3:17 PM, Dan Corneanu <dan.corneanu(a)gmail.com> wrote: > While playing with the OldSocket class>>clientServerTestUDP method I > found out that a call to Socket>>discardReceivedData is blocking and > this is not what happened with OldSocket>>discardReceivedData. An > extra test for available data is missing. > > I could help with moving the methods from OldSocket class examples to > a new SocketTest class. Pleqse -- Damien Cassou Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu)

Oct. 21, 2008

Re: [Pharo-project] PluggableMultiSelectList, ListStub (SUnitToolBuilder)

by John Thornborrow

Hi, sorry for delay, I've just prepared the changes but before I commit to pharoinbox, how do I sign the agreement? Do I just add my name to the "Signed" section on the page? What is the "Pending" section for? Thanks, John. StÃ©phane Ducasse wrote: > thanks mike this is 100% correct > > On Oct 14, 2008, at 10:57 PM, Michael Roberts wrote: > >> http://code.google.com/p/pharo/wiki/HowToContribute >> >> which is roughly >> 1) Sign the agreement 2) Check the issue tracker, you could also check >> Mantis 3) Create an entry on the issue tracker if you want to, either >> with a CS or reference to a SLICE in the PharoInbox, 4) discuss here >> or watch what people comment on the tracker > > discussing it here is important > > Stef >> >> >> cheers, >> >> Mike >> >> _______________________________________________ >> 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 > > > > ****************************************************************************************************************************************** This email is from Pinesoft Limited. Its contents are confidential to the intended recipient(s) at the email address(es) to which it has been addressed. It may not be disclosed to or used by anyone other than the addressee(s), nor may it be copied in anyway. If received in error, please contact the sender, then delete it from your system. Although this email and attachments are believed to be free of virus, or any other defect which might affect any computer or IT system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by Pinesoft for any loss or damage arising in any way from receipt or use thereof. ******************************************************************************************************************************************* Pinesoft Limited are registered in England, Registered number: 2914825. Registered office: 266-268 High Street, Waltham Cross, Herts, EN8 7EA

Oct. 21, 2008

Re: [Pharo-project] squeak sites not available

by Lukas Renggli

>> The server was already down in September and the box admins started to >> search for an explanation - see [1] > > No of course not. > And this is not our goal to see squeak dead. > I think that lukas was just pissed of. I don't wish it dead either. It just makes a very strange impression to anybody, if a server is away for such a long time. Unfortunately we depend on the infrastructure for the Seaside mailing-lists and we desperately need these lists. We were doing a Seaside sprint over the weekend and this was very hard as mailing-list communication was (and is still) blocked. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 21, 2008

Re: [Pharo-project] OldSocket removal

by Dan Corneanu

While playing with the OldSocket class>>clientServerTestUDP method I found out that a call to Socket>>discardReceivedData is blocking and this is not what happened with OldSocket>>discardReceivedData. An extra test for available data is missing. I could help with moving the methods from OldSocket class examples to a new SocketTest class. On Tue, Oct 21, 2008 at 10:14 AM, Damien Cassou <damien.cassou(a)gmail.com> wrote: > I've started working on OldSocket removal: > http://code.google.com/p/pharo/issues/detail?id=275. I need someone to > review my first changes. > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

Oct. 21, 2008

Re: [Pharo-project] 10095: questions

by Lukas Renggli

Another thing I missed in recent versions is the possibility to open a changes-list on the recently logged changes. This is an absolutely crucial feature for an image based system, to be able to restore after a crash. Cheers, Lukas On Tue, Oct 21, 2008 at 1:24 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > Excellent! > > Cheers, > Alexandre > > > On 21 Oct 2008, at 13:13, Damien Cassou wrote: > >> On Tue, Oct 21, 2008 at 1:02 PM, Alexandre Bergel >> <Alexandre.Bergel(a)inria.fr> wrote: >>> >>> Why is there only a simple change browser. Why not the double one? I >>> always >>> found the simple one less useful. >> >> I think Adrian is aware of that and will replace the single one by the >> double one. In the meantime, you can still: DualChangeSorter open >> >>> How can I update Pharo ? Before the 'load update' in the left-hand flap >>> provided it. >> >> World menu->system->uptade >> >> -- >> Damien Cassou >> Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good >> luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) >> _______________________________________________ >> 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 > -- Lukas Renggli http://www.lukas-renggli.ch

Oct. 21, 2008