Hello all,
I have exposed the SVG Output preferences in a new tab in the preference dialog.
Because of some of the preferences I am not too sure what they do, the tooltip text might be wrong. I hope someone who does know can fix them.
The "allowshorthands" option seems not used anywhere in Inkscape code. Does anybody know what happened with this option? (I have commented it out, so it does not show up in Pref dialog)
Thanks, Johan
J.B.C.Engelen@...1578... wrote:
Hello all,
I have exposed the SVG Output preferences in a new tab in the preference dialog.
Because of some of the preferences I am not too sure what they do, the tooltip text might be wrong. I hope someone who does know can fix them.
The "allowshorthands" option seems not used anywhere in Inkscape code. Does anybody know what happened with this option? (I have commented it out, so it does not show up in Pref dialog)
Indeed, it's not used. I'm not really sure (anymore at least) how it ended up in the preferences file. While working on the code to generate path data with relative commands I considered also letting Inkscape generate path data with shorthands (h/v commands), but finally decided against it because of the increased complexity and very minor gains.
Jasper van de Gronde wrote:
J.B.C.Engelen@...1578... wrote:
Hello all,
I have exposed the SVG Output preferences in a new tab in the preference dialog.
Because of some of the preferences I am not too sure what they do, the tooltip text might be wrong. I hope someone who does know can fix them.
The "allowshorthands" option seems not used anywhere in Inkscape code. Does anybody know what happened with this option? (I have commented it out, so it does not show up in Pref dialog)
Indeed, it's not used. I'm not really sure (anymore at least) how it ended up in the preferences file. While working on the code to generate path data with relative commands I considered also letting Inkscape generate path data with shorthands (h/v commands), but finally decided against it because of the increased complexity and very minor gains.
Was the original idea that we would have different PathString implementations for different path optimisations?
http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/svg/p... http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/svg/p...
Now that I think of it I'm not sure how that would work, but I seem to remember something like that.
Aaron
Aaron Spike wrote:
...
The "allowshorthands" option seems not used anywhere in Inkscape code. Does anybody know what happened with this option? (I have commented it out, so it does not show up in Pref dialog)
Indeed, it's not used. I'm not really sure (anymore at least) how it ended up in the preferences file. While working on the code to generate path data with relative commands I considered also letting Inkscape generate path data with shorthands (h/v commands), but finally decided against it because of the increased complexity and very minor gains.
Was the original idea that we would have different PathString implementations for different path optimisations?
Perhaps, but it definitely wasn't my intention. I used the "allowshorthands" option in much the same way as the option for relative coordinates (but as far as I can remember I only did tried it locally, and current SVN definitely does not use shorthands in any way, shape or form).
http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/svg/p... http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/svg/p...
Now that I think of it I'm not sure how that would work, but I seem to remember something like that.
PathString currently simply uses some dynamic programming to optimize the path data length by using absolute and/or relative coordinates (and eliminating repeated commands).
-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of Jasper van de Gronde Sent: dinsdag 20 mei 2008 11:44 To: Engelen, J.B.C. (Johan) Cc: inkscape-devel@lists.sourceforge.net Subject: Re: [Inkscape-devel] NEW: SVG Output preferences
J.B.C.Engelen@...1578... wrote:
Hello all,
I have exposed the SVG Output preferences in a new tab in
the preference dialog.
Because of some of the preferences I am not too sure what
they do, the tooltip text might be wrong. I hope someone who does know can fix them.
The "allowshorthands" option seems not used anywhere in
Inkscape code.
Does anybody know what happened with this option? (I have
commented it
out, so it does not show up in Pref dialog)
Indeed, it's not used. I'm not really sure (anymore at least) how it ended up in the preferences file. While working on the code to generate path data with relative commands I considered also letting Inkscape generate path data with shorthands (h/v commands), but finally decided against it because of the increased complexity and very minor gains.
Aha! Actually Peter and I were thinking about adding axis aligned path segments to 2geom, which makes the complexity for Inkscape neglegible. It's good that the option is called "Allow..." because indeed I don't think it is worth actively converting lines to axis aligned lines when possible.
Thanks, Johan
J.B.C.Engelen@...1578... wrote:
The "allowshorthands" option seems not used anywhere in
Inkscape code.
Does anybody know what happened with this option? (I have
commented it
out, so it does not show up in Pref dialog)
Indeed, it's not used. I'm not really sure (anymore at least) how it ended up in the preferences file. While working on the code to generate path data with relative commands I considered also letting Inkscape generate path data with shorthands (h/v commands), but finally decided against it because of the increased complexity and very minor gains.
Aha! Actually Peter and I were thinking about adding axis aligned path segments to 2geom, which makes the complexity for Inkscape
neglegible. > It's good that the option is called "Allow..." because indeed I don't
think it is worth actively converting lines to axis aligned lines when possible.
Sure, that wouldn't be any trouble at all. The option was for letting PathString use h/v commands for lines that are horizontal/vertical if it would result in a smaller path data description.
But as I said before, the option isn't used (I only tried this locally) and I have no idea (anymore) how it ended up in the preferences in SVN.
participants (3)
-
unknown＠example.com -
Aaron Spike -
Jasper van de Gronde