Other XML information would be out of place in the context of managing styles. That's why I reckon xml editor / style editor switcher buttons would be useful. ( I just think we need an area to edit other attributes like d="" and transformMatrix="". ) and not think about styles as much.
I'll run through some desired behaviour of the editor.
When the editor is in view, selected objects will automatically open to the element style tab only if there are inline styles specified.
The global styles and possibly external style tabs are highlighted if there are styles in them affecting the selected object.
Within the editor area the style lines affecting the object should be highlighted
that add file button really should be named apply/use external stylesheet. Let me know if more mockups will help visualise this.
On 7/25/06, Meu-07-24 at 13:29 +1000, Andy Fitzsimon wrote:
okay so the title is horrible but take a look at this mockup.
Do we really need separate "XML" and "Style" versions of the tree? I'm not particularly attached to the current XML tree -- it seems like having a single version with the (element, id, class) columns would be fine.
-mental
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQBExPERSuZBmZzm14ERAsWOAJ46ypbfq3YNg0PNkC/oEugwKkTiiwCdEx6o MQdzeLJUatPKxsAlNUZR45c= =ZB8f -----END PGP SIGNATURE-----