You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Although we use blueprint.js to provide a consistent UI foundation for various widgets/components, its usage does:
a) Bloat up our bundle size
b) Make our [embedding / use as a package] story a bit awkward as we may be consuming this library into an application not based on blueprint.js and our usage of blueprint.js may "infect" or override the application's existing styling.
In practice, our usage of blueprint.js is limited to:
Buttons
Styled form inputs
Slider controls
Non-ideal state placeholders
Cards
Callouts (stylized info/error/warning panels)
Dialog frames for modals
Menus
Toast-style notifications
Font/SVG icons
Most, if not, all can be replicated "in-house" or with a lower-footprint and un-opinionated, but themeable UI foundation library.
The text was updated successfully, but these errors were encountered:
Radix UI looks to be a decent alternative in terms of what we're using.
A key selling point here is that it is "headless", so it does not impose any pre-defined styling constraints on downstream consumers of this viewer package.
Although we use blueprint.js to provide a consistent UI foundation for various widgets/components, its usage does:
a) Bloat up our bundle size
b) Make our [embedding / use as a package] story a bit awkward as we may be consuming this library into an application not based on blueprint.js and our usage of blueprint.js may "infect" or override the application's existing styling.
In practice, our usage of blueprint.js is limited to:
Most, if not, all can be replicated "in-house" or with a lower-footprint and un-opinionated, but themeable UI foundation library.
The text was updated successfully, but these errors were encountered: