- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Pharo sprint at Smalltalk 2010?
by StÃ©phane Ducasse Oct. 27, 2010

Oct. 27, 2010

Yes! I suggested that to marcus yesterday. So take initiatives and have fun. Stef On Oct 27, 2010, at 1:08 PM, Esteban Lorenzano wrote: > Hi, > I wonder if a pharo sprint could be possible at Smalltalks 2010. > If there are people (more than me), interested, I can contact Smalltalks 2010 organizers in order to get a place/horary for it. > > Cheers, > Esteban > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] Delay when I upload to Squeaksource 2MB files size
by nullPointer Oct. 27, 2010

Oct. 27, 2010

Seems upload correctly, but when the progress bar is almost ended seems much more slow... Regards. -- View this message in context: http://forum.world.st/Delay-when-I-upload-to-Squeaksource-2MB-files-size-tp… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

4 3

Re: [Pharo-project] posting etiquette - please post new text at the *top* of your email
by StÃ©phane Ducasse Oct. 27, 2010

Oct. 27, 2010

+ 1 > Hi Folks, > > It is really hard keeping up with the deluge of email on this list. It is even harder if you have to search through posts to find the actual new text buried in all the quoted stuff. > > Unless there is a very good reason to provide the context, please add your new text *before* any quoted material. > > Thanks a bunch.

1 0

Re: [Pharo-project] OCompletion doesn't work in Pharo 1.2 because of Preferences delete
by StÃ©phane Ducasse Oct. 27, 2010

Oct. 27, 2010

thanks! On Oct 27, 2010, at 3:52 AM, Levente Uzonyi wrote: > On Tue, 26 Oct 2010, Mariano Martinez Peck wrote: > >> HI Ramain (or someone with time). >> >> OCompletion does not work anymore in Pharo 1.2 because of the Preferences >> removal. It would be nice if you could update it to use the new settings >> framework. > > Ocompletion-ul.74 should work in both Pharo 1.1 and 1.2. After loading the package evaluate [ECToolSet register]. > > > Levente > >> >> There is information here: >> http://book.pharo-project.org/book/CustomizingPharo/DeclaringSetting/ >> >> Thanks >> >> mariano >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: [Pharo-project] akuhn/SUnit: run faster tests first & step through tests
by StÃ©phane Ducasse Oct. 27, 2010

Oct. 27, 2010

On Oct 25, 2010, at 10:12 AM, Niko Schwarz wrote: > Couldn't Adrian be the maintainer? I could step in, too. yes but it means being present and reactive. > I don't really know what you have in mind for a testing framework. We > have our own independent and fully compatible fork of SUnit: > akuhn/SUnit, which is quite a strong code basis. but do we need should, class factory..... > And on top of that we > have Phexample, which has its own > name, some extra features and gives a clear point where Pharo is > different from the rest. This is not the difference that we look for. This is addressing people problems. > Just a suggestion: Let Adrian maintain akuhn/SUnit, perhaps minus the > "should" syntax that you don't like (as in: #(a b c) size should = 3), > and make akuhn/SUnit part of Pharo core. The new features (having tests depend > on one another, "should" syntax) go into Phexample, and I could > maintain that. Why not. If adrian wants. Now first we should have - a better name - clean the code = remove class factory + add comments - make sure that the tools can work with it - move the long execution Sunit extension to it - make sure that the tests are green - integrate/digest latest Sunit feature > > Cheers, > > Niko > > On Sun, Oct 24, 2010 at 8:37 AM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> Lack of maintainers, too many unwanted features, lack of explanation, >> large changes... >> >> And this is not that several persons did not look at the code. It got more than the average. >> >> Now I'm thinking that with discussion and care we should really get another testing framework with the same API that SUnit >> because if we want that PharoSunit is the same as Sunit then we are doomed to be backward compatible and no >> real improvements. >> >> Stef >> >> On Oct 23, 2010, at 10:58 PM, Adrian Kuhn wrote: >> >>> Sad to hear that. >>> >>> Technical difficulties, or just lack of customers? ^^ >>> >>> --AA >>> >>> On Oct 23, 2010, at 08:05 , StÃ©phane Ducasse wrote: >>> >>>> It was too difficult to integrate. >>>> >>>> Stef >>>> >>>> On Oct 23, 2010, at 2:01 PM, Niko Schwarz wrote: >>>> >>>>> What's the status of akuhn/SUnit? I couldn't find his code in 1.2 core. >>>>> >>>>> Niko >>>>> >>>>> On Wed, Feb 3, 2010 at 1:13 PM, StÃ©phane Ducasse >>>>> <stephane.ducasse(a)inria.fr> wrote: >>>>>> this loads well in the latest 1,1 core :) >>>>>> so now we should really have a look and these cool changes >>>>>> >>>>>> Stef >>>>>> >>>>>> On Jan 6, 2010, at 2:38 PM, Adrian Kuhn wrote: >>>>>> >>>>>>> SystemChangeNotifier uniqueInstance >>>>>>> noMoreNotificationsFor: TestCase. >>>>>>> Gofer it >>>>>>> disablePackageCache; >>>>>>> squeaksource: 'akuhn'; >>>>>>> package: 'SUnit'; >>>>>>> package: 'SUnitGUI'; >>>>>>> load. >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Pharo-project mailing list >>>>>> Pharo-project(a)lists.gforge.inria.fr >>>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> http://scg.unibe.ch/staff/Schwarz >>>>> twitter.com/nes1983 >>>>> Tel: +41 076 235 8683 >>>>> >>>>> _______________________________________________ >>>>> 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 >> > > > > -- > http://scg.unibe.ch/staff/Schwarz > twitter.com/nes1983 > Tel: +41 076 235 8683 > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] OCompletion doesn't work in Pharo 1.2 because of Preferences delete
by Mariano Martinez Peck Oct. 27, 2010

