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

Re: [Pharo-project] modal windows and unit tests
by StÃ©phane Ducasse Oct. 13, 2010

Oct. 13, 2010

On Oct 13, 2010, at 3:04 PM, Alexander LazareviÄ wrote: > There are also some basic things that would need some adjustment as I > see it. I think core or basic classes and models shouldn't make any > assumptions about the UI or even if there is an UI at all. YESSSssssssss.... and a minicore will help /force us to do that (imagine an hudson script blocked because of a nice popup) > So things like Object inform: aString would be something I'd rather > see to disappear. Yes Alexander, this is years that I want that. In fact we started pharo exactly for these kinds of reasons. Getting a clean and cool system. Any code going in that direction is welcome and will be warmly considered. > Or Class rename: aString, which kindly pops up a Dialog to inform the > "user" when there are still references in Undeclared. I think that > check should better move to the sending method in Browser renameClass, > where chances are very high that a real user initiated the rename of a > class and not some filein. > > Alex > > 2010/10/13 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> I think that we will have to reconsider a lot of the infrastructure decision and the hudson server will kick us >> >> Stef >> >> On Oct 12, 2010, at 10:45 PM, Alexander LazareviÄ wrote: >> >>> I was just looking at something similar. >>> I guess for modal windows that are a kind of DialogWindow something >>> like this should work >>> >>> [UIManager default confirm: 'Got milk?'] >>> on: ProvideAnswerNotification >>> do: [:ex | ex resume: (ex messageText = 'Got milk?')] >>> >>> But which modal windows do pop up in your scenario, that do not send a >>> notification? >>> >>> Regards, >>> Alex >>> >>> 2010/10/12 Alexandre Bergel <alexandre(a)bergel.eu>: >>>> Hi! >>>> >>>> A modal window is pop up by one of my tests. Is there a way to capture this situation and simply remove the modal window? >>>> Apparently, no notification is raised... >>>> >>>> Cheers, >>>> Alexandre >>>> -- >>>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>>> 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 >>>> >>> >>> _______________________________________________ >>> 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

2 1

Re: [Pharo-project] Issue 3099: Create method in the debugger does not provide getters/setters implementations
by StÃ©phane Ducasse Oct. 13, 2010

Oct. 13, 2010

+1 We are nice and taking on our time to fix problems but if you do it directly on the current unstable version you will speed up the integration. On Oct 13, 2010, at 2:34 PM, Igor Stasenko wrote: > 2010/10/13 Hernan Wilkinson <hernan.wilkinson(a)10pines.com>: >> No... I have 1.1, is 1.2 released? I have no problem to migrate it to 1.2, >> let me know > > 1.2 is a bleeding-edge under-development image. > > IMO, If you want to add new feature(s) to future release of pharo, > then you need to always work with latest available/updated image to make sure > your changes working w/o problem and do not interfere with other stuff. >

1 0

[Pharo-project] Fwd: License question
by StÃ©phane Ducasse Oct. 13, 2010

Oct. 13, 2010

