- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Issue 3099: Create method in the debugger does not provide getters/setters implementations

by StÃ©phane Ducasse

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

Oct. 13, 2010

Re: [Pharo-project] modal windows and unit tests

by Alexandre Bergel

Thanks for your answers. But the problem still persists. For example, the following does not open the popup: [self inform:'No cycles' ] on: Notification do: [:ex | ]. The notification is captured. However, the following opens the popup: [StandardWindow new message:'No cycles' ] on: Notification do: [:ex | ]. Any idea how I can make the popup not open? Cheers, Alexandre On 12 Oct 2010, at 17:42, Schwab,Wilhelm K wrote: > First, did you open the window (as in it's the point of the test), or did Pharo open it in contradiction to your better judgment? If the latter, what is happening? > > Assuming that you have opened a modal window in a test, there are a couple of ways that I have handled such things in Dolphin. First, if you can slightly refactor your code, you might be able to open it non-modally, which might help some; however, you really want to dismiss it as part of the test. Regardless of modality, you probably want to store the window in a temporary variable as part of your test and then either send it a message or command to close. > > I will take a quick look for something I wrote in Dolphin and reply if it looks like it might have any value. > > Bill > > > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Alexandre Bergel [alexandre(a)bergel.eu] > Sent: Tuesday, October 12, 2010 3:39 PM > To: Pharo Development > Subject: [Pharo-project] modal windows and unit tests > > 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 -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Oct. 13, 2010

Re: [Pharo-project] Issue 3099: Create method in the debugger does not provide getters/setters implementations

by Hernan Wilkinson

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 <http://www.10pines.com/>*

Oct. 13, 2010

[Pharo-project] Fwd: License question

by StÃ©phane Ducasse

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

Oct. 13, 2010

Re: [Pharo-project] is Squeaksource down?

by Steven Baker

That doesn't actually work, because squeaksource.com has a landing page. -Steven 2010/10/13 Norbert Hartl <norbert(a)hartl.name>: > http://downforeveryoneorjustme.com/squeaksource.com > you can use this if you are asking yourself. > Norbert > On 13.10.2010, at 09:40, Mariano Martinez Peck wrote: > > yes from here :( > > 2010/10/13 Guillermo Polito <guillermopolito(a)gmail.com> >> >> :( >> >> Can someone check it? >> >> Thanks! >> >> _______________________________________________ >> 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 >

Oct. 13, 2010

Re: [Pharo-project] is Squeaksource down?

by Norbert Hartl

http://downforeveryoneorjustme.com/squeaksource.com you can use this if you are asking yourself. Norbert On 13.10.2010, at 09:40, Mariano Martinez Peck wrote: > yes from here :( > > 2010/10/13 Guillermo Polito <guillermopolito(a)gmail.com> > :( > > Can someone check it? > > Thanks! > > _______________________________________________ > 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. 13, 2010

Re: [Pharo-project] is Squeaksource down?

by Mariano Martinez Peck

yes from here :( 2010/10/13 Guillermo Polito <guillermopolito(a)gmail.com> > :( > > Can someone check it? > > Thanks! > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Oct. 13, 2010

Re: [Pharo-project] modal windows and unit tests

by StÃ©phane Ducasse

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

Oct. 13, 2010

Re: [Pharo-project] Issue 3099: Create method in the debugger does not provide getters/setters implementations

by StÃ©phane Ducasse

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

Oct. 13, 2010

Re: [Pharo-project] [squeak-dev] Re: Xtreams port to Squeak - second wave

by mkobetic＠gmail.com

"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.

Oct. 13, 2010