As requested by Martin Owens here: http://sourceforge.net/p/inkscape/mailman/message/34734828/ Currently, either possible by multi-difference extension or by duplicating topmost object and repeating, which can be annoying... Combining can easily be chained afterwards or before, if you want a combination. As it's destructive, it would be nice to leave that out of the 'multi' process and let the user decide. Possible to do the same for the remaining two-paths-only operations.
one of the last proposals I made for the new gradient editor * the button "extract" with the color picker in it is a feature I imagined as following: you import a bitmap image to Inkscape then select it and click on the button so Inkscape will extract a color palette from the image and present them as color stops of a gradient.
a mockup i did for some features i wanted us to have in the new revamped gradient editor mike was developing. at the end we didnt incoporate all the features above but am hoping someone will did in the near future.
Concept to improve the Document Properties panel. Relocates scale controls to a new tab and exposes the resize page tools for easier access and smaller total panel size.
Shows the online canvas branch and the ideas we could play with here.
We find several usability issues on current tools placements and organization. There are too many options at plain sight, with a questionable or difficult to understand organization and with no apparent hierarchy. We’ll make a proposal that involves grouping similar tools, organizing them with some kind of hierarchy and displaying options and parameters consistently.
Inkscape UI mockup based on the gnome design team mockups for designing software
proposal for a horizontal list of stops in the new gradient editor to save space in the dialog.
I recently found Martin Owen's brilliant 'On Canvas Alignment' proposal https://www.youtube.com/watch?v=Wk_wf1heHF4 It's a great idea but suffers from some issues, e.g. visual clutter and focus on alignment points rather than lines. I took his idea and did some thinking of my own.
Here is a UI flow diagram of the proposed Style and CSS dialogs. These are just my initial thoughts, and some questions that came to mind when figuring out the flow.
UI proposal for meassure segments LPE
my proposal for a draggable list of color stops in the new gradient editor.
i proposed this to save space, make it familiar and retain the extra special functions Inkscape has over other vector tools. for the pattern, we could do this and display a default pattern or if it's possible we could show the actual pattern used in the shape.
Could be for a loading screen, and also a thumb up to stop climate change. I have problems whith SMIL in firefox, better view in Chromium/Chrome
I proposed this as a more familiar and intuitive node workflow compared to the current filter editor one
cursors i designed for the new gradient editor to ease its discoverability
This is a demo video for an addon that uses inkscape to create a floating UI in blender with hitboxes fo rselecting parts of your rig/character
A full site-wide map showing all the major pages. * Dark grey is all CMS, edit live, this is content that should abide a standard set of styles and contain mostly written content with a few visual plugins like the shield (front page), recent-news (front page), pictures, links etc. * Light grey and green are non-cms content, which means the templates must be edited in the repository and can contain their own style sheets. - Light grey is user pages, which means most of these functions and pages are specific to that user or the user processes. - Green pages are all functions which are the same for all users, but are fully generated content. Mostly lists of news, galleries and similar. * Red is admin pages, these mostly use the django-admin style sheet and this isn't a bad thing to continue to use. They're the least concerning. * Purple are the legacy docs from the previous website. We need to have a discussion with the docs team (if there is anyone left in that team) about if these docs should be in the cms or not. It might be better to have them in since we'd get more translations. But we should link to them more too from other pages. * there's some light grey pages too, some system stuff.
A video showing the new inkscape mirror system.
After apply deconstruct, same visual
This is a mockup of an interactive alignment preview.
We find the current layout structure a bit chaotic. Grouping the type of content and functionalities provided to the user will greatly facilitate his tasks. Defining areas can facilitate the user recognizing what he need without using his memory. We’ll discriminate between tools, subtools, panels and info
This is a UI flow diagram of the new proposed behaviour of Stroke to Path. This document also contains Use case testing steps and results. Please download this svg to view it properly in Inkscape. Any additional use cases, please email them to me and I'll add them in. Thanks. -C