Begin forwarded message: > From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > Date: October 13, 2010 2:46:31 PM GMT+02:00 > To: Paolo Bonzini <bonzini(a)gnu.org> > Cc: "Fitzell, Julian" <jfitzell(a)cincom.com>, "stephane.ducasse(a)inria.fr" <stephane.ducasse(a)inria.fr> > Subject: RE: [Pharo-project] License question > > Paolo, > > The language is not childish; it is a valid expression of how this looks to others; I know, because I had it blow up in my face. I am fairly content to use GSL for its feature set and working around its foibles, only because I use it internally and GPL is not a concern. I got a cold dose of reality in the form of resistance from other programmers - some of whom see the license as a legal virus. After reading your "clone the API, then you can run fast as GPL or slow as MIT," I am more than ever aware of just how on the mark that characterization might be. > > Another indication of the extent of the problems with/from GPL arises from my planned use of the Pharo Inbox. Put the code in there, and it's MIT; that's good. But what mess does that cause with a binding to something that is GPL? The answer is not to change the Pharo license, it is to exclude GPL code. I can put something on my web site and allow people to grab it from there. > > The base of the GSL binding is (from memory) 100+ structure definitions (most of which are correct in spirit but not yet tested) and 1800+ function definitions. It ends up being something like 20,000 things that have to be named and typed. They are not much good without wrappers that help with memory management and control flow. I would like to make at least some of the wrapper functionality available, but I am not willing to GPL it for fear of future problems using my own code. If you are telling me that anything that directly or indirectly calls GPL code becomes GPL on release, that will impact how much of the code I can release. One solution would be to clone and release just enough of the wrapper set to help people to roll their own wrappers, which might eventually spawn a clean-roomed set of wrappers. A good MIT library will eventually appear, and when it does, I want to be able to move my higher level code to it. I will not hobble that goal for short-term gains. Childish? Quite the opposite. > > Bill > > > > ________________________________________ > From: Paolo Bonzini [paolo.bonzini(a)gmail.com] On Behalf Of Paolo Bonzini [bonzini(a)gnu.org] > Sent: Wednesday, October 13, 2010 3:50 AM > To: Schwab,Wilhelm K > Cc: Fitzell, Julian; stephane.ducasse(a)inria.fr > Subject: Re: [Pharo-project] License question > > On 10/12/2010 08:13 PM, Schwab,Wilhelm K wrote: >> nor do I want my code, other than the binding itself, affected by >> GPL. > > Code that uses the binding is obviously affected by the GPL, just like > if you used GSL directly in C. It's not like using a different > programming language is a magic wand that makes the GPL disappear. > > However, your code that does not use the binding will not be affected by > the GPL. Code doesn't fall under the GPL just because it lived for a > short time in the same image. In particular: > > 1) the GPL does not kick in until you distribute the code. As long as > GPL and non-GPL (or even GPL-incompatible) code resides in a private > image (or even circulates within an institution such as a company) there > is no distribution and the GPL is not involved at all. > > 2) let's say you juxtapose GPL and X11-licensed (MIT) code in the same > image. The non-GPL code doesn't use your bindings or any other GPL > code, it's just placed together in the same image. This time you > distribute the image, and in order to do so you must follow the GPL. > However, you can still extract the X11-licensed code and distribute > _that_ code under its own original license, or even as proprietary code > since _that_ code's license is what counts. > >> It would be a shame to have to limit the a release to just the >> binding, but if GPL starts to infect anything that connects to the >> binding > > It doesn't "start to infect". Please do not use such childish language. > The GPL simply "applies" to anything that connects to the binding, > just like it would "apply" to anything that uses GSL using the C interface. > > You probably would not say that using proprietary source code in Squeak > or Pharo "infects" it with a proprietary license. You'd simply say "you > have to respect the license of the proprietary source code", or you > violate the copyright owner's rights. The GPL is absolutely no > different. It tells you what you can do and what you cannot do. > > Very frankly: if you think the GPL has "infected" something, well, it > didn't do anything on its own, it was _you_ who did something stupid. > > Paolo

1 0

Re: [Pharo-project] Issue 3099: Create method in the debugger does not provide getters/setters implementations
by StÃ©phane Ducasse Oct. 13, 2010

Oct. 13, 2010

unstable is available on the forge and this is important to develop on it else we have a lot of problem merging. Stef On Oct 13, 2010, at 1:18 PM, Hernan Wilkinson wrote: > No... I have 1.1, is 1.2 released? I have no problem to migrate it to 1.2, let me know > > On Wed, Oct 13, 2010 at 3:06 AM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Thanks hernan > did you do that with the lastest 1.2? > > Stef > > On Oct 13, 2010, at 3:35 AM, Hernan Wilkinson wrote: > > > Hi, > > I added an issue (an enhancement really) and also uploaded the code for it. > > The enhancement is that when you press "Create" on the debugger, it would be nice if the generated method could realize that the message is a getter or setter and provide an implementation accordingly. > > I also refactor the method #createMethodStub in Message. To do so I create the class DynamicMessageImplementor and its test DynamiMessageImplementorTest. > > > > I hope you like it! > > Hernan. > > > > -- > > HernÃ¡n Wilkinson > > Agile Software Development, Teaching & Coaching > > Mobile: +54 - 911 - 4470 - 7207 > > email: hernan.wilkinson(a)10Pines.com > > site: http://www.10Pines.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 > > > > -- > HernÃ¡n Wilkinson > Agile Software Development, Teaching & Coaching > Mobile: +54 - 911 - 4470 - 7207 > email: hernan.wilkinson(a)10Pines.com > site: http://www.10Pines.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 2

Re: [Pharo-project] modal windows and unit tests
by StÃ©phane Ducasse Oct. 13, 2010

Oct. 13, 2010

I think that we will have to reconsider a lot of the infrastructure decision and the hudson server will kick us Stef On Oct 12, 2010, at 10:45 PM, Alexander LazareviÄ wrote: > I was just looking at something similar. > I guess for modal windows that are a kind of DialogWindow something > like this should work > > [UIManager default confirm: 'Got milk?'] > on: ProvideAnswerNotification > do: [:ex | ex resume: (ex messageText = 'Got milk?')] > > But which modal windows do pop up in your scenario, that do not send a > notification? > > Regards, > Alex > > 2010/10/12 Alexandre Bergel <alexandre(a)bergel.eu>: >> Hi! >> >> A modal window is pop up by one of my tests. Is there a way to capture this situation and simply remove the modal window? >> Apparently, no notification is raised... >> >> Cheers, >> Alexandre >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> 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 >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

