Skip to content

Kaleido docs updates for v1 #5111

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

Open
wants to merge 48 commits into
base: main
Choose a base branch
from
Open

Kaleido docs updates for v1 #5111

wants to merge 48 commits into from

Conversation

LiamConnors
Copy link
Member

@LiamConnors LiamConnors commented Mar 25, 2025

This PR adds changes for Kaleido v1

@LiamConnors LiamConnors self-assigned this Mar 25, 2025
@LiamConnors LiamConnors added the documentation written for humans label Mar 25, 2025
@LiamConnors LiamConnors changed the title Kaleido docs updates Kaleido docs updates for v1 Apr 1, 2025
@LiamConnors LiamConnors marked this pull request as ready for review April 1, 2025 19:49
@LiamConnors LiamConnors requested review from emilykl and ndrezn April 1, 2025 19:49
Other Chromium-based browsers may also work, though Kaleido won't discover them automatically. You can set a browser to use by setting the path to search using an environment variable called `BROWSER_PATH`. For example:

```
BROWSER_PATH=/Applications/Microsoft\ Edge.app/Contents/MacOS/Microsoft\ Edge
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this line should begin with export right? or do we not usually put export for env vars in the docs?


pio.write_image(fig, "fig.png")
~~~
<!-- #endregion -->

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add section here (or elsewhere in the file) documenting the new pio.write_images function, recommended for exporting multiple images in a row because it is much faster than calling pio.write_image repeatedly.

Documentation for the function is here. Happy to help suggest wording if that would be helpful.

pio.write_images should also be referenced in the Kaleido v1 migration doc, because anyone calling write_images many times in a row will notice a significant performance hit unless they switch to using pio.write_images.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added an example and note in the migration doc

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should link to the Chrome setup instructions from this doc, since that's one of the major differences between Kaleido v0 and v1.

Copy link
Contributor

@emilykl emilykl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great @LiamConnors ! 🚀

The pio.write_images documentation should be added; all my other comments are just minor details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation written for humans
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants