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

Re: [Pharo-project] [update 1.1] #11392

by Henrik Johansen

On Jun 11, 2010, at 4:22 43PM, Schwab,Wilhelm K wrote: > Rotating text?? What is the correct way to do that? I have found ways to rotate forms, but not text. What am I missing? You can rotate any morph. What's really happening is the morph (in this case a TextMorph) is displayed on a form, which is then rotated. Cheers, Henry

June 11, 2010

Re: [Pharo-project] [update 1.1] #11392

by Schwab,Wilhelm K

Rotating text?? What is the correct way to do that? I have found ways to rotate forms, but not text. What am I missing? ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Marcus Denker [marcus.denker(a)inria.fr] Sent: Friday, June 11, 2010 8:10 AM To: Pharo-project(a)lists.gforge.inria.fr Development Subject: [Pharo-project] [update 1.1] #11392 11392 ----- Issue 2533: GradientFillStyle cant change first and last color from halo menu Issue 2207: Rotating text is broken -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD. _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 11, 2010

Re: [Pharo-project] seaside.gemstone.com down - unable to build 1.1-dev

by James Foster

I'm investigating this with GemStone's IT people. I'll give an update as soon as I have something. James Foster VMware (formerly GemStone Systems) On Jun 11, 2010, at 5:42 AM, Schwab,Wilhelm K wrote: > This is why I want to see separate web images; by not pre-packaging we just transfer the headaches from Pharo's developers to its users, increasing the number of opportunities to have failures, load on servers, etc. > > Bill > > > > -----Original Message----- > From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Torsten Bergmann > Sent: Friday, June 11, 2010 6:53 AM > To: pharo-project(a)lists.gforge.inria.fr > Subject: [Pharo-project] seaside.gemstone.com down - unable to build 1.1-dev > > http://seaside.gemstone.com/ss/metacello/ is down, therefore ConfigurationOfPharo can not be used to build Pharo 1.1. from an updated core. > > See http://downforeveryoneorjustme.com/seaside.gemstone.com > > Maybe the machine is switched to vmware.com? > > However - we should again think about reliable infrastructure ... > > Thx > T. > > > -- > GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. > Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl > > _______________________________________________ > 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 >

June 11, 2010

Re: [Pharo-project] GUI Polymorph

by Schwab,Wilhelm K

Hilaire, I will indeed consider it, but it will take me time to get to your level of understanding of Polymorph. My priorities are networking, serial communications, printing (which I am dreading) and then finally GUI construction. The last two are backwards, but the GUI does me no good if I can't print on Linux. Somewhere in there I hope to pull a big thorn out of my foot by moving various machines to Linux. With a working GUI+printing, the rest of the boxes go to Linux, and the drinks are on me :) Understood about your objectives, but I think they SHOULD include teaching efficient updates. When MS did this correctly, they did the simplest thing that would work, and then separately modified it for efficiency. Smalltalk is not the fastest language in existence, Pharo is not the fastest among its peers, and even if it were, we should be doing things better and more efficiently than the rest of the world. It is nuts that we need 2GB of RAM to boot an OS and read email; while that sloppiness arguably begins in Redmond, it can be attenuated here. Bill ________________________________________ From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Hilaire Fernandes [hilaire.fernandes(a)gmail.com] Sent: Friday, June 11, 2010 9:46 AM To: pharo-project(a)lists.gforge.inria.fr Subject: Re: [Pharo-project] GUI Polymorph Schwab,Wilhelm K a Ã©crit : > Hilaire, > > It was interesting to watch MS' position on GUI examples change over time. Visual C++ started out teaching how to create efficient software. Then one day those examples were gone and all they could talk about was "smooth scrolling" which turned out to be a way to make the machine do the inefficient thing four times instead of once. > > The idea of altering the model, finding out what is invalidated, marking that as closely as can be done within bounds of common sense (or until diminishing returns), and then drawing just the changed parts is non-intuitive and VERY important. You have done a wonderful job so far, but optimization deserves attention. Please fell free to search and to document it. As I wrote in my previous email, my objective writing this documentation was not how to efficiently implement a paint canvas. Hilaire _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 11, 2010

Re: [Pharo-project] OpenDBX for dbase files

by Carla F. Griggio