4 5

[Pharo-project] modal windows and unit tests
by Alexandre Bergel Oct. 13, 2010

Oct. 13, 2010

Hi! A modal window is pop up by one of my tests. Is there a way to capture this situation and simply remove the modal window? Apparently, no notification is raised... Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

3 7

Re: [Pharo-project] Issue 3099: Create method in the debugger does not provide getters/setters implementations
by StÃ©phane Ducasse Oct. 13, 2010

Oct. 13, 2010

Thanks hernan did you do that with the lastest 1.2? Stef On Oct 13, 2010, at 3:35 AM, Hernan Wilkinson wrote: > Hi, > I added an issue (an enhancement really) and also uploaded the code for it. > The enhancement is that when you press "Create" on the debugger, it would be nice if the generated method could realize that the message is a getter or setter and provide an implementation accordingly. > I also refactor the method #createMethodStub in Message. To do so I create the class DynamicMessageImplementor and its test DynamiMessageImplementorTest. > > I hope you like it! > Hernan. > > -- > HernÃ¡n Wilkinson > Agile Software Development, Teaching & Coaching > Mobile: +54 - 911 - 4470 - 7207 > email: hernan.wilkinson(a)10Pines.com > site: http://www.10Pines.com > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

3 2

Oct. 13, 2010

Begin forwarded message: > From: Paolo Bonzini <bonzini(a)gnu.org> > Date: October 13, 2010 9:51:01 AM GMT+02:00 > To: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> > Cc: "Fitzell, Julian" <jfitzell(a)cincom.com>, "stephane.ducasse(a)inria.fr" <stephane.ducasse(a)inria.fr> > Subject: Re: [Pharo-project] License question > > On 10/12/2010 08:13 PM, Schwab,Wilhelm K wrote: >> nor do I want my code, other than the binding itself, affected by >> GPL. > > Code that uses the binding is obviously affected by the GPL, just like if you used GSL directly in C. It's not like using a different programming language is a magic wand that makes the GPL disappear. > > However, your code that does not use the binding will not be affected by the GPL. Code doesn't fall under the GPL just because it lived for a short time in the same image. In particular: > > 1) the GPL does not kick in until you distribute the code. As long as GPL and non-GPL (or even GPL-incompatible) code resides in a private image (or even circulates within an institution such as a company) there is no distribution and the GPL is not involved at all. > > 2) let's say you juxtapose GPL and X11-licensed (MIT) code in the same image. The non-GPL code doesn't use your bindings or any other GPL code, it's just placed together in the same image. This time you distribute the image, and in order to do so you must follow the GPL. However, you can still extract the X11-licensed code and distribute _that_ code under its own original license, or even as proprietary code since _that_ code's license is what counts. > >> It would be a shame to have to limit the a release to just the >> binding, but if GPL starts to infect anything that connects to the >> binding > > It doesn't "start to infect". Please do not use such childish language. The GPL simply "applies" to anything that connects to the binding, just like it would "apply" to anything that uses GSL using the C interface. > > You probably would not say that using proprietary source code in Squeak or Pharo "infects" it with a proprietary license. You'd simply say "you have to respect the license of the proprietary source code", or you violate the copyright owner's rights. The GPL is absolutely no different. It tells you what you can do and what you cannot do. > > Very frankly: if you think the GPL has "infected" something, well, it didn't do anything on its own, it was _you_ who did something stupid. > > Paolo

1 0

[Pharo-project] is Squeaksource down?
by Guillermo Polito Oct. 13, 2010

Oct. 13, 2010

:( Can someone check it? Thanks!

4 3

Re: [Pharo-project] [squeak-dev] Re: Xtreams port to Squeak - second wave
by mkobetic＠gmail.com Oct. 13, 2010

Oct. 13, 2010

"Sven Van Caekenberghe"<sven(a)beta9.be> wrote: > >> I also found an issue: the process in XTTransformWriteStream doesn't > >> terminate. If you run the tests, you'll get 12 lingering processes. > > > > I don't see that happening in Pharo 1.1. Normally the process should end normally when the stream is closed (the close synchronizes with the process via the closeReady semaphore). Maybe there's a missing close somewhere in the test suite ? > > I have these hanging processes as well (you probably know that the Process Browser does not auto update by default ?), I've never seen unit tests that did that... OK, I can see this on VW side too. The following test cases fail to close the transform write stream (against our own advice, sic): Xtreams.ReadingWritingTest>>#testWriteRejecting Xtreams.ReadingWritingTest>>#testWriteSelecting Xtreams.ReadingWritingTest>>#testWriteTransformHexToByte Xtreams.ReadingWritingTest>>#testWriteTransforming1into2 Xtreams.ReadingWritingTest>>#testWriteTransforming2into1 I'll make the fixes on VW side.

1 0