Display of text decorations is in trunk and it can display things as
shown in this example:
(Note install the last patch in
https://bugs.launchpad.net/inkscape/+bug/1243401 to see these again, as
a recent change to trunk broke them.)
Text decoration control requires three GUI fields:
Line: NONE, or any combination of: underline, overline, linethrough,
Style: solid, double, dashed, wavy
Color: From Text or (Color setting widget)
I'm thinking about what the GUI should look like to access these. My
first thought was to add them to the "A" (Create and edit text objects)
part of the GUI, since text decoration does not make a lot of sense
without text to decorate, and this sort of thing would be in a part of
the GUI like that in a Word processor. But that part of the GUI is
already packed with options, to the extent that on my computer I can
only see all the options when Inkscape fills the entire screen. If text
decoration was added there, it would never all fit.
So my second thought was to maybe put these in "A (with a wavy line
through it)" as (Create and edit text decorations). That would let it
fit on screen better, at the cost of making the line of icons down the
left side of the screen one longer.
The third option is to add a second line of options to the existing "A".
That would use up more vertical screen space, but it would have the
advantage that all of the text and text decoration formatting options
could be on screen at once. This is more of a departure for the GUI,
since it seems not to happen anywhere else.
(Note: "blink" line type is emulated with a type of double line style.
I don't expect true blink display to be found in many SVG viewers, ever,
so all Inkscape has to do is indicate that it is set.)
Is there at present anything in the Inkscape GUI where a check box
widget is exposed when one of the left side icons is selected? As far
as I could tell all of the widgets exposed by selecting one of those
icons are of the "select one" type.
Manager, Sequence Analysis Facility, Biology Division, Caltech
Is anyone out there secretly working on the symmetry-tool branch?
I've tried to compile recently, but it seems to be suffering some bit
rot. I'm working through errors, but for the moment I'm stumped on what
seems to be a lot of c style object code from the general src breaking
compilation. Any hints?
The one major item that is available in html5
that I miss in Inkscape 48.4 is the drop down menu
feature. I can emulate it of course with a second
(third etc.) copy of the entire index.svg page
with the menu dropped down. It would be cool
however if I could overlay the first page with a
smaller page consisting of just the menu items,
live of course.
Any thoughts on this?
Free list of books for self-publishers:
PDF e-book: "Create Book Covers with Scribus"
Because we're now in the Chill phase of the release cycle, I need to
inquire as to the status of any unfinished features for the 0.91
We still have ample time before the release, but what we want is for any
feature that will take more than a month or two to reach full maturity,
to be postponed for a future release.
If you're working on a feature which you, or someone else, may
legitimately consider to be not "release ready", please let me know
I have been experimenting with adding text-decoration control to the
"Text and Font" dialog. It is working (crudely) except I have not yet
figured out how to remove the
text-decorate property from a "style". That is, to go from:
style="text-decoration: underline wavy
To add this property, or to modify it, this works:
sp_repr_css_set_property(css, "text-decoration", td_full_string);
and these work:
sp_repr_css_set_property(css, "text-decoration", "none");
sp_repr_css_set_property(css, "text-decoration", "inherit");
putting "text-decoration: none" and "text-decoration: inherit" in the
style. But while this looks like it should have eliminated any mention
of text-decoration from the style:
it only succeeded in moving the existing text-decoration from wherever
it was to the end of the style.
In the file src/xml/repr-css.cpp it says that that unset function sets
"inkscape:unset" for that property. Is something else (that I need to
modify?) supposed to see that and then really delete the property? Is
there an sp_repr_css_remove_property() somewhere that I have not found?
Manager, Sequence Analysis Facility, Biology Division, Caltech
It appears that Google will fund up to $500 US for travel
(airplane/train/bus) expenses to send some 2013 GSoC students to LGM
in Leipzig (April 2nd-5th). Students, if you are interested, please fill
out the form at:
Hotel/meal expenses will not be covered but there are cheap hostels near
the meeting site. Google will not be funding mentor travel.
NB. There is currently a cut/paste error on the form. Accommodations in
Phnom Penh are not being provided!
Having been in China for quite a while I understand the situation you're
in using low bandwidth.
It would be way cool to have external style sheet support in Inkscape and
something that has been on my wish list for quite a while, so please
continue. Even if it's ugly coding and creates a performance hit when
loading Inkscape, I think it would be worthwhile to have it. Maybe using a
switch in the prefs to turn it on or off, for performance improvement.
Added to that is another question.
How feasible would it be to use the external style sheet support code
you're currently making to do the same for external <USE
xlink:href="file.svg#objectID"/> ? I have the idea that it would be pretty
similar in scope, reading data from file and changing style attributes for
CSS and reading and adding SVG code to the SVG code in memory (leaving the
file code alone).
If it isn't too much work, could you experiment with it a little to see
how feasible it is? It would kill two BIG flies in one go if it would work
and greatly increase the productivity of Inkscape as an authoring tool.
You'd certainly be one of my hero's if you can make this work in Inkscape.
I can also imagine Tav's Symbol tool to increase usability by using
external links to symbol files rather than embedding them into the code
like it currently does, but that would be food for 0.92 I guess.
Last but not least would be an option to save all linked content into a
single whopper of a file and an option to export all style info and <use>
objects to external files. Hmm,.. you cannot prevent me from dreaming now