I used xbase for reading dbf. That should work. But I don't have idea if xbase could be integrated to squeakDBX. Cheers! Carla On Friday, June 11, 2010, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > > > 2010/6/11 Facundo Vozzi <facundov79(a)gmail.com> > > > Hi at all,can I used openDBX for read dbase (.dbf) files or I need try with xbase ? > > Hi Facundo. Sounds Spanish name (or even Argentinian!!!Â ;)Â ) > > I don't know if it is possible. I even don't know that dbase is (I had to googled it) > > what is xbase also? > > I cc'ed openDBX mailing list and maybe Norbert can help you. > > Cheers > > Mariano > > > > regards,Facu > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >

June 11, 2010

Re: [Pharo-project] GUI Polymorph

by Hilaire Fernandes

Schwab,Wilhelm K a Ã©crit : > Hilaire, > > It was interesting to watch MS' position on GUI examples change over time. Visual C++ started out teaching how to create efficient software. Then one day those examples were gone and all they could talk about was "smooth scrolling" which turned out to be a way to make the machine do the inefficient thing four times instead of once. > > The idea of altering the model, finding out what is invalidated, marking that as closely as can be done within bounds of common sense (or until diminishing returns), and then drawing just the changed parts is non-intuitive and VERY important. You have done a wonderful job so far, but optimization deserves attention. Please fell free to search and to document it. As I wrote in my previous email, my objective writing this documentation was not how to efficiently implement a paint canvas. Hilaire

June 11, 2010

Re: [Pharo-project] Autotest, proof-of-concept [was: About TDD and Pharo]

by Alexandre Bergel

> If you look at Autotest package, AutotestView is just the GUI, so we can implement several GUI and see the best solution. I need to take the time to do it, repository is read / write so feel free to commit :) Today I will not have time, but I will try to implement the "button listener" this week end to see. > What I want to have is a dashboard docked on one side of the screen which acts like you're driving a car. It's always visible, you have to be able to look quickly at it as when you check the speed of your car, adjust your drive, .... I like the idea of dashboard. There is something similar in Eclipse. It is really effective I feel. > Also another problem with the current version if that if a test fails, change it and fails again, you don't see it has run (nothing moves in the GUI). > > Finally, another problem is that you see that a test has failed, but you don't know why (SUnit TestRunner has the same problem). I want to display the exception message too. Yes, that would be interesting. One step forward in that direction is to exploit assert:equal:. We could imagine assert:include: and friends. Oscar proposed something like this some time ago. Cheers, Alexandre > > On 3 Jun 2010, at 17:11, laurent laffont wrote: > > > Hi, > > > > I've written a proof-of-concept for Autotest. Draft/crappy code and no tests (exploration mode :) but it loads on PharoCore-1.1-11383-beta image. > > > > Load it: > > Gofer new > > squeaksource: 'Autotest'; > > package: 'Autotest'; > > load > > > > Open it: > > AutotestView open > > (there's en entry in WorldMenu > Tools) > > > > And change a tested method to see the results. > > > > There's a bug I need to find, maybe someone knows: > > - Change Bag>>occurrencesOf: > > - Autotest gives: > > > > 284 run, 281 passes, 0 expected failures, 1 failures, 2 errors, 0 unexpected passes > > Failures: > > CollectionRootTest>>#test0FixtureIterateTest > > > > Errors: > > CollectionRootTest>>#testBasicCollect > > CollectionRootTest>>#testDoWithout > > > > but in SUnit CollectionRootTest gives > > 0 run, 0 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected passes ?? > > > > > > Cheers, > > > > Laurent Laffont > > > > http://pharocasts.blogspot.com/ > > http://magaloma.blogspot.com/ > > > > > > On Thu, Jun 3, 2010 at 6:09 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > The idea is excellent. > > > > Cheers, > > Alexandre > > > > > > On 3 Jun 2010, at 10:22, laurent laffont wrote: > > > > > > > > > > > On Thu, Jun 3, 2010 at 3:42 PM, Alexandre Bergel <alexandre(a)bergel.eu> wrote: > > > > You may have a lot of noise. > > > > > > > > I guess that Ruby uses files as a unit of development/deployment. The closest Smalltalk/Pharo has is the class and the package. > > > > > > > > I would suggest that TestCase which would use this feature use some pragma/method to identify/declare which classes/packages this test depends upon. Then the "autotest" framework would register such tests and listen for changes in the given classes/packages, launching required tests whenever a change happen. > > > > > > > > Additionally, one could declare such a pragma on a single test method, when this test should be run for a specific class. > > > > > > > > Of course, you also to take care of long running tests, which you probably want to exclude from auto-testing. > > > > > > I see autotest in Pharo in a slighly different way: When I press save in the Monticello browser, I have a popup menu which asks me whether (i) I want to run all the tests or (ii) only the tests that cover that I changed from the last version. > > > > > > Does this make sense? > > > > > > Please no popup :) What I like in ruby autotest is that I can quickly look at test results if I want (or not) without stop writing. Often you want to see your tests failing, as you type / save code. I don't have to stop writing, click a button, wait test results, go again.... testing is done in background and I just see notifications whether it's OK or not. > > > > > > So test log in a Transcript is OK for me. > > > > > > > > > For autotest unit of work is file: it runs the test file which has the same name as the code file, but you can customize this behavior. For autotest-rails: > > > "A simplified version of Autotest heuristics in this mode would be: > > > When changing a test file, only this file is run (e.g. test/unit/foo_test.rb âtest/unit/foo_test.rb). > > > When changing a model file, only associated unit test file is run (e.g.app/models/foo.rb â test/unit/foo_test.rb). > > > When changing a controller file, associated functional test file is run (e.g.app/controllers/foo_controller.rb âtest/functional/foo_controller_test.rb). > > > When changing a fixture file, associated unit test and functional test are run (e.g.app/fixtures/foos.yml â test/unit/foo_test.rb +test/functional/foo_controller_test.rb). > > > When changing a helper file, associated functional test file is run (e.g.app/helpers/foo_helper.rb âtest/functional/foo_controller_test.rb). > > > When changing application_helper.rb file all functional test files are run (e.g.application_helper.rb â test/functional/*_test.rb). > > > When changing a file under the config directory, all tests are run." > > > > > > Laurent > > > > > > > > > > > > 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 > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > 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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

