On 30 May 2016 at 12:48, Sebastian Zartner
<sebastianzartner@...400...> wrote:
> On 29 May 2016 at 13:11, Diederik van Lierop <mail@...1689...> wrote:
>> On Sun, May 29, 2016 at 11:46 AM, Sebastian Zartner
>> <sebastianzartner@...400...> wrote:
>>>
>>> > 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.
>>
>>
>> I don't agree with this. [...]
>
> Got the point. So, I'll add the Grids tab back.
On 30 May 2016 at 12:49, Sebastian Zartner <sebastianzartner@...400...> wrote:
> On 30 May 2016 at 04:32, Brynn <brynn@...3133...> wrote:
>>>> On the Page tab, what happened to the Display section, where you can
show
>>>> or
>>>> hide the page border, or disable antialiasing?
>>>
>>>
>>> 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.
>>>
>>>> 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.
>>
>>
>> Respectfully, I disagree.
>>
>> Grids tab:
>> Sometimes I might have 2 or 3 grids in 1 file (although only 1 at a time is
>> visible). But other times, no grids at all. So this is very much a "per
>> document" feature for me.
>
> Convinced, adding the tab back.
While writing this, I forgot about my own suggestion. What about
moving guides and grids into a separate dialog? Doing so, those would
still be document specific though could be adjusted separately from
the general document properties.
(Previously I suggested to move grids + snapping into a combined
dialog, though snapping is not restricted to grids, so it should
rather be kept separate.)
>> --------------------------------------------------
>> From: "Sebastian Zartner" <sebastianzartner@...400...>
>> Sent: Sunday, May 29, 2016 3:46 AM
>> To: "Maren Hachmann" <maren@...3165...>; "Brynn"
<brynn@...3133...>
>> Cc: "Inkscape" <inkscape-devel(a)lists.sourceforge.net>
>> Subject: Re: [Inkscape-devel] [UI] Rework Document Properties dialog
>>
>>
>>> Hi Brynn, hi Maren,
>>>
>>> thank you for the feedback!
>>>
>>> On 28 May 2016 at 12:21, Brynn <brynn@...3133...> wrote:
>>>>
>>>> On the Page tab, what happened to the Display section, where you can
show
>>>> or
>>>> hide the page border, or disable antialiasing?
>>>
>>>
>>> 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.
>>>
>>>> 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.
>>>
>>> On 28 May 2016 at 16:13, Maren Hachmann <maren@...3165...> wrote:
>>>>
>>>> Sebastian, I've seen a lot of people using the 'set page border
color'
>>>> option when they are using a dark background for their drawings.
>>>> Where would that option go? Or did you mean to remove that completely?
>>>
>>>
>>> Well, I imagined this option not to be used often. Though I agree that
>>> with dark backgrounds the contrast may be very low, so people would
>>> like to adjust it.
>>>
>>> As I guess keeping a high contrast is the main reason for having that
>>> option and people are currently required to adjust the border color
>>> accordingly when they set a background color, I see two possible
>>> solutions to improve this:
>>>
>>> 1. Only set the viewport background color and keep the area outside of
>>> it unchanged.
>>> 2. Adjust the border color automatically according to the chosen
>>> background color, so that you always keep a high contrast (like it's
>>> done for the grippies on object selection).
>>>
>>> Having said that, this is probably out of scope for the blueprint, so
>>> I may just add the option back for now.
>>>
>>>> As guides colors are document-specific (as far as I understand), having
>>>> them set in the preferences doesn't make a lot of sense to me. I
imagine
>>>> that the best guide color also depends upon the selected background
>>>> color for the document, and as such should either also be in a separate
>>>> 'Guide' dialog, or stay where it is.
>>>
>>>
>>> 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.
>>>
>>>> The coupling of document units and page size units, mmh. I think it
>>>> would simplify things for new users. For myself, I don't like it too
>>>> much.
>>>
>>>
>>> What are the use cases to adjust them individually?
>>>
>>>> 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!
>>>
>>>> What I always find difficult about these kinds of dialogs, though, is
>>>> that I never know if I need to hit OK for each tab separately, or if it
>>>> will apply for everything I changed in all tabs (different programs do
>>>> this differently). Is there an UI way to make this really obvious?
>>>
>>>
>>> The programs I know on Windows and Linux always accept the whole
>>> preferences when clicking the OK button.
>>> Sometimes there is an additional 'Apply' button, which saves the
>>> settings without closing the dialog. Eclipse has such a button within
>>> its preferences dialog, for example. Though there it's clear that the
>>> 'Apply' button only affects the current options page, as it is
located
>>> within the options area (while the OK button is outside that area, so
>>> it's meant to save all preferences).
>>>
>>>> Will the dialog close automatically upon hitting OK?
>>>
>>>
>>> In accordance to the above, yes, it will close the dialog (as it is
>>> located outside the tabs; normal behavior across programs).
>>>
>>> Sebastian
>>>
>>>> Am 28.05.2016 um 12:21 schrieb Brynn:
>>>>>
>>>>> On the Page tab, what happened to the Display section, where you can
>>>>> show or
>>>>> hide the page border, or disable antialiasing?
>>>>>
>>>>> What is the benefit of moving Grids and Snap tabs to a separate
dialog?
>>>>> Same for Scripting tab?
>>>>>
>>>>> All best, brynn
>>>>>
>>>>> _______________________
>>>>> From: Sebastian Zartner
>>>>> Sent: Thursday, May 26, 2016 4:39 PM
>>>>> To: Inkscape
>>>>> Subject: [Inkscape-devel] [UI] Rework Document Properties dialog
>>>>>
>>>>>
>>>>> Hi all,
>>>>>
>>>>>
>>>>> I took the time to draft a reworked Document Properties dialog.
>>>>>
>>>>>
>>>>> I already created a blueprint for that two years ago:
>>>>>
>>>>>
https://blueprints.launchpad.net/inkscape/+spec/document-properties-rework
>>>>>
>>>>>
>>>>> And now I finally also described my proposal in a bit more detail
>>>>> including
>>>>> some mockups within the wiki:
>>>>>
>>>>>
http://wiki.inkscape.org/wiki/index.php/BlueprintReworkedDocumentProperti...
>>>>>
>>>>>
>>>>> Would be great if someone took the time to review it and give me
some
>>>>> feedback.
>>>>>
>>>>>
>>>>> Thank you in advance,
>>>>>
>>>>>
>>>>>
>>>>> Sebastian
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
------------------------------------------------------------------------------
>>>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>>>>> traffic
>>>>> patterns at an interface-level. Reveals which users, apps, and
protocols
>>>>> are
>>>>> consuming the most bandwidth. Provides multi-vendor support for
NetFlow,
>>>>> J-Flow, sFlow and other flows. Make informed decisions using
capacity
>>>>> planning reports.
>>>>>
https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
>>>>>
>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Inkscape-devel mailing list
>>>>> Inkscape-devel(a)lists.sourceforge.net
>>>>>
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>>>>
>>>>>
>>>>>
>>>>>
------------------------------------------------------------------------------
>>>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>>>>> traffic
>>>>> patterns at an interface-level. Reveals which users, apps, and
protocols
>>>>> are
>>>>> consuming the most bandwidth. Provides multi-vendor support for
NetFlow,
>>>>> J-Flow, sFlow and other flows. Make informed decisions using
capacity
>>>>> planning reports.
>>>>>
https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
>>>>> _______________________________________________
>>>>> Inkscape-devel mailing list
>>>>> Inkscape-devel(a)lists.sourceforge.net
>>>>>
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>>>>
>>>>
>>>>
>>>>
>>>>
------------------------------------------------------------------------------
>>>> What NetFlow Analyzer can do for you? Monitors network bandwidth and
>>>> traffic
>>>> patterns at an interface-level. Reveals which users, apps, and protocols
>>>> are
>>>> consuming the most bandwidth. Provides multi-vendor support for NetFlow,
>>>> J-Flow, sFlow and other flows. Make informed decisions using capacity
>>>> planning reports.
>>>>
https://ad.doubleclick.net/ddm/clk/305295220;132659582;e
>>>> _______________________________________________
>>>> Inkscape-devel mailing list
>>>> Inkscape-devel(a)lists.sourceforge.net
>>>>
https://lists.sourceforge.net/lists/listinfo/inkscape-devel
>>
>>