New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] - New component to represent process stages / timelines #260
Comments
lol check the PRs... #189 |
feel free to leave comments #189! would love your input as we build it. |
aaand i didn't click on the links! I took looks like we've got a naming problem! |
@giladgray Hahaha I was just about to comment that it was not the same kind of component! ;) But a better name might be |
+1 for this |
Just for reference - Equivalent component in Salesforce Lightning Design System: And in Ant Design: |
We're aware that this component exists in other UI kits. If you implement this using Blueprint core, it would be nice to see your code or a community-maintained package so that others can re-use your work. Other than that, there are no plans for us to develop this feature right now. |
@adidahiya No worries! I wasn't complaining about BlueprintJS not having the component btw - I just linked a few examples to help inspire BlueprintJS's design, if someone wants to implement it. |
Resurrecting an old post to express interest in this ! |
I have a suggestion for a new component, a stepper component; I'm partial to Semantic UI's but Material UI's feels like a good "minmal" version of it.
I could see these options being available on the component.
In which you can combine to use all of them, or just for example the Icon or Label, or any combination of them to create an step item. Preferably the layout and size would go from Big (with all options) to a smaller layout if you just use the Label or Icon for example.
Could be nice if some animations where used while transitioning between steps, such as having the Description hidden until that step is the active one and fading in or whatnot.
A pseudo code example;
The text was updated successfully, but these errors were encountered: