This probably is a recurring topic, but I didn't find any recent posts about it (only old feature requests #170258 Syntax highlighting in XML editor and #198352 XML window and Layer window (whislist)), so I wanted to ask:

how about syntax highlighting in the XML editor?
Seems to me it would really be helpful, and being a non-programmer, I have the idea (probably ridiculously wrong) that the algorithms are there for the take and should just be copy-pasted into inkscape ?

EDIT: actually, it's especially the "style" properties that are a bit messy to read, other properties are nicely laid out in XML editor.
Maybe just break down the style attribute would be sufficient...

Yes, break out the style values. It would be nice to have an option to split the style values into separate xml attributes to make writing XSLT scripts easier.

Hello

As a side note, in the style attribute, there is so much information or specifications, that at the moment of visualizing in a web browser, it seems to me that it's unnecessary.
To explain me better:


In my opinion, It can be reduced to:


But, of course, for more complex designs, more info about the style may be needed.

And how about of support for CSS code, into Inkscape code? Since already exist support for JavaScript code in some parts of the SVG code.

troyd2010 wrote:Yes, break out the style values. It would be nice to have an option to split the style values into separate xml attributes to make writing XSLT scripts easier.

I think that option already exists, when you save to Optimized SVG. I think there is also something related when setting Inkscape's preferences.

I wonder if it helps to click "This affects me" in the bug report. I always do, hoping that it will gain some importance... Would love syntax highlighting too.

OT
I always thought it matters to click "this affects me too" on the bug report or feature request. (Because otherwise, what's the purpose of that option? Well, I think it does subscribe you to the topic.... But if subscribing is the only reason for it, why not just call it "subscribe"?)

Anyway, there was a rather significant change in 0.91 (how the sliders work for Opacity, Blur, and maybe some others). To me, it's outrageous, and I can't imagine why so many people must have wanted it. It makes those sliders harder to use, instead of easier, to me. As it turns out, the change was made because 1 person wanted it! I don't know if the 1 person who wanted it was the person who programmed it, or if actually 2 people wanted it (the reporter and the coder).

So now, I think it must be there just in case someone wants to use it as a measure for the popularity of the request. But I'm starting to think it doesn't matter much.

This is a part of open source development that's harder for me to understand. It's not necessarily democratic (majority decision, etc.).
/OT

I think clicking on that button increases the 'heat' of the bug, symbolized by the little flame in the bug list.