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

Re: [Pharo-project] Call for UI gripes
by Bill Schwab Feb. 10, 2009

Feb. 10, 2009

Sig, Is it something that could be themed? Then it could be present in the "expensive" themes and left out for a limited theme that would hopefully still look nice, have robust focus behavior, but seeks to be as fast as possible. Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> siguctua(a)gmail.com 02/10/09 7:11 AM >>> 2009/2/10 David RÃ¶thlisberger <squeak(a)webcitas.ch>: > Hi Igor, > >> OB is quite complex thing, and its hard to understand what it does for >> outsider :) >> >> I just identified a few points, which can improve rendering speed by a >> certain amount: > [...] >> - default. >> 60 ms >> >> - with override in SystemWindow>>drawDropShadowOn: aCanvas to do nothing: >> 51 ms >> >> - with override in OBMonticelloPackageNode>>classCategories to return >> cached collection >> 45 ms >> > > I incorporated into OB a patch that is following your idea concerning caching of > class cats in package nodes. I did it differently than you but the results are even > better now. > Great! In my patch i didn't care about correctness or whatever, it was simply to outline what possible can be done to improve rendering speed. > Can you take care of integrating the SystemWindow patch into Pharo? > you mean override of SystemWindow>>drawDropShadowOn: ? Its not really correct override. Shadow should be drawn, if it there. And by default , to draw shadow, it using Morph>>drawOn: method with special shadow canvas. For system window it means that a rectangular area with dimensions of morph is filled with shadow color, shifted by shadowOffset. To improve its speed, we could clip a shadow rectangle to not visit pixels which is covered my system window contents, only pixels which are outside of it and 'dropping' shadow. I can implement such method, but concerning integration - i'm not in charge here :) What is interesting about shadows, that by default a shadow offset is 1 pixel wide: shadowOffset: 1@1 this means that unless you using magnifying glass on you display, you can't really tell if there shadow drawn or not. Since visual difference is minimal, do anyone can tell, why wasting so much CPU cycles on it? :) > Thanks, > David > > _______________________________________________ > 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. _______________________________________________ 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] [ANN][Dev-Images] February 2009 versions
by Bill Schwab Feb. 10, 2009

Feb. 10, 2009