June 11, 2010

Re: [Pharo-project] Autotest, proof-of-concept [was: About TDD and Pharo]

by laurent laffont

On Fri, Jun 11, 2010 at 2:29 PM, Alexandre Bergel <alexandre(a)bergel.eu>wrote: > Hi Laurent, > > I like Autotest. It is true that I always execute the test after modifying > it. > There are three horizontal panes. Why so? Is it just to open a debugger > when necessary? > I want to be able to open a debugger from autotest. I agree the GUI is crap now. > We could imagine one standalone button instead with a green color to say > the test I just edited is green, and yellow or red when it fails. In that > case, clicking on the button open a debugger. > > I just feel the window of autotest takes a lot of space in the screen, > without having a real benefit. > Yes it's true. I'm still thinking on a good GUI. But I'm learning how to make GUI now :) If you look at Autotest package, AutotestView is just the GUI, so we can implement several GUI and see the best solution. I need to take the time to do it, repository is read / write so feel free to commit :) What I want to have is a dashboard docked on one side of the screen which acts like you're driving a car. It's always visible, you have to be able to look quickly at it as when you check the speed of your car, adjust your drive, .... Also another problem with the current version if that if a test fails, change it and fails again, you don't see it has run (nothing moves in the GUI). Finally, another problem is that you see that a test has failed, but you don't know why (SUnit TestRunner has the same problem). I want to display the exception message too. Thanks a lot for feedback. Laurent Laffont http://pharocasts.blogspot.com/ http://magaloma.blogspot.com/ > > Cheers, > Alexandre > > > On 3 Jun 2010, at 17:11, laurent laffont wrote: > > > Hi, > > > > I've written a proof-of-concept for Autotest. Draft/crappy code and no > tests (exploration mode :) but it loads on PharoCore-1.1-11383-beta image. > > > > Load it: > > Gofer new > > squeaksource: 'Autotest'; > > package: 'Autotest'; > > load > > > > Open it: > > AutotestView open > > (there's en entry in WorldMenu > Tools) > > > > And change a tested method to see the results. > > > > There's a bug I need to find, maybe someone knows: > > - Change Bag>>occurrencesOf: > > - Autotest gives: > > > > 284 run, 281 passes, 0 expected failures, 1 failures, 2 errors, 0 > unexpected passes > > Failures: > > CollectionRootTest>>#test0FixtureIterateTest > > > > Errors: > > CollectionRootTest>>#testBasicCollect > > CollectionRootTest>>#testDoWithout > > > > but in SUnit CollectionRootTest gives > > 0 run, 0 passes, 0 expected failures, 0 failures, 0 errors, 0 unexpected > passes ?? > > > > > > Cheers, > > > > Laurent Laffont > > > > http://pharocasts.blogspot.com/ > > http://magaloma.blogspot.com/ > > > > > > On Thu, Jun 3, 2010 at 6:09 PM, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: > > The idea is excellent. > > > > Cheers, > > Alexandre > > > > > > On 3 Jun 2010, at 10:22, laurent laffont wrote: > > > > > > > > > > > On Thu, Jun 3, 2010 at 3:42 PM, Alexandre Bergel <alexandre(a)bergel.eu> > wrote: > > > > You may have a lot of noise. > > > > > > > > I guess that Ruby uses files as a unit of development/deployment. The > closest Smalltalk/Pharo has is the class and the package. > > > > > > > > I would suggest that TestCase which would use this feature use some > pragma/method to identify/declare which classes/packages this test depends > upon. Then the "autotest" framework would register such tests and listen for > changes in the given classes/packages, launching required tests whenever a > change happen. > > > > > > > > Additionally, one could declare such a pragma on a single test > method, when this test should be run for a specific class. > > > > > > > > Of course, you also to take care of long running tests, which you > probably want to exclude from auto-testing. > > > > > > I see autotest in Pharo in a slighly different way: When I press save > in the Monticello browser, I have a popup menu which asks me whether (i) I > want to run all the tests or (ii) only the tests that cover that I changed > from the last version. > > > > > > Does this make sense? > > > > > > Please no popup :) What I like in ruby autotest is that I can quickly > look at test results if I want (or not) without stop writing. Often you want > to see your tests failing, as you type / save code. I don't have to stop > writing, click a button, wait test results, go again.... testing is done in > background and I just see notifications whether it's OK or not. > > > > > > So test log in a Transcript is OK for me. > > > > > > > > > For autotest unit of work is file: it runs the test file which has the > same name as the code file, but you can customize this behavior. For > autotest-rails: > > > "A simplified version of Autotest heuristics in this mode would be: > > > When changing a test file, only this file is run (e.g. > test/unit/foo_test.rb âtest/unit/foo_test.rb). > > > When changing a model file, only associated unit test file is run > (e.g.app/models/foo.rb â test/unit/foo_test.rb). > > > When changing a controller file, associated functional test file is run > (e.g.app/controllers/foo_controller.rb > âtest/functional/foo_controller_test.rb). > > > When changing a fixture file, associated unit test and functional test > are run (e.g.app/fixtures/foos.yml â test/unit/foo_test.rb > +test/functional/foo_controller_test.rb). > > > When changing a helper file, associated functional test file is run > (e.g.app/helpers/foo_helper.rb âtest/functional/foo_controller_test.rb). > > > When changing application_helper.rb file all functional test files are > run (e.g.application_helper.rb â test/functional/*_test.rb). > > > When changing a file under the config directory, all tests are run." > > > > > > Laurent > > > > > > > > > > > > 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 > > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > > > > > > > > _______________________________________________ > > 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 > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

June 11, 2010

[Pharo-project] [update 1.1] #11393

by Marcus Denker

11393 ----- Issue 1589: StandardFileMenu should be removed -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

June 11, 2010

Re: [Pharo-project] seaside.gemstone.com down - unable to build 1.1-dev

by Schwab,Wilhelm K

This is why I want to see separate web images; by not pre-packaging we just transfer the headaches from Pharo's developers to its users, increasing the number of opportunities to have failures, load on servers, etc. Bill -----Original Message----- From: pharo-project-bounces(a)lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Torsten Bergmann Sent: Friday, June 11, 2010 6:53 AM To: pharo-project(a)lists.gforge.inria.fr Subject: [Pharo-project] seaside.gemstone.com down - unable to build 1.1-dev http://seaside.gemstone.com/ss/metacello/ is down, therefore ConfigurationOfPharo can not be used to build Pharo 1.1. from an updated core. See http://downforeveryoneorjustme.com/seaside.gemstone.com Maybe the machine is switched to vmware.com? However - we should again think about reliable infrastructure ... Thx T. -- GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

June 11, 2010