- Pharo-dev - lists.pharo.org

[Pharo-project] Autotest / TDD + screencast
by laurent laffont Oct. 14, 2010

Oct. 14, 2010

Hi, Here's a first usable version of Autotest (automatic test runner, inspired by Ruby's ZentTest autotest). The goal is to have instant feedback on the code you The screencast to see it in action: http://lolgzs.free.fr/pharo/autotest_1.mpeg To load it: Gofer new squeaksource: 'Autotest'; package: 'Autotest'; load Comments are welcome as I have to rewrite it better :) Repository is read / write for those who wants to contribute. Cheers, Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/

3 3

[Pharo-project] [ANN] Pharo 1.1.1 OneClickCogVm
by Mariano Martinez Peck Oct. 13, 2010

Oct. 13, 2010

Hi. This is not an official release. I didn't do all the formal procedure for releasing a Pharo image. My idea is try to push CogVM and try to get as much as testers as possible. Try to report issues and help Eliot. For that purpose, I think having a one click image is worth it. So.....I build a Pharo dev on top of the PharoCore 1.1.1 (which has some fixes over 1.1 and the CogVM necessary changes). I build the image with exactly the same versions of the external packages than Pharo 1.1. If you want to download that this Pharo1.1.1 dev image that works with Cog here is the link: https://gforge.inria.fr/frs/download.php/27516/Pharo-1.1.1-dev10.09.1.zip In addition, and thanks to Lukas, we could generate OneClicks with CogVM. Here you can have a OneClick using the above image: https://gforge.inria.fr/frs/download.php/27524/Pharo-1.1.1-OneClickCogVM.zip Notice that this is not an official release and that there are failing/errors tests. I've already sent emails for them and hopefully someone may fix them. The only thing is not supported is the TestCoverage (since it uses objects as methods, with is not yet supported in CogVM). Cheers Mariano

9 21

[Pharo-project] How about atomic value-swap bytecode?
by Igor Stasenko Oct. 13, 2010

Oct. 13, 2010

Hello, i just thought, that it would be cool to have a special bytecode, which guarantees atomicity for swapping values between two variables. To swap two values, you usually do: | var1 var2 temp | temp := var1. var1 := var2. var2 := temp. But since its non-atomic, a process can be interrupted and such operation is not thread-safe. In order to make it thread safe, you must add even more boilerplate: | var1 var2 temp | semaphore critical: [ temp := var1. var1 := var2. var2 := temp. ] So, i thought , if we could have a special bytecode, then we could write something like: | var1 var2 | var1 :=: var2. So, VM will guarantee that values of var1 and var2 will be swapped atomically, and completely thread-safe. var1 and var2 could be either temps or instance variables, but of course not arguments, since they are not assignable. One thing i don't like, that it will need to introduce a new syntax for atomic-value-swap operator - :=: Or, maybe just reserve a special keyword selector (which is recognized by compiler), so var1 __atomicSwapWith: var2 so it will look like a regular smalltalk syntax, except that its not a message send, but a low-level operation instead. -- Best regards, Igor Stasenko AKA sig.

4 8

[Pharo-project] Iliad 0.9.1 released
by Nicolas Petton Oct. 13, 2010

Oct. 13, 2010

Hi, We are happy to announce the release of Iliad 0.9.1 for GNU Smalltalk, Pharo and Squeak. This is a bug fix release. Download & installation instructions can be found at http://www.iliadproject.org/pages/Download. The website also received some love and is now wearing a new design. Happy Iliad hacking, Nicolas Petton & SÃ©bastien Audier

1 0

[Pharo-project] OCompletion usability
by Nicolas Cellier Oct. 13, 2010

Oct. 13, 2010

Hi all, Thanks to Levente, I activated OCompletion in trunk. It's nice when typing a text from scratch (like in a workspace). But when modifying an existing text, not that great. The feature I most miss is the ability to overwrite a word fragment and hit cmd+j to repeat the replacement. Would it be possible to restore this behavior ? Nicolas