Damien, Is there a Pharo-web link? Apologies if I'm missing the obvious. Thanks! Bill Wilhelm K. Schwab, Ph.D. University of Florida Department of Anesthesiology PO Box 100254 Gainesville, FL 32610-0254 Email: bschwab(a)anest.ufl.edu Tel: (352) 273-6785 FAX: (352) 392-7029 >>> damien.cassou(a)gmail.com 02/10/09 5:57 AM >>> Hi, I've just uploaded new dev and web images based on Squeak3.9.1-7075, Squeak3.10.2-7179 and Pharo0.1-10231. More information and download: http://damiencassou.seasidehosting.st/Smalltalk/squeak-dev Pharo-based images can be downloaded at: http://code.google.com/p/pharo/wiki/Downloads?tm=2 Download statistics at http://damiencassou.dabbledb.com/publish/dev-imagesdownloads Changes in this version: --------------------------- - Pharo images are based on version 10231 - Polymorph fixes (by Gary Chambers) - OmniBrowser changes (by David RÃ¶thlisberger) - Refactored auto-selection of list items to be easier extensible - Extended and improved traits integration (various new features) - Integrated OB patches done by various people - Improved compatibility to Polymorph (button colors, scrollbars) - Several defects corrected - Magritte and Pier have been updated to version 1.1 (by Lukas Renggli and Tudor Girba) Contained packages: ------------------------ This image contains the following packages (some packages are only in the squeak-web image or 3.10-based images): Aida version 5.6 Algernon version 1.2 AST version 160 AutomaticMethodCategorizer version 0.25 AutomaticMethodCategorizerOB version 0.2 DynamicBindings version 2.7 eCompletion version 0.102 eCompletion-Traits version 0.1 eCompletionOmniBrowser version 0.5 Installer version 4.3.284 KomHttpServer version 7.0.30 KomServices version 1.12 Magritte-Model version 1.1.331 Magritte-Seaside version 1.1.283 Magritte-Tests version 1.1.148 OB-Enhancements version 0.292 OmniBrowser version 0.436 OmniBrowser-Algernon version 0.5 OmniBrowser-Full version 0.27 OmniBrowser-Morphic version 0.74 OmniBrowser-Refactory version 117 OmniBrowser-Regex version 0.9.1 OmniBrowser-Standard version 0.389 Pier version current Pier-Blog version 1.1.103 Pier-Documents version 1.1.7 Pier-EditorEnh version 1.1.17 Pier-Model version 1.1.263 Pier-Seaside version 1.1.331 Pier-Security version 1.1.119 Pier-Tests version 1.1.116 Polymorph EventEnhancements version 1.1 Polymorph Geometry version 1.1 Polymorph TaskbarIcons version 1.0 Polymorph ToolBuilder version 1.2 Polymorph Tools Diff version 1.3 Polymorph Widgets version 1.3 Refactoring Core version 17 RoelTyper version 0.60 RSRSS2 version 2.8.3.11 Scriptaculous version 2.8.3.242 ScriptManager version 0.6 Seaside version 2.8.3.572 Seaside-Adapters-Core version pmm.2.mcz Seaside-Adapters-Swazoo version 9 Seaside-Squeak-Adapters version pmm.3.mcz SeasideAdaptersCompatibility version pmm.1.mcz Shout version 3.15-tween.72 ShoutWorkspace version 1-tween.4 SmaCC runtime version 13 Sport version 2.31 Squeak dev packages version 0.27 Squeak dev packages beta version 0.32 Squeak web packages version 0.2 SUnit-improved version 4.0.118 SUnitGUI-improved version 4.0.50 Swazoo version 2.1 Universes version 51 Universes OmniBrowser version 0.38 VBRegex version 1.9 YAXO version 14 -- Damien Cassou http://damiencassou.seasidehosting.st _______________________________________________ Pharo-project mailing list Pharo-project(a)lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

2 1

[Pharo-project] Plugin organization
by Michael Rueger Feb. 10, 2009

Feb. 10, 2009

Hi all, while working on a new (Open)Sophie release I ran into the problem of where to put some plugin code. In this case it is for the Curl Plugin, which Steven Riggins ported into Sophie, but the problem is pretty common I would guess. So the problem is this (as illustrated using our Curl package): - we have a package Sophie-Curl, which includes the Squeak Curl client and the CurlPlugin class. - loaded into a "normal" image, the CurlPlugin ends up being a subclass of ProtObject as the superclass is missing. - now we separate it into Sophie-Curl and Sophie-Curl-Plugin, but that won't fly with the MC name matching - so we name it Sophie-Curl and Sophie-Plugin-Curl I think that is ugly. What I would like to propose is that we organize all plugins in Pharo in to a Plugin category. So we would then have "Plugin-Curl", "Plugin-Locale" etc. Or alternatively "Plugin-Network-Curl", "Plugin-System-Locale" etc. That would also allow to simply load all plugins into a VMMaker image by using a package "Plugin". What do you guys think? Michael

7 24

[Pharo-project] 519: Can't pass a script to the VM
by Damien Cassou Feb. 10, 2009

Feb. 10, 2009

http://code.google.com/p/pharo/issues/detail?id=519 -- Damien Cassou http://damiencassou.seasidehosting.st

2 1

