-
Notifications
You must be signed in to change notification settings - Fork 5
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
Consolidate stylesheets? #11
Comments
For app development (use with html) this is a feasible. I agree that it would be a good idea to provide users with a single stylesheet that handles default formatting for the page, parcoords, and slickgrid. Yes, lets call it Your point also led me to another question. In the same way that we use import './parallel-coordinates.css'; at the top of import './slick-grid.css'; there as well? This would mainly serve the npm library aspect of parasol and not the html use since any stylesheets addressing slickgrid in the html would take precedence over this. The thing I want to keep in mind is that the user should always have the freedom to customize slickgrid and I don't know if doing this would inhibit that freedom. |
Perhaps we can discuss this in person? You're more familiar with npm libraries than I am, so a bit of clarification would help on my end. I'll go ahead and make a combined styling sheet and do a pull request. |
Sounds great! Yeah, l'll email you about a time for next week. |
Implemented this in recent commit |
I'm going to keep this open until I have a chance to test out the effects of including style sheets in the library directly. Also, I think the "proper" way to build the This way, the general setup would be <link rel="stylesheet" type="text/css" href="parasol.css">
<link rel="stylesheet" type="text/css" href="style.css"> |
Got it! I'll update the examples and tutorial accordingly. |
@joshhjacobson, is there a compelling reason not to consolidate the various stylesheets into a single CSS file (which I would call parasol.css) for the sake of simplicity in app development?
That way, users could replace this...
With this!
Let me know, so I can implement this if you don't see an issue with it.
The text was updated successfully, but these errors were encountered: