-
Notifications
You must be signed in to change notification settings - Fork 366
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
New standalone example showing blueprint configuration of some stock #5603
Conversation
Size changes
|
702af1c
to
75add53
Compare
bf8a6b0
to
4563b48
Compare
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.
real nice
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.
pretty cool example, but the requirements.txt is causing me issues
Available choices are: | ||
|
||
- `auto`: Reset the blueprint to the auto layout used by the viewer. | ||
- `one-stock`: Uses a filter to show only a single chart. | ||
- `one-stock-with-info`: Uses a container to layout a chart and its info document | ||
- `one-stock-no-peaks`: Uses a filter to additionally remove some of the data from the chart. | ||
- `compare-two`: Adds data from multiple sources to a single chart. | ||
- `grid`: Shows all the charts in a grid layout. |
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.
I think we have to give them different application ids each: Right now it's quite confusing when you just leave the viewer open and try to execute the script several times with different blueprints :/
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.
discussed on slack, no immediate action to take. We know that application id changing is more wrong. Comes down to figuring out the blueprint lifecycle
What
This is the example that the blueprint getting started guide / tutorials will be built off of.
However, this is a slightly more full-featured example that can be used as a reference and standalone application.
Checklist
main
build: app.rerun.ionightly
build: app.rerun.io