On 29 May 2016 at 16:42, Maren Hachmann <maren@...3165...> wrote:
Thanks, Sebastian, for your answers!
Am 29.05.2016 um 11:46 schrieb Sebastian Zartner:
> The display options would be moved to the general 'Preferences'
> dialog, i.e. be made global. I assume there is not much need to set
> them per document. Regarding the page border field, see below.
- For me, the page border is a per-document setting, too... I may work
with things I want to print in one project, and with things that never
leave the svg file in another.
>> What is the benefit of moving Grids and Snap tabs to a separate dialog? Same
>> for Scripting tab?
> Grids and snap options are not document properties in my eyes but
> helper functionality. Also, snapping is rather a global functionality
> than specific to a document.
- While I wouldn't mind the dialog being moved to a different place (if
that makes things easier, and not less accessible), I would mind if the
grid settings there would become global settings instead of per-document
settings. Examples were given by Diederik.
> While the same solution as for the border color might be applied
> (automatically keep a high contrast), I agree that moving them into a
> separate dialog might be a good solution - also in regard of future
> feature additions like allowing to adjust their position precisely
> within that dialog or allowing to define different colors per guide.
> I'll adjust the proposal accordingly.
- We can already define guide colors per guide in 0.91, just like guides
can be labelled. The individual color is not saved, currently, but
that's a bug (of which I can't tell if it has been fixed in trunk yet or
Ah, cool! I didn't know about that feature. (There's no hint that you
can double-click them.)
Still, is there a need for a document-wide color definition for them
in case they would automatically keep a high contrast by default?
>> The coupling of document units and page size units, mmh. I
>> would simplify things for new users. For myself, I don't like it too much.
I'd say not only for new users. I understand the difference between
the two, though it can be quite confusing for users to have two units
fields (especially when they are located on the same tab).
> What are the use cases to adjust them individually?
- In 0.91, I often use px as document units (to prevent a few bugs and
to have more fine-grained control, they are the smallest available unit
- just think of stroke widths, there's a limit to the number of decimal
places after the comma in the entry field).
I'd still like to set the page size for my document in a unit that I can
measure with a real-world ruler, and cut out with a real-world pair of
scissors ;-) . Of course, it would still be possible to switch the unit
twice to get the same result. The automagically adapting number fields
do confuse new users, I think.
So, that's obviously workflow dependent. Regarding your usage of
pixels as units I assume you use integer values for them.
In that case, 0.001 would be more fine-grained than a pixel.
(Btw. my workflow is normally web-based, so I use pixels for both in
I'd like to get some feedback from other people on this before I add
the second field back, as I am not convinced yet that the advantages
of having two fields for them overweight the disadvantages.
>> I like the Licences being put into the Metadata section and
the 'Save as
>> template' option a lot. The change to the colors tab also is really
>> nice. And the cancel button is really useful (so the document will not
>> be resized while you're still entering the values, and you can change
>> your mind, too, without several actions happening in the background).
> Thank you!
- I just realized that there's no free-form licence entry field anymore.
As Inkscape sometimes is a bit late in updating the list of available
licences (I recently read that OSI has created an API for retrieving
info about free licences...), and as it can never list all possible
ones, how will people enter a different licence in your blueprint?
I also realized that after sending my previous mail related to that.
Though the answer to this is pretty simple. The field would be a
combobox, i.e. you could select from existing licenses but also type
in your own URL.