Oct. 27, 2010

HI Ramain (or someone with time). OCompletion does not work anymore in Pharo 1.2 because of the Preferences removal. It would be nice if you could update it to use the new settings framework. There is information here: http://book.pharo-project.org/book/CustomizingPharo/DeclaringSetting/ Thanks mariano

2 2

[Pharo-project] Smells looking at collections
by Florin Mateoc Oct. 26, 2010

Oct. 26, 2010

Eliot wrote: Hi Levente, in my experience playing with the Dan and Alan Borning's multiple inheritance implementation getting things to work was one thing, reasonably straighforward, but getting tool support right (file-out format so that things filed back in correctly, etc) was another, an dth ebulk of the work. Looking at your proposal below I see no problem getting it to work but see lots of problems integrating it, e.g. with Monticello, etc. Traits is already integrated with Monticello, supported with tests, etc. As such it is a much less risky or effortful proposition than a new scheme. So with that in mind are there important functional benefits of your scheme's direct state access as compared with traits that use accessors to access state that each user of a trait must implement? i.e. what are the key benefits you see in direct inst var access? best Eliot Hi Eliot, I think there is a strong argument for stateful traits, especially since we are talking about collection smells. One of the main selling points for traits (for me, at least) is that they would allow us to clean up the mess created by inheritance for reuse (Dictionary is a Set) in existing libraries. And obviously to create cleaner libraries going forward. Well, inheritance for reuse is used not just for behavior, but for state as well. Stateful traits would allow for a cleaner separation between inheritance and subtyping. Stateful traits would even allow you to push the separation further and, as part of your design, you could have state-only traits complementing behavior-only traits. Let us not forget that clean concepts are also easier to learn. I think it is much more important to get the concepts right than any existing integration with Monticello. Why does it matter that we have tests and integration if people are not using traits? Cheers, Florin

2 3

[Pharo-project] Fwd: Cog VM doesn't start to listen on socket
by Eliot Miranda Oct. 26, 2010

Oct. 26, 2010

---------- Forwarded message ---------- From: Eliot Miranda <eliot.miranda(a)gmail.com> Date: Tue, Oct 26, 2010 at 10:23 AM Subject: Re: Cog VM doesn't start to listen on socket To: Lukas Renggli <renggli(a)gmail.com> Hi Lukas, obviously we use sockets intensively in Teleplace and we see no problems that are to do with Cog. But Cog does throw up timing issues in your code because it has very different performance to the base VM (Smalltalk code is faster, most primitives have the same speed, allocation is slightly faster, etc). So my gut feeling is that what you're seeing is a timing related issue (race condition?) that is revealed when on Cog and hidden when on the normal VM. HTH (yeah, right... ed.) Eliot On Tue, Oct 26, 2010 at 5:04 AM, Lukas Renggli <renggli(a)gmail.com> wrote: > Hi Eliot, > > I noticed that on the Cog VM the Kom Seaside server does not > automatically start to listen, even if there is a process waiting at > the semaphore of the socket. Singaling that semaphore from the process > browser fixes the problem and the Cog image is fully working until the > next time it is opened. > > The exact same image opened with an old VM does not show the problem > and immediately starts to listen by itself. > > Did anybody else notice the same problem? Anybody found a solution? > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch >

