Kim Yoonmi 김윤미 金潤美 Surname first
My feedback
4 results found
-
155 votes
The latest Beta build 29.0.0.9 now allows us to create a gradient from selected swatches, using two ways:
- Select swatches you need (use Cmd/Ctrl to select several) and drag-n-drop them onto the gradient strip in Gradient panel.
- Select swatches you need and choose the new 'Gradient from Swatches Selection' command from the Swatches panel’s flyout menu.
In both cases new gradient stops will be spread uniformly, using the current order of swatches in the panel (not the order of selection).
If you have artwork selected in the document while doing this, the gradient will be automatically applied to it.
Please try the feature and comment back.
An error occurred while saving the comment An error occurred while saving the comment I can't get the script suggested to work regardless on my machine, and I do think it should be native to Illustrator in the first place and also easily accessible in the ways I listed. (the 2 ways listed). I can mock up the wireframes too.
I know how to do the UX for it. I think the scripting UX , as shown is awkward in the first place.
Being able to right click and being able to access it from a menu would help.
The stack exchange scripting idea doesn't work either since it's asking to "repeat the same colors" and "Why don't you use a script?" But a script doesn't always work and for some people they can't use one... so... I think making it native would make it easier.
Right click--> "Make gradient from Swatches" --> Goes to gradient panel. The math is done for you.
Hamburger swatches Menu--> "Make gradient from swatches"-->Goes to gradient panel.
You can then drag and drop gradient to the swatches panel.
Say I've picked up 13 key colors. That's really hard to math out of 100, no?
But these 13 key colors are throughout the whole document and you want to make a gradient, sitting there and mathing 13/100 would be hard.
7.69230769231 >.< Who wants to sit there for an hour to math that with the sliders? Make it easier on the graphic designers. Key colors used throughout the piece, unify into a gradient. The sliders are also finnicky sometimes and moves a degree off. TT Anything over 3-4 and it's harder to place colors.
Just make it native.
An error occurred while saving the comment Automatically create gradient from swatches (Yes I know there is a plug-in. It won't work on my machine and I think this should be native and then it might be able to expand the capabilities of the swatches panel from there?)
So say you have 10 colors, I don't want to have to sit there dividing 10 colors already in the swatches panel. If I select the folder or a range of them, I should be able to right click and then select "create gradient" menu comes up.
Or be able to select it from the Swatches hamburger menu (both would be great)
Then it evenly spaces the colors from the swatches.
2 colors? 2 sliders at 100 and 0
3 colors? 3 sliders at 100, 50 and 0.
... etc.No need to do the math and get it imperfect. 20 colors? No sweat. Currently Sit there and cry...
A rainbow swatch creation: Easy under the new proposal
Under the current system: Sit there and calculate the number, and math it wrong and then cry.I frequently have to make gradients, so this would be great to have. It would also encourage me to use the swatches palette.
Also, it would make it easier to pull colors from a gradient this way. I know what the base color is already because I used a color/folder to create the gradient in the first place. (I often have to tweak gradients and this is a pain.)
-
145 votes
The 29.1 general release now allows to add gradient and pattern swatches into color groups.
An error occurred while saving the comment I need the organization. PLLLLEEEAASSSEE. It's a pain having to click through swatches, not sure which one is the one I want, even if I name them all.
-
6 votes
Since version CS6, Illustrator allows to align gradients on strokes with a dedicated set of Align Stroke buttons in the full expanded Stroke panel.
-
2 votes
I think being able to recover the gradient and specific colors later would be important.
@Saurav
But here are some ways to fix it without the "extra steps":
1. There is an idea with the swatch to do something like Photoshop where it remembers X amount of colors from dropper tool. If you implement that *at the same time* as this idea, then implementation of both won't be as difficult.
Personally, I would think given the infrastructure of AI and the fact it is vector, this idea would be much more easy to implement than it was in Photoshop.
2. For users, doing both isn't a bad idea?
Redundancy in UX is often the gold standard and why cut off one option when you could easily have both, especially if you do the previous idea of previous colors used. If you up the usefulness of the swatches pane in several ways, then it's not "extra steps".
Other swatches pane ideas like better organization of patterns and gradients, the automatic swatches idea would mean more traffic to that section.
So if you coordinate the ideas, I think implementation might be easier in the long run.
*Some programmer talk*
If the program has picked up on the previous colors and then uses that already in its system as a reference, wouldn't that be the same as picking from the pane, though to the user it looks exactly the same? To the program it's already created the reference to the user, so it makes no difference because it "remembers" it, thus creating from the swatches panel or creating on the fly would be the same since it has already "remembered" the swatch involved. The only additional issue would be creating the infrastructure of "On the fly" and "from the pane" but in theory it can be fairly similar and would both end in referring to the gradient panel anyway.
"Are you sure you want to create gradient?" Yes
check if you don't want to see this again.
Gradient panel w/colors.--> Done.
Or that's my suggestion. i.e. implement both suggestions, coordinate them, and in the long run it would cut programmer time on both ends.
Do you need the Figma? The front end implementation would simply be two different locations that lead to the same path, simplify the UX, though it's only like what? 2 points of entry.
Of course this means you have to implement the other suggestion first, (i.e. remember last colors eyedropped), but building the architecture on the back of that and doing both sides of this wouldn't be difficult, I would think, since it's leading to the same UX path only from different entries. Of course, if you do this suggestion first, then do the other one, then the programming is going to be a lot more difficult... but I think reasonably one shouldn't do that.