Brennan Young
My feedback
51 results found
-
71 votesBrennan Young
supported this idea
·
-
149 votes
Just a general status update. We are currently and will continuously improve SVG import support in Adobe Illustrator. We are currently working on solving the issues mentioned in this report. Please feel free to open new bug reports here on uservoice if you are experiencing additional/untracked issues.
An error occurred while saving the comment An error occurred while saving the comment Brennan Young
commented
Regarding the use of AI as a dedicated SVG editor, and the possible compromises for other AI features, I would draw attention to the way that Photoshop can operate in various color modes (e.g CMYK, grayscale, RGB...) and in each mode, various editing features are disabled, or modified.
Crucially, if you open an image with a CLUT, Photoshop puts the GUI into indexed color mode automagically. When opening certain file types, Photoshop even asks the user to clarify how the image should be handled.
I know SVG-in-AI is a little different, but my point is that the idea that the GUI can be in a format-specific editing mode is already a precedent which graphics professionals (and creative cloud users) will be familiar with, so it need not be a huge paradigm shift
Perhaps a way to constrain the illustrator UI to SVG-native features would help? e.g. if you open a SVG, you're in SVG mode, or perhaps you check a 'SVG mode' checkbox somewhere, then if you try to apply a non-SVG feature AI warns that it may not turn out as expected unless you save as an AI file. Something like that.
Brennan Young
supported this idea
·
-
26 votes
An error occurred while saving the comment Brennan Young
commented
I think this is a duplicate of https://illustrator.uservoice.com/forums/333657-illustrator-desktop-feature-requests/suggestions/37298245-add-data-attributes-to-elements-for-svg-export which is older and has more votes
Brennan Young
shared this idea
·
-
6 votesBrennan Young
supported this idea
·
-
23 votesBrennan Young
supported this idea
·
-
2 votesBrennan Young
supported this idea
·
-
4 votesBrennan Young
supported this idea
·
-
7 votesBrennan Young
supported this idea
·
-
13 votesBrennan Young
supported this idea
·
-
5 votesBrennan Young
shared this idea
·
-
710 votesCompleted (Comments Open) · 136 comments · Illustrator (Desktop) Feature Requests » User Interface · Admin →
An error occurred while saving the comment Brennan Young
commented
I find it astonishing that anyone can imagine File Versioning could be a viable replacement for Undo History. Versioning and Undo History serve similar goals, but at very different levels.
Versioning is at a higher level of organisation. It's certainly a useful 'import' from the software development world.
But even software developers (who have pioneered and used versioning for many years) don't commit every single keystroke, clipboard operation and micro edit to the version history. Versioning was not created to solve that problem. Software developers still rely on the undo buffer just as much as Illustrator users. Versioning didn't make it obsolete.
Furthermore, a 'commit' should preferably be relatively stable, so that others can pull it and try it out immediately. Devs who make too many commits of micro edits quickly become unpopular! If I wanted to find an old version of a graphic in the history, I'd be utterly dismayed to find that history polluted with dozens of near-identical micro edits. Don't do that. Be a good citizen. Consider that it might be you that has to trawl through your own version history in six months.
Let Undo History handle the low-level edits. Let File Versioning handle the high-level edits.
So, if it's not already loud and clear, we still need the Undo History panel, Adobe.
Brennan Young
supported this idea
·
-
25 votes
An error occurred while saving the comment Brennan Young
commented
Layer does not have a selected property in the object model, but there is "has selected artwork" which might work for you.
You can use a filter reference form (a "whose" clause) to get all the layers with selected artwork. Example:
tell application "Adobe Illustrator"
layers of document 1 whose has selected artwork is true
end tellBrennan Young
supported this idea
·
-
7 votes
An error occurred while saving the comment Brennan Young
commented
SVG export should convert symbols to <use> elements.
-
22 votesBrennan Young
supported this idea
·
-
11 votesNeed More Info · 11 comments · Illustrator (Desktop) Feature Requests » File Save, Import and Export · Admin →
An error occurred while saving the comment Brennan Young
commented
Completely agree with Tim Kelly - it's a significant shortcoming not to support <title> and <description>, but regarding accessibility, I would love to see a way to work with aria roles, tabindexes and accessible names (such as aria-label). A more generally useful approach would be for the Illustrator GUI to support the full range of SVG attributes (including aria).
An error occurred while saving the comment Brennan Young
commented
If I could click the vote button for Edu Couchez' well-considered proposals, I would.
Brennan Young
supported this idea
·
-
14 votes
An error occurred while saving the comment Brennan Young
commented
fillColor and strokeColor sorely missing. These are extremely important. Also graphic styles.
Brennan Young
supported this idea
·
-
4 votesNeed More Info · 3 comments · Illustrator (Desktop) Feature Requests » File Save, Import and Export · Admin →
An error occurred while saving the comment Brennan Young
commented
Hi Dirk,
I ran into this issue trying to make a (flattened) hexagon shape with rounded corners, which could be scaled without changing the stroke width. The 'points' of the hexagon were at the sides.
Can't really see how border-image-slice would help with this, or any shape which is not basically a rectangle.
Brennan Young
shared this idea
·
-
10 votes
An error occurred while saving the comment Brennan Young
commented
Hi Dirk,
As long as the renaming on export is consistent, and predictable, so that when you roundtrip, it doesn't re-encode its own output from the previous export, and so that we have a fighting chance of constructing an id or class identifier algorithmically, then the renaming on export is ok.
I do wonder why 'special' characters are converted to numerical entities. If the exported SVG is tagged as having a utf-8 charset (which it is, if you use Save As... SVG), the only truly forbidden characters are <, >, &, ' and ". All other characters might well be represented in their literal form. No? Some fine-grained control over this behavior would be welcome.
An error occurred while saving the comment Brennan Young
commented
Hi Dirk,
Yes, I've tried using Graphic Styles and yes, they get exported, and yes this is a good start. But the renaming is infuriating.
But we will certainly want to use the same class name on things with *different* graphic styles - or different kinds of drawing object (e.g. text).An error occurred while saving the comment Brennan Young
commented
So compellingly useful, it's astounding that this is not implemented yet.
Also: when importing SVG, Illustrator should not rename the class and id attributes because there might be scripts that depend on those specific names. Current behavior makes roundtrip editing of SVG very impractical.
Brennan Young
supported this idea
·
-
5 votesUnder Review · 8 comments · Illustrator (Desktop) Feature Requests » File Save, Import and Export · Admin →
An error occurred while saving the comment Brennan Young
commented
This is encouraging, Dirk!
I understand the predicament here. As a low-hanging fruit, I suppose a warning alert ("Are you sure you want to trample onwards" with a "don't show this again" checkbox) might appear if you do something in AI which destroys some incompatible third-party structures.
"most-minimal-destructive" sounds great in the long term!
An error occurred while saving the comment Brennan Young
commented
Illustrator seems to wreck a lot of things when importing SVG, regardless of where it originated. Its habit of changing css, classnames etc. is infuriating.
I fully understand there are legacy reasons why this has happened, since Illustrator predates SVG, but it begins to look like poor strategy in the post Flash, responsive-design century.
Illustrator is currently a liability for the integrity of any SVG roundtrip work. It's fine for originating markup, but falls very short if that markup is going to be tweaked or manipulated by other tools.
Brennan Young
supported this idea
·
-
4 votes
An error occurred while saving the comment Brennan Young
commented
Thank you!
Brennan Young
shared this idea
·
I've just been converting some SVG text to foreignObject (so we can have reflow, text spacing, superscripts, lists and whatnot). It occurs to me that if Illustrator is going to support the SVG standard "fully", it will also need to handle foreignObject, i.e. it will need to have some kind of HTML renderer/editor. (In theory, foreignObject can use "any" markup namespace). I consider HTML editing in Illustrator extremely unlikely to appear. But if Illustrator would just keep its fingers out of any foreignObject that would be nice. Further down the line, if there was a way to paste in some HTML markup, and have it come out as foreignObject in the SVG that would be even better, but it's been over five years since full SVG support was requested here.