3 5

Re: [Pharo-project] OCompletion doesn't work in Pharo 1.2 because of Preferences delete
by StÃ©phane Ducasse Oct. 26, 2010

Oct. 26, 2010

On Oct 26, 2010, at 11:38 PM, Levente Uzonyi wrote: > On Tue, 26 Oct 2010, StÃ©phane Ducasse wrote: > >> >> On Oct 26, 2010, at 11:18 PM, Levente Uzonyi wrote: >> >>> On Tue, 26 Oct 2010, Mariano Martinez Peck wrote: >>> >>>> HI Ramain (or someone with time). >>>> >>>> OCompletion does not work anymore in Pharo 1.2 because of the Preferences >>>> removal. It would be nice if you could update it to use the new settings >>>> framework. >>> >>> I fixed some of the preference issues (i didn't upload it yet), but it's a PITA to make it work in Pharo 1.2, because too many things were changed and are therefore broken. >> >> I can imagine. >> We should really get a way to support automatic change application but this is a real job to build that. >> >>> Btw what's with the "keep deprecated stuff for the next 2 minor versions" policy? >> >> this is what we do: we will remove 1.1 deprecated methods in 1.3 alpha. May be we did not apply it totally and are messy with that >> because we did not deprecated all the preferences methods. >> >>> Preferences are gone in 1.2, but Settings were only introduced in 1.1 and Preferences doesn't seem to be deprecated at all in 1.1. So, according to the policy, Preferences should be available till at least 1.3. >> >> the preferences class is just there in 1.2 to help people loading their code. but the behavior is gone. > > No, it's not there. At least not in the core image (12216). then this is just a mistake. > > > Levente > >> >> Settings were introduced in 1.1 (but not used) so that people can migrate their code in 1.1 to save it in 1.2. >> Alain reminds that recently. >>> >>> >>> Levente >>> >>>> >>>> There is information here: >>>> http://book.pharo-project.org/book/CustomizingPharo/DeclaringSetting/ >>>> >>>> Thanks >>>> >>>> mariano >>>> >>> >>> _______________________________________________ >>> 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 > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

1 0

Re: [Pharo-project] OCompletion doesn't work in Pharo 1.2 because of Preferences delete
by StÃ©phane Ducasse Oct. 26, 2010

Oct. 26, 2010

On Oct 26, 2010, at 11:18 PM, Levente Uzonyi wrote: > On Tue, 26 Oct 2010, Mariano Martinez Peck wrote: > >> HI Ramain (or someone with time). >> >> OCompletion does not work anymore in Pharo 1.2 because of the Preferences >> removal. It would be nice if you could update it to use the new settings >> framework. > > I fixed some of the preference issues (i didn't upload it yet), but it's a PITA to make it work in Pharo 1.2, because too many things were changed and are therefore broken. I can imagine. We should really get a way to support automatic change application but this is a real job to build that. > Btw what's with the "keep deprecated stuff for the next 2 minor versions" policy? this is what we do: we will remove 1.1 deprecated methods in 1.3 alpha. May be we did not apply it totally and are messy with that because we did not deprecated all the preferences methods. > Preferences are gone in 1.2, but Settings were only introduced in 1.1 and Preferences doesn't seem to be deprecated at all in 1.1. So, according to the policy, Preferences should be available till at least 1.3. the preferences class is just there in 1.2 to help people loading their code. but the behavior is gone. Settings were introduced in 1.1 (but not used) so that people can migrate their code in 1.1 to save it in 1.2. Alain reminds that recently. > > > Levente > >> >> There is information here: >> http://book.pharo-project.org/book/CustomizingPharo/DeclaringSetting/ >> >> Thanks >> >> mariano >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1