-
-
Notifications
You must be signed in to change notification settings - Fork 112
SCSS and Legend Panel #54
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
26506f4
port css over to scss. Swap `bem` to use hierarchical namespacing
bpostlethwaite 8058d55
Colorpicker uses BEM and a some folder structure changes
bpostlethwaite 12ace8c
delete files that are not in use
bpostlethwaite 3b02455
split out styles/containers into separate files
bpostlethwaite e319b00
add initial icon support
bpostlethwaite 000b5f1
Add plotly.js default font to default font list
bpostlethwaite 68a41af
rename css class accordion -> fold
bpostlethwaite 6896707
introduce CogMenu and Info
bpostlethwaite 6335fbb
Section looks for CogMenu for special placement
bpostlethwaite d6f2375
Use CogMenu in Legend in DefaultEditor
bpostlethwaite 9628ccd
css cogmenu becomes a more generic subpanel
bpostlethwaite 2225452
rename CogMenu to SubPanel
bpostlethwaite 440f88b
Section handles non Attr children as default Visible
bpostlethwaite 51f7b46
add subMenu to DefaultEditor
bpostlethwaite 7becfbe
test Section visibility and SubPanel handling
bpostlethwaite File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want this behavior? Seems kinda like you wouldn't want
<Info>
to be enough to invoke display, or maybe sometimes you do but not always?fit
fit
et al in all test files)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yep I did catch that one. And yep we have the same test in the workspace. I'll make an issue for that right now.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#57
Hmmm yeh I could see skipping
<Info>
actually. But not<MenuPanel>
? Unless you interrogate the<Section>
s inside<MenuPanel>
... but that would take some serious gymnastics...There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah right, that's your caveat above. It might be worth thinking a bit about whether there really are any cases where only the
<MenuPanel>
exists to make a<Section>
visible. If that's really "advanced settings" we might be able to argue that if none of the basics for that section exist, there's never a case where the advanced would be needed?I'm not sure if any similar argument works for
<Panel>
. Would be worthwhile looking for a concrete example.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
True I'll add this to an issue and deal with it once I have some breathing room
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#58