October 2008 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] History and SUnit

by Keith Hodges

Oh and in the ss/Testing repo the master packages are still SUnit and SUnitGUI, the "Testing" heirarchy is a proposed reorganisation for the future. Keith

Oct. 2, 2008

Re: [Pharo-project] History and SUnit

by Keith Hodges

StÃ©phane Ducasse wrote: > Thanks > I will have a look. I do not really understand what is written, this > is too cryptic. > Does the framework changes remove the fact that tests should start > with test? > > Stef Yes, although the default behaviour is preserved, TestCase subclasses can publish their own test suites with whatever behaviour they wish. BTW: the framework has changed somewhat since that documentation was written. For example in SSpec "specs" start with spec* the goal is to enable TestRunner to be used as a runner for SSpec as well as SUnit, if I ever get around to it. Keith

Oct. 2, 2008

[Pharo-project] Exupery's VMMaker on SqueakSource now has closures

by bryce＠kampjes.demon.co.uk

I can supply a built VM if anyone wants to try it immediately. If not I'll package one up after finishing tidying up. Looking at the bytecodes, they're suppressing context recycling whenever a closure is created. The only reason that closures refer to their surrounding contexts is to support ^ returns from blocks. With two more context creation bytecodes we should allow all contexts to be recycled except the outer method context when there's a block that ^ returns. Such optimisation can wait though, especially as it would involve removing some of Eliot's sanity checking which may be useful when adapting the image to use these bytecodes. Bryce

Oct. 2, 2008

[Pharo-project] Re: Universe Browser - search

by Dan Corneanu

Just made an update and seen the Univers Browser (enhanced). It seems to have what I wanted :) On Thu, Oct 2, 2008 at 11:46 PM, Dan Corneanu <dan.corneanu(a)gmail.com> wrote: > Hi, > I know it is not decided yet what will pharo use for loading code, but > I would really appreciate a search button in the Univers Browser. > I always find myself lost in the tree. >

Oct. 2, 2008

[Pharo-project] Universe Browser - search

by Dan Corneanu

Hi, I know it is not decided yet what will pharo use for loading code, but I would really appreciate a search button in the Univers Browser. I always find myself lost in the tree.

Oct. 2, 2008

[Pharo-project] Did you harvest Kernel-dc.198

by StÃ©phane Ducasse

Hi marcus did you harvest ? Name: Kernel-dc.198 Author: dc Time: 28 September 2008, 4:00:03 pm UUID: 3b2eeec4-6461-4d22-94d1-e7f692e7e177 Ancestors: Kernel-marcus.denker.197 - M7166: speedup allSelectors add allSelectorsBelow:. Firstly #allSelectors inefficiently creates multiple intermediate collections. Refactoring this yields a 27% speed improvement. Secondly many users of #allSelectors forget that when applied to the class side it doesnt stop at ProtoObject class, it continues to Class ClassDescription, Behavior, Object and ProtoObject. This is catered for by adding #allSelectorsBelow: Magritte and SUnit are heavy users which benefit. I imagine not so I will.

Oct. 2, 2008

Re: [Pharo-project] History and SUnit

by StÃ©phane Ducasse

Thanks I will have a look. I do not really understand what is written, this is too cryptic. Does the framework changes remove the fact that tests should start with test? Stef >> http://wiki.squeak.org/squeak/SUnit%20for%203.10 > > -- > Damien Cassou > Peter von der AhÃ©: Â«I'm beginning to see why Gilad wished us good > luckÂ». (http://blogs.sun.com/ahe/entry/override_snafu) > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 2, 2008

Re: [Pharo-project] Formalised UI

by Gary Chambers

Well, I've done a bit with CSS (3.0) not fully looked though, just enough that our Report Builder file format (XML) is roughly equivalent. Just a thought about states of "widgets" I've seen in the wild... base Morphic doen't honour any of them by default... hence lots of extra code for dealing with interactive states in eveyone's subclasses/overrides. To be fair it is not appropriate to every Morph... just more common with "standard" (if you like) styles of widgets. As for ordinates, it was on IRC with Sig... tricky to track down logs, did find a link for a related dev-list email part of it though: http://www.nabble.com/Re:--squeak-dev--Subcanvas-p18270830.html Gary. ----- Original Message ----- From: "Michael Rueger" <m.rueger(a)acm.org> To: "An open mailing list to discuss any topics related to an open-sourceSmalltalk" <pharo-project(a)lists.gforge.inria.fr> Sent: Thursday, October 02, 2008 6:42 PM Subject: Re: [Pharo-project] Formalised UI > Gary Chambers wrote: >> Just some thoughts picked up over the years. Things that all Morphs >> should have, at least, defaults for... >> >> UI States: > > how does this list compare to the list of possible CSS states? > > >> Transitions would be nice, but might be a bit overboard... Igor and I >> discussed a framework based on 4 dimensional representations being >> function based (I think we coined the phrase "Ordinates"). > > Can you say more about this? > > Michael > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Oct. 2, 2008

Re: [Pharo-project] Formalised UI

by Michael Rueger

Gary Chambers wrote: > Just some thoughts picked up over the years. Things that all Morphs > should have, at least, defaults for... > > UI States: how does this list compare to the list of possible CSS states? > Transitions would be nice, but might be a bit overboard... Igor and I > discussed a framework based on 4 dimensional representations being > function based (I think we coined the phrase "Ordinates"). Can you say more about this? Michael

Oct. 2, 2008

[Pharo-project] Formalised UI

by Gary Chambers

Just some thoughts picked up over the years. Things that all Morphs should have, at least, defaults for... UI States: Enabled Enabled Mouse over Enabled Mouse down inside Enabled Mouse down outside (?) Enabled Selected Enabled Selected Mouse over Enabled Selected Mouse down inside Enabled Selected Mouse down outside (?) Disabled Disabled Mouse over (?) Disabled Mouse down inside (?) Disabled Mouse down outside (?) Disabled Selected Disabled Selected Mouse over (?) Disabled Selected Mouse down inside (?) Disabled Selected Mouse down outside (?) "Inactive" (may be responsive to input, as aside from disabled) (part of non primary, up-front window) (as above) ... Transitions between states ... Perhaps it would be good to have Morph have generalised support for these (the inactive ones I've picked up from the Mac, background windows tend to have their controls in a "relatively passive look" state. Just some thoughts for moving ahead with Polymorph... Transitions would be nice, but might be a bit overboard... Igor and I discussed a framework based on 4 dimensional representations being function based (I think we coined the phrase "Ordinates"). Regards, Gary.

Oct. 2, 2008