- Pharo-dev - lists.pharo.org

Re: [Pharo-project] Question about Morphic

by Lukas Renggli

> canvas being actually displayed. It simply try to render everything. > Is my guess right? Can anyone confirm please? > Is there a way to turn this on? In the original implementation whenever a shape was draw, all child shapes were clipped according to the bounds of the parent shape. So the root shape clipped to the bounds of the window. You could test before drawing if the shape is visible at all, however in my experience you do not gain any speed because the graphic engine is much faster at performing such tests. At some points I also experimented with R- and Generalized Search Trees, but I figured out that in most cases it is not worth the troubles. For Mondrian visualization the whole dataset is normally displayed anyway. These kind of trees only bring speed improvement, if typically only a fraction of a huge amount of data is visible, like this is the case in a game world or a CAD application. Cheers, Lukas -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 22, 2009

Re: [Pharo-project] Question about Morphic

by Igor Stasenko

2009/2/22 Alexandre Bergel <Alexandre.Bergel(a)inria.fr>: > Dear All, > > I know some of you are morphic expert :-) > I am still on the quest to make Mondrian usuable in Squeak/Pharo. The > situation is the following: I have a window having scrollbar, and I am > trying to render (using Balloon) something bigger than what the window > can actually display. Balloon seems to not be aware of the part of the > canvas being actually displayed. It simply try to render everything. > Is my guess right? Can anyone confirm please? > Is there a way to turn this on? > Canvas has the clipping capabilities. So, you can send a command to render a rectangle (-1000 @ -1000) corner: (10000 @10000) but depends on canvas clipping area, it will render only part of it. Also, for displaying morphs withing area with scrolling - use a TransformMorph to apply clipping & sroll in view. There are another morphs , ready for use , like ScrollPane > 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 > -- Best regards, Igor Stasenko AKA sig.

Feb. 22, 2009

[Pharo-project] Question about Morphic

by Alexandre Bergel

Dear All, I know some of you are morphic expert :-) I am still on the quest to make Mondrian usuable in Squeak/Pharo. The situation is the following: I have a window having scrollbar, and I am trying to render (using Balloon) something bigger than what the window can actually display. Balloon seems to not be aware of the part of the canvas being actually displayed. It simply try to render everything. Is my guess right? Can anyone confirm please? Is there a way to turn this on? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

Feb. 22, 2009

Re: [Pharo-project] [update] #10241

by StÃ©phane Ducasse

Adrian in 10241 when i did Smalltalk condenseChanges I got a ClassDescription syntax error on the license " use and modification subject to a liberal open source license. See the main Squeak website for details. Unless stated to the contrary, works submitted for incorporation into or for distribution with Squeak shall be presumed subject to the same license. Portions of Squeak are: Copyright Nothing more expected ->(c) 1996 Apple Computer, Inc. Copyright (c) 1997-2001 Walt Disney Company, and/or Copyrighted works of many other contributors. All rights reserved. ' " I think that fixing the condensing is the next key items since now we cannot work with Moose anymore. The changeset is getting too close to the limit. Stef On Feb 21, 2009, at 3:10 PM, Adrian Lienhard wrote: > #10241 > > Issue 167: > - Traits implementation refactoring (no sharing of compiled methods > and source) > - New tests for Traits MOP > > > Since this changes the handling of sources, the following issues with > condensing changes may be resolved: > http://code.google.com/p/pharo/issues/detail?id=466 > http://code.google.com/p/pharo/issues/detail?id=470 > > Can somebody check these issues? > > Adrian > ___________________ > http://www.adrian-lienhard.ch/ > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 22, 2009

Re: [Pharo-project] Getting started

by StÃ©phane Ducasse