[Pharo-project] Tests are back to dark red :(
by Adrian Lienhard Feb. 10, 2009

Feb. 10, 2009

I run all the tests in #10231: 2910 run, 23 failures, 33 errors Many of the errors and failures are from PCCByLiteralsTest. Was this introduced recently? Are these tests supposed to run green? Please help to improve the test results. Some time ago we managed to get down to only 5 or so failures, now we are back at 56 errors and failures! Cheers, Adrian PS: there are also Undeclared references and the tests don't run through because a method was deprecated that is still called. ___________________ http://www.adrian-lienhard.ch/

5 8

[Pharo-project] Swazoo 2.2beta3 with class variable patch
by Janko MivÅ¡ek Feb. 10, 2009

Feb. 10, 2009

Hello, I just released new beta of Swazoo which has a problem with Singleton class variable solved. Note also that two classes are renamed: Site to SwazooSite and Resource to SwazooResource. I recommend to rename them manually before loading this new beta over. Just in case. New beta is published to http://www.swazoosource.com/Swazoo.html . This beta is the last before final 2.2. release. If it will prove reliable it will be released in few day. Best regards Janko -- Janko MivÅ¡ek AIDA/Web Smalltalk Web Application Server http://www.aidaweb.si

2 3

[Pharo-project] [ANN] prebuild image #10231
by Marcus Denker Feb. 9, 2009

Feb. 9, 2009

http://gforge.inria.fr/frs/download.php/17057/Pharo0.1Core-10231.zip ------------------------------------------------------ update10226 - Issue 483: [Pending Etoy Cleaning] Morph>>actorState remove actorState ------------------------------------------------------ update10227 ssue 482: [Pending Etoy Cleaning] Object>> uniqueNameForReferenceOrNil ------------------------------------------------------ update10228 Monticello merged loader changes (mike rueger) MonticelloConfigurations merged with impara MonticelloConfigurations- jl.43 mainly adds "atomic" loading ScriptLoader adding configuration map loading support ------------------------------------------------------ update10229 Network packages reorganisation by mike rueger - loaded as MCConfig ------------------------------------------------------ update10230 Issue 506: fix: remove #baseUniclass Issue 508: fix: clean StandardScriptingSystem more Issue 507: remove #setNumericValue: ------------------------------------------------------ update10231 -------------- Small Etoy cleanup -> remove class Player -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

3 2

Feb. 9, 2009

When you drag and drop a cs file you get a DN callGetMimeTypeOrNilForFileExtension: http://code.google.com/p/pharo/issues/detail?id=510 Stef

2 1

[Pharo-project] Concerning issue #264
by Igor Stasenko Feb. 9, 2009

Feb. 9, 2009

Hi Markus, i have some comments about morphs :) To my personal feel, a drop shadow feature (and all what is connected with it) is quite controversial, i don't think its worth promoting hasDropShadow shadowOffset to ivars. Instead, i think its worth demoting these ones to a void! :) Can anyone tell me why morph (and moreover - canvas) should be aware of a shadows effect? And what if i want a glow effect instead? Will you extend/expand both morphs/canvas protocol to support it too? Will you sacrifice ivars for it? :) What if tomorrow i want another myCoolSpecialEffect to be there? Will you force a Morph and Canvas be aware of that? I think no. I think all special effects should be a) removed b) reintroduced using different means. No Morph (abstract class) should be aware of any special effects, like it currently hardcoded in #fullDrawOn: self hasDropShadow ifTrue: [self drawDropShadowOn: aCanvas]. (self hasRolloverBorder and: [(aCanvas seesNothingOutside: self bounds) not]) ifTrue: [self drawRolloverBorderOn: aCanvas]. i think such code is candidate for removal. Instead, if we need to, we could simply put: self drawSpecialEffectsOn: aCanvas. -- Best regards, Igor Stasenko AKA sig.

2 2

[Pharo-project] [update] #10231
by Marcus Denker Feb. 9, 2009

Feb. 9, 2009

10231 ==== Small Etoy cleanup Class removed: Player Methods removed: SmallInteger #uniqueNameForReference PasteUpMorph #printScriptSummary SmartRefStream #restoreClassInstVars ScriptLoader #cleanUpEtoys Presenter #goButtonState: #reportPlayersAndScripts #startRunningScripts #startRunningScriptsFrom: #uniclassesAndCounts -- Marcus Denker -- denker(a)iam.unibe.ch http://www.iam.unibe.ch/~denker

1 0