On 4/7/06, Andrius Ramanauskas <knutux@...400...> wrote:
- 1 step - <switch> support. I already tested prototype of semi-working
switch element support, but there still some work to do. Currently switch element works just like <g>, but I will make it work according to SVG standard - to render only first element which conditional properties evaluate to true (I will implement support for "systemLanguage" property for a start, which will evaluate to true if property is not set or contains current document language).
And the current document language is defined where? Taken from the OS and probably overridden in document properties?
I plan to make SPSwitch a subclass of SPGroup, so user can enter switch element (turn it into a temporery layer, which will show all contained items, not just first)
Making it a subclass of group is OK, but I don't see how this will let you see all variants just by entering it - only by "ungrouping" it, i.e. removing the switch. You will need to implement the non-destructive "see all" method for switch separately.
Even then, I'm reluctant to approve this because it will violate our "correct rendering of SVG" principle. For example a user may give a command to see all in a switch and leave it in that state, forgetting to undo this, in which case our display of that SVG document will remain different from e.g. Batik.
I think the "see all" functionality is still doable, we just need to invent a good unambiguous UI for it.
The rest of your plan looks good. By the way, thanks also for your work on clipping/masking - it's much appreciated!
-- bulia byak Inkscape. Draw Freely. http://www.inkscape.org