August 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Package Browser (bis)

by Alexandre Bergel

Yes, this was the case before Alexandre On 31 Aug 2009, at 05:39, StÃ©phane Ducasse wrote: > But in the browser of david the refactoring are there too. don't they? > > Stef > > On Aug 31, 2009, at 9:31 AM, Lukas Renggli wrote: > >>> 1. Where did the refactoring tools go? This version does not seem >>> to >>> include them. >> >> The refactoring code is only available for the traditional OB >> Browser. >> If you wanted you could fork the package and make it work with the OB >> Package Browser. >> >> Lukas >> >> -- >> 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 > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Aug. 31, 2009

[Pharo-project] method pane got crossed

by Carlos Crosetti

While updating software, I experienced a disconect in my DSL, then a exception raised (please read on) and as you may sse in the attached screenshot, the text pane where the method source code is shown, got crossed with a red background. I saw this effect happening but have not recorded the scenario. What is the code behind that makes the pane to get "crossed", what are the circumstances ? Regards, Carlos -----Mensaje original----- De: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr]En nombre de Ken Dickey Enviado el: Lunes, 31 de Agosto de 2009 01:25 a.m. Para: Pharo-project(a)lists.gforge.inria.fr Asunto: Re: [Pharo-project] Complex Solutions I have updated PharoInbox with a newer slice: SLICE-basic-Complex-KenDickey.3 Float hyperbolic trig methods no longer return Complex answers. Renamed: #angle -> #argument, #magnitude -># modulus. Added more unit tests. Thanks again for suggestions, -KenD _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Internal Virus Database is out-of-date. Checked by AVG. Version: 7.5.560 / Virus Database: 269.21.6/1323 - Release Date: 10/03/2008 11:07 a.m.

Aug. 31, 2009

Re: [Pharo-project] Complex Solutions

by Ken Dickey

Bill, I have already said that I think IEEE floats tend to give the wrong answer fast. Better solutions are hard to come by, however, as they definately depend on the problem domain. E.g. Apple's old plot program used interval arithmetic and did a great job with functions like x * sin(1/x) near zero. You could zoom in time after time and still get an accurate plot -- where IEEE floats are useless. Interval math is also great when you have measurement error and you can't fool yourself about error analysis. It is sure helpful to know the difference between 3.023+/-0.001 and 3.023+/-2e56 . Interval math does have splits and it is sometimes useful to calculate the probability distribution of the value in the interval. No perfect world, sigh. If you are using ideal mathematics, on the other hand, there are exact real representations which can be used, but these are pretty heavy weight for day to day computing. Another day; a little better approximation, -KenD >From: "Schwab,Wilhelm K" <bschwab(a)anest.ufl.edu> ... >As for the zero vector, it is hard to say. Note that a nearly zero vector > is going to have a very poorly defined direction in that the result will > likely be dominated by roundoff error. Often there is a better way to > compute such things; a rearrangment of governing equations can make a world > of difference - that's not something you can fix, it will be > problem-specific how one would avoid computing the argument in tricky > situations. One possible approach is to simply compute the angle the same > way for all values and let under/over flow errors take care of the garbage. > Another would be to raise an error. Finally, you might define #argument, > #argumentIfSmall: (takes a block for the troublesome case) and > #argumentIEEE to use their convetion. > >Something that deserves a careful look is the test for floats being close to > each other. I have been supicious about that for a while, and on first > glance, Dolphin seems to handle it very differently from the way Squeak > does. IMHO, being different from Dolphin is cause for a good think. We > shouls also see how VW handles it. > >Just looking at #closeTo:, it appears to "think" that 10^-4 is a good > threshold, and that is questionable depending on the scales involved, and > is far from the smallest float that can be reasonable represented. > >Bill

Aug. 31, 2009

Re: [Pharo-project] [ OT] ESUG videos?

by Serge Stinckwich

James is doing doing videos of some tracks. So i guess, you will find them soon on his blog. On Mon, Aug 31, 2009 at 5:13 PM, Esteban Lorenzano<estebanlm(a)gmail.com> wrote: > Hi, > Sorry for the Off-Topic, but couldn't go to ESUG, and I'm eager to > watch almost every presentation on it... > Will it be possible? > > Cheers, > Esteban > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Serge Stinckwich UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam Smalltalkers do: [:it | All with: Class, (And love: it)] http://doesnotunderstand.org/

Aug. 31, 2009

[Pharo-project] [OT] ESUG videos?

by Esteban Lorenzano

Hi, Sorry for the Off-Topic, but couldn't go to ESUG, and I'm eager to watch almost every presentation on it... Will it be possible? Cheers, Esteban

Aug. 31, 2009

