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" <[EMAIL PROTECTED]>
To: "An open mailing list to discuss any topics related to an
open-sourceSmalltalk" <[email protected]>
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
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
