Update keys for 1.0

Bug #1796566 reported by Hachmann
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape-docs
Undecided
Patrick Storz

Bug Description

Collecting info about changed/added shortcuts for 1.0 here.

* Calligraphy Tool:
  A new option to add dots has been added to the tool.
  Click in place without moving the mouse to
  create a dot, Shift+Click to create a larger dot.

* <bind key="r" modifiers="Ctrl,Shift" action="FitCanvasToSelectionOrDrawing" display="true" /> (for both 0.92.x and 1.0)

* new keyboard shortcuts for the on-canvas-alignment

* https://gitlab.com/inkscape/inkscape/compare/1fb5264d...393bb895 (center page in window)

* New Selector dialog: <bind key="q" modifiers="Primary,Shift" action="DialogSelectors" display="true" />
  <bind key="Q" modifiers="Primary,Shift" action="DialogSelectors" />
(https://gitlab.com/Moini/inkscape/compare/c07d8d790a5c73c894b26e39cd869cd5db5f998b...99fa4a496962196fd7f81e978dd82a09f987f14d)

@Eduard Can we have a branch for 1.0 in docs? I'd rather put these in instead of collecting them in a report.

Revision history for this message
Patrick Storz (ede123) wrote :

I'll try to get it done next week.

The statistics which I got sorted out during the hackfest were about the last thing I wanted to finish before branching (maybe inkview, too, but maybe it's also better to keep this exlusive to 1.0 anyway in order not to change packaging for 0.92.x).g

Changed in inkscape-docs:
assignee: nobody → Patrick Storz (ede123)
Revision history for this message
Hachmann (marenhachmann) wrote :

Thank you!

Hachmann (marenhachmann)
description: updated
Revision history for this message
Hachmann (marenhachmann) wrote :

Patrick, what name should the new branch get?

Revision history for this message
Patrick Storz (ede123) wrote :

I'm not sure yet, basically there are two possibilities:
1. Create "master" branch and fork branch for Inkscape 1.0
   once Inkscape itself branches.
2. Create branch for 1.0 and fork "master" branch at some
   point in the future.

Likely it makes more sense to keep in sync with the Inkscape repo, even if it's slightly more work, as at some point we should create a master branch for the documentation repository anyway.

One thing I'm not sure yet (maybe you have a suggestion?) is which version of the docs Inkscape master should point at - latest stable version or a master-specific version?

On the website we likely want the latest stable version when manually following internal links (i.e. 1.0 once it's released)? Or would you start offering keys and similar for 0.92.x and 1.0.x and potentially even master in parallel (might be unnecessarily complex and more confusing then helpful)? (this question is unrelated to help menu entries - they point to specific releases and we only need to remember to update them for 1.0)

Hachmann (marenhachmann)
description: updated
Revision history for this message
Hachmann (marenhachmann) wrote :

As for options 1 or 2, 1 is fine, as it goes along with the main program, and thus is quite logical.
I wouldn't complain about 2, either, though. So, slight tendency to 1.

"One thing I'm not sure yet (maybe you have a suggestion?) is which version of the docs Inkscape master should point at - latest stable version or a master-specific version?"

If there is a master version generated, it could use that. I don't think we really need one on the website, though, if this causes more work.

For normal website links that go to 'keys' without a version number, it would be great to point them to the latest stable, I think that's what it does now.

Hachmann (marenhachmann)
description: updated
Revision history for this message
Patrick Storz (ede123) wrote :

Closing in favor of https://gitlab.com/inkscape/inkscape-docs/documentation/issues/1 (where we can also set an appropriate milestone)

Changed in inkscape-docs:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.