Hi david this is strange because on mac I used the squeak 3.9 default setup and I just double click on the core image and this is working. My suggestions are - either use a pharo-dev without updating - or a core and update Can you let us know if this is working for you? Stef On Feb 22, 2009, at 9:59 AM, David Finlayson wrote: > I tried all the suggestions here (abandon the error and continue; > download a one-click source and over write the files with the dev > updates. In both cases, I wound up with an unstable image. I got > further with the second method and used it for a couple of hours, but > I am seeing a lot of errors. For example: errors are raised when I > delete morphs (something to do with the trash can); an error searching > in OB for the word "morph" raised an error in OBEnhancementMetaNode >> > Fan ?? > > I know that you guys are ripping out a lot of cruft in Squeak and > things are understandably unstable right now. You've made great > progress on the UI, that's for sure. I'll come back again when you > release the first stable build in a couple of months. > > Thanks for your work, > > David > > On Sat, Feb 21, 2009 at 7:44 PM, Rob Rothwell > <r.j.rothwell(a)gmail.com> wrote: >> Is this reproducible then? (It is by me!) Should I report it as >> an issue? >> >> Rob >> >> On Sat, Feb 21, 2009 at 9:03 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu >> > >> wrote: >>> >>> I'm glad this came up, because I hit that one too and forgot about >>> it. >>> The other thing I have found is that more recent images are somewhat >>> particular about the VM version - they will freeze if the (Windows >>> is where >>> I have seen it) vm is too old. >>> >>> Bill >>> >>> ---- >>> Wilhelm K. Schwab, Ph.D. >>> bschwab AT anest DOT ufl DOT edu >>> >>> ________________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>> [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Rob >>> Rothwell >>> [r.j.rothwell(a)gmail.com] >>> Sent: Saturday, February 21, 2009 2:15 PM >>> To: Pharo-project(a)lists.gforge.inria.fr; dfinlayson(a)usgs.gov >>> Subject: Re: [Pharo-project] Getting started >>> >>> I get that error with the new 10236 dev image as well; I don't >>> recall >>> getting it with the 10231 dev image. I think it is related to the >>> initial >>> FreeType startup process. >>> >>> Start with a 10236 image, click "abandon" and close the debug >>> window, save >>> the image, close it, and open it again. At least I don't get the >>> error the >>> next time. >>> >>> Rob >>> >>> On Sat, Feb 21, 2009 at 12:21 PM, David Finlayson >>> <dfinlayson(a)usgs.gov<mailto:dfinlayson@usgs.gov>> wrote: >>> What's the trick to getting a pharo image up and running? >>> >>> I tried downloading the pharo-dev image 20231 from the downloads >>> page, >>> then I added SqueakV39.sources from a Squeak image. When I >>> launched I >>> got an error dialog saying: >>> >>> Error: a primative has failed. >>> >>> I was hoping to take a look around at the work you folks are doing. >>> >>> -- >>> David Finlayson >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> >>> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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 >> > > > > -- > David Finlayson, Ph.D. > Operational Geologist > > U.S. Geological Survey > Pacific Science Center > 400 Natural Bridges Drive > Santa Cruz, CA 95060, USA > > Office: 831-427-4757 > Lab: 831-427-4462 > Fax: 831-427-4748 > E-mail: dfinlayson(a)usgs.gov > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Feb. 22, 2009

Re: [Pharo-project] Tagging methods for expected lint failures

by StÃ©phane Ducasse

On Feb 22, 2009, at 12:52 AM, Lukas Renggli wrote: > Normally yes, it should work. However some lint rules don't work on a > single method but on a class or multiple classes. In these cases the > pragmas don't really work and scale well. I could think of a solution > here, but this is not implemented yet. > > In any case, if there is something wrong with the marking please > report to me. Even if this is in the base code for more than a year, > it is quite rarely used. As I said I prefer to fix the issues. :) me too but the problem is that some rules are too broad. So we will learn and improve. Stef > > > Also I started to exclude certain rules by default. For example, it > always complained about ever single test method that it is never sent. > So this test is not run on subclasses of TestCase anymore. > > Lukas > > On Sat, Feb 21, 2009 at 10:00 PM, StÃ©phane Ducasse > <stephane.ducasse(a)inria.fr> wrote: >> I hope so because I started to do use. >> >> >> On Feb 21, 2009, at 5:56 PM, Adrian Lienhard wrote: >> >>> I've looked at some of the "Message sent but not implemented:" >>> issues >>> that Damien created. In tests where classes and methods are >>> created at >>> runtime, Lint incorrectly complains. >>> >>> Do we use pragmas to mark the expected failures (see http://www.lukas-renggli.ch/blog/ignoring-lint-rules)? >>> Is this lint pragma honored by the version of Lint that we use? >>> >>> Adrian >>> ___________________ >>> http://www.adrian-lienhard.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 >> > > > > -- > 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 >

Feb. 22, 2009

Re: [Pharo-project] Getting started

by StÃ©phane Ducasse

what is important is to see if the update is working on the core. We do not check if the update works when the tools and all the packages are loaded. Stef On Feb 22, 2009, at 4:44 AM, Rob Rothwell wrote: > Is this reproducible then? (It is by me!) Should I report it as an > issue? > > Rob > > On Sat, Feb 21, 2009 at 9:03 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu > > wrote: > I'm glad this came up, because I hit that one too and forgot about > it. The other thing I have found is that more recent images are > somewhat particular about the VM version - they will freeze if the > (Windows is where I have seen it) vm is too old. > > Bill > > ---- > Wilhelm K. Schwab, Ph.D. > bschwab AT anest DOT ufl DOT edu > > ________________________________________ > From: pharo-project-bounces(a)lists.gforge.inria.fr [pharo-project-bounces(a)lists.gforge.inria.fr > ] On Behalf Of Rob Rothwell [r.j.rothwell(a)gmail.com] > Sent: Saturday, February 21, 2009 2:15 PM > To: Pharo-project(a)lists.gforge.inria.fr; dfinlayson(a)usgs.gov > Subject: Re: [Pharo-project] Getting started > > I get that error with the new 10236 dev image as well; I don't > recall getting it with the 10231 dev image. I think it is related > to the initial FreeType startup process. > > Start with a 10236 image, click "abandon" and close the debug > window, save the image, close it, and open it again. At least I > don't get the error the next time. > > Rob > > On Sat, Feb 21, 2009 at 12:21 PM, David Finlayson > <dfinlayson(a)usgs.gov<mailto:dfinlayson@usgs.gov>> wrote: > What's the trick to getting a pharo image up and running? > > I tried downloading the pharo-dev image 20231 from the downloads page, > then I added SqueakV39.sources from a Squeak image. When I launched I > got an error dialog saying: > > Error: a primative has failed. > > I was hoping to take a look around at the work you folks are doing. > > -- > David Finlayson > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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

Feb. 22, 2009

Re: [Pharo-project] Getting started

by Marcus Denker

On 22.02.2009, at 09:59, David Finlayson wrote: > I tried all the suggestions here (abandon the error and continue; > download a one-click source and over write the files with the dev > updates. In both cases, I wound up with an unstable image. I got > further with the second method and used it for a couple of hours, but > I am seeing a lot of errors. For example: errors are raised when I > delete morphs (something to do with the trash can); an error searching > in OB for the word "morph" raised an error in OBEnhancementMetaNode >> > Fan ?? I have added reports for those at http://code.google.com/p/pharo/issues/list Thanks! Marcus -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 22, 2009

Re: [Pharo-project] What about #ifNotNil and #ifNotNilDo:

by Lukas Renggli

Yeah, simply don't use #ifNotNilDo: and friends. If you follow the coding conventions of Seaside your code will basically run anywhere <http://www.seaside.st/community/conventions>. Slime also contains rules to automatically refactor non-portable code, for example: ansiCompatibilityConditionals ^ self rewrite: #( " kill abnormalities " ('``@boolean ifNotNilDo: ``@block' '``@boolean ifNotNil: ``@block') ('``@boolean ifNotNilDo: ``@block1 ifNil: ``@block2' '``@boolean ifNotNil: ``@block1 ifNil: ``@block2') ('``@boolean ifNil: ``@block1 ifNotNilDo: ``@block2' '``@boolean ifNil: ``@block1 ifNotNil: ``@block2') " normalize arguments " ('``@boolean ifNotNil: [ | `@temps | ``@body ]' '``@boolean ifNotNil: [ :arg | | `@temps | ``@body ]') ('``@boolean ifNotNil: [ | `@temps | ``@body ] ifNil: ``@block ' '``@boolean ifNotNil: [ :arg | | `@temps | ``@body ] ifNil: ``@block') ('``@boolean ifNil: ``@block ifNotNil: [ | `@temps | ``@body ]' '``@boolean ifNil: ``@block ifNotNil: [ :arg | | `@temps | ``@body ]')) methods: false name: 'ANSI Compatibility: Conditionals' Cheers, Lukas On Sun, Feb 22, 2009 at 10:22 AM, Marcus Denker <denker(a)iam.unibe.ch> wrote: > > On 21.02.2009, at 18:31, Damien Cassou wrote: > >> Hi, >> >> is there a way to get the #ifNotNilDo: behavior to write compatible >> Squeak and Pharo code? >> > > -> do not use ifNotNilDo: > -> use ifNotNil: without the argument. > > The real fix of course would be for Squeak adopting the optinal args > changeset > (this is from 2007...) > > Marcus > > -- > Marcus Denker -- denker(a)acm.org > http://www.marcusdenker.de > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli http://www.lukas-renggli.ch

Feb. 22, 2009

Re: [Pharo-project] Getting started

by Marcus Denker

On 22.02.2009, at 09:59, David Finlayson wrote: > I tried all the suggestions here (abandon the error and continue; > download a one-click source and over write the files with the dev > updates. In both cases, I wound up with an unstable image. I got > further with the second method and used it for a couple of hours, but > I am seeing a lot of errors. For example: errors are raised when I > delete morphs (something to do with the trash can); an error searching > in OB for the word "morph" raised an error in OBEnhancementMetaNode >> > Fan ?? Ups. Normally the images are very usable... we need to look at how these problems where introduced in the last ones. > > > I know that you guys are ripping out a lot of cruft in Squeak and > things are understandably unstable right now. You've made great > progress on the UI, that's for sure. I'll come back again when you > release the first stable build in a couple of months. > I hope it's weeks, not months... Marcus > Thanks for your work, > > David > > On Sat, Feb 21, 2009 at 7:44 PM, Rob Rothwell > <r.j.rothwell(a)gmail.com> wrote: >> Is this reproducible then? (It is by me!) Should I report it as >> an issue? >> >> Rob >> >> On Sat, Feb 21, 2009 at 9:03 PM, Schwab,Wilhelm K <bschwab(a)anest.ufl.edu >> > >> wrote: >>> >>> I'm glad this came up, because I hit that one too and forgot about >>> it. >>> The other thing I have found is that more recent images are somewhat >>> particular about the VM version - they will freeze if the (Windows >>> is where >>> I have seen it) vm is too old. >>> >>> Bill >>> >>> ---- >>> Wilhelm K. Schwab, Ph.D. >>> bschwab AT anest DOT ufl DOT edu >>> >>> ________________________________________ >>> From: pharo-project-bounces(a)lists.gforge.inria.fr >>> [pharo-project-bounces(a)lists.gforge.inria.fr] On Behalf Of Rob >>> Rothwell >>> [r.j.rothwell(a)gmail.com] >>> Sent: Saturday, February 21, 2009 2:15 PM >>> To: Pharo-project(a)lists.gforge.inria.fr; dfinlayson(a)usgs.gov >>> Subject: Re: [Pharo-project] Getting started >>> >>> I get that error with the new 10236 dev image as well; I don't >>> recall >>> getting it with the 10231 dev image. I think it is related to the >>> initial >>> FreeType startup process. >>> >>> Start with a 10236 image, click "abandon" and close the debug >>> window, save >>> the image, close it, and open it again. At least I don't get the >>> error the >>> next time. >>> >>> Rob >>> >>> On Sat, Feb 21, 2009 at 12:21 PM, David Finlayson >>> <dfinlayson(a)usgs.gov<mailto:dfinlayson@usgs.gov>> wrote: >>> What's the trick to getting a pharo image up and running? >>> >>> I tried downloading the pharo-dev image 20231 from the downloads >>> page, >>> then I added SqueakV39.sources from a Squeak image. When I >>> launched I >>> got an error dialog saying: >>> >>> Error: a primative has failed. >>> >>> I was hoping to take a look around at the work you folks are doing. >>> >>> -- >>> David Finlayson >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> >>> Pharo-project(a)lists.gforge.inria.fr<mailto:Pharo-project@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 >> > > > > -- > David Finlayson, Ph.D. > Operational Geologist > > U.S. Geological Survey > Pacific Science Center > 400 Natural Bridges Drive > Santa Cruz, CA 95060, USA > > Office: 831-427-4757 > Lab: 831-427-4462 > Fax: 831-427-4748 > E-mail: dfinlayson(a)usgs.gov > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Marcus Denker -- denker(a)acm.org http://www.marcusdenker.de

Feb. 22, 2009