Re: [Pharo-project] Package Browser (bis)

by StÃ©phane Ducasse

But in the browser of david the refactoring are there too. don't they? Stef On Aug 31, 2009, at 9:31 AM, Lukas Renggli wrote: >> 1. Where did the refactoring tools go? This version does not seem to >> include them. > > The refactoring code is only available for the traditional OB Browser. > If you wanted you could fork the package and make it work with the OB > Package Browser. > > Lukas > > -- > 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

Aug. 31, 2009

Re: [Pharo-project] How to build a GUI

by StÃ©phane Ducasse

YES!!! On Aug 30, 2009, at 11:57 PM, Torsten Bergmann wrote: > Release early and show a steady progress by releasing often. Thats the > key to success. And listen to feedback. > Otherwise you will work towards "the perfect time to > release" (remember > you already said it will be in a releasable state after 14 days) > You already mentioned the next tasks on your list (which will continue > to grow the more you work since you will get more ideas and it will > become more and more work for a single person). > > Most of the time projects working towards perfection will never be > released or used. There is also the problem that others will start > developing a similar one meanwhile since they cant wait or dont know > that > there is already someone investing his time and knowledge.

Aug. 31, 2009

Re: [Pharo-project] How to build a GUI

by StÃ©phane Ducasse

+ 1 + 1 Release the code. Get other people have a look. Release often get feedback. Stef On Aug 30, 2009, at 11:30 PM, Henrik Johansen wrote: > > On Aug 30, 2009, at 10:32 32PM, nullPointer wrote: > >> -Create a mechanism for link properties or accessors of a object >> ( entitys ) >> at controls.I donÂ´t like the MorphicModel mechanism,and dependences. >> I want >> events for all.That last is very important necessity. > Having seen a...fair amount of how complex event handling can get in > VisualWorks GUI's, I'd really appreciate it if you'd take a look into > using Announcements :) > Unless of course, events mean something entirely different in Squeak. >> Now iÂ´m adding new capabilities. >> >> -Radio buttons widget mechanism.A selection of one must disable the >> others >> in the same container. >> -Styles editor. I want add the capabilitie of create and edit styles >> for the >> widgets.And apply with a #applyStyle: method. and too from UIBuilder. >> -Add new properties for set in the UIBuilder, not only the basics >> text, >> image or font. >> -I want build a tabControl of intuitive way, add, remove and fill >> tabs from >> designer. >> -A good way for persist the morph mechanism is needed.Perhaps not >> now but it >> will be necessary more ahead if something serious is wanted. > I love the sweet smell of feature creep in the morning! > Just remember, shipping something is better than nothing, and it's not > like anything existing seems to come even close to what you have made > already. >> >> I prefer not to say when I will conclude my work, but It does not >> have sense >> to raise something incorrect or incomplete. IÂ´m put much effort in >> that work >> and i want do it good. >> >> Regards :) > Incorrect, I agree. Take a look at the Pharo bugtracker and note the > amount of pure bugs not marked 1.0 if you feel 0 bugs is the limit for > when something is in a releasable state though :) > Incomplete... well, 20% gets used 80% of the time and all that. > > I have no idea of the structure of what you are doing, just thought > I'd add one thing, which I've found immensely useful in the VW > UIBuilder: > - Include hooks in the interface building process. (preBuildWith: , > postBuildWith:, preOpenWith: postOpenWith: ), so you can modify the > spec at runtime. > Not everything about how you want an interface to display can be known > at design-time, adding such hooks provide the means to do pretty neat > dynamic stuff based on the runtime environment. > F.ex: - VisualWorks allows you to provide application-specified labels > instead of hardcoding them in the design viewer. > However, by default, only labels defined as methods on the class side > of the ApplicationModel will be mapped to the builders list of labels. > (as far as I know at least...). > Using preBuildWith:, you can add instance-specific (say, taken from > its model) labels to the Builders dictionary of available labels. > > Good luck with the further work, I look forward to seeing the results! > > Cheers, > Henry > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Aug. 31, 2009

Re: [Pharo-project] Package Browser (bis)

by Lukas Renggli

> 1. Where did the refactoring tools go?Â This version does not seem to > include them. The refactoring code is only available for the traditional OB Browser. If you wanted you could fork the package and make it work with the OB Package Browser. Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Aug. 31, 2009

Re: [Pharo-project] Complex Solutions

by Ken Dickey

I have updated PharoInbox with a newer slice: SLICE-basic-Complex-KenDickey.3 Float hyperbolic trig methods no longer return Complex answers. Renamed: #angle -> #argument, #magnitude -># modulus. Added more unit tests. Thanks again for suggestions, -KenD

Aug. 31, 2009