2 1

[Pharo-project] FreeType fonts scan annoyance on windows
by Igor Stasenko Oct. 13, 2010

Oct. 13, 2010

If you're on Windows, a freetype searching fonts everywhere on all drive letters. This causes opening annoying 'Insert disk in drive X:' dialog. guessWindowsFontFolderPath "Guess the location of the Windows font folder" | possibles | possibles := Set new. 'cdefghijklmnopqrstuvwxyz' do:[:drive | #('\windows\fonts' '\winnt\fonts') do:[:path | | d | (d := FileDirectory on: drive asString, ':', path) exists ifTrue:[possibles add: d]]]. possibles := possibles asSortedCollection: [:a :b | a directoryEntry creationTime >= b directoryEntry creationTime]. possibles ifNotEmpty:[^possibles first pathName]. ^nil Here what i found occasionally, when read ReadFile() function documentation in MSDN: If you are attempting to read from a floppy drive that does not have a floppy disk, the system displays a message box that prompts the user to retry the operation. To prevent the system from displaying this message box, call the SetErrorMode function with SEM_NOOPENFILEERRORBOX. But it will require changing VM to call SetErrorMode() during startup to prevent these promts from appearing. -- Best regards, Igor Stasenko AKA sig.

1 0

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

Oct. 13, 2010

Begin forwarded message: > From: Paolo Bonzini <bonzini(a)gnu.org> > Date: October 13, 2010 3:38:49 PM 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/13/2010 02:46 PM, Schwab,Wilhelm K wrote: >> 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. > > It only blew up in your face, because you didn't make a totally informed > decision upfront. The GPL FAQ can be a tough read, but it is really complete and helpful. It's not legally binding, but it's written by people who are experts and try to cover as many cases as possible, and . > >> 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. > > Note that nothing forbids you from extending the "slow MIT" part until > it's as fast as the GPL version and effectively obsoletes it. It's just > basic software engineering that you'll first make things work, then > make things fast. > >> Another indication of the extent of the problems with/from GPL >> arises from my planned use of the Pharo Inbox. > > That's not a problem with/from GPL. That's a conscious choice from the > Pharo people, who decided to restrict the Inbox to only accept things > with a particular license. It's not good or wrong, it's simply a > decision that you have to live with. > >> 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. > > Ok, that's fine---making provisions for the future is totally understandable and not childish at all. But then, it doesn't require the usage of language such as "infect" or "virus", either. :) > > The good news is that you can do it. See this other point from the GPL FAQ: > > If a library is released under the GPL (not the LGPL), does that > mean that any program which uses it has to be under the GPL or a > GPL-compatible license? > > Yes, because the program as it is actually run includes the library. > > Note how it says "GPL-compatible" license. Right above this, it says > > The GPL says that the whole combined program has to be released > under the GPL. [...] > > But you can give additional permission for the use of your code. > You can, if you wish, release your program under a license which is > more lax than the GPL but compatible with the GPL. > > So you can release your bindings now and put it under the X11/MIT license. However, I'd still add a README statement specifying that everything using the bindings will also use GSL, and so will have to respect the GPL (when distributed). You can quote the GPL FAQ and highlight "GPL-compatible". > > I can understand if there were some resistance from the Pharo > people about putting this in the main image, however. So, I still suggest that you release your library from your website or from SqueakSource. > > -*- > > As an aside, the GPL is not alone in putting restrictions on redistributions, but it does so for a specific end, which is to maximize the users' freedom. This includes end users, not only developers. > > Take instead Microsoft's license on sample source code, which says you cannot distribute any derivative work in source code. Personally I prefer something that forces me to help people learn, than something that forbids me from doing so. > > I hope this helps you in making a conscious choice, and also in trying to understand my position. > > Paolo

2 1

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

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