-
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
Render large tables #158
Render large tables #158
Conversation
Instructions for code reviewerHello reviewer, thanks for taking the time to review this PR!
Checklist
|
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.
Looks good. I have not tested but looks like in practice it should just check if the table needs to be rotated or not
Next thing to think about is how this could be applied for custom tables? or do we just state a recommended practice to follow? |
Thanks! What I hope is one of the last components of this PR, which I'm working on now, is designing a way to accommodate tables that need landscape orientation but are too wide to be shrunken with the existing workflow (e.g., red snapper, which has a 60" wide indices table without shrinking, and with shrinking, has text that is too small to read). |
Great point. I'll write up an explanation for our workflow and explain how the user can do it manually for custom tables in the FAQs and manual. |
899f3fb
to
7439a1c
Compare
06181fd
to
1f2d01f
Compare
… to require changing page orientation from portrait to landscape. Alter the Tables qmd to allow orientation changes for each table, if necessary.
…y splitting into multiple tables
…te create_tables_doc
…date documentation and usage in create_tables_doc()
…multiple smaller tables, but still a bug in render_lg_table (producing "Error" as part of output when testing)
…ccessfully rendering extra-wide table with new solution, but need to check if this will work in other circumstances
…p: apply to other tables, and simplify/clarify the new functions
…e tables will only reference the last table in the chunk, not the first. So next step: make a chunk for each table. Also removed now irrelevant function: ID_split_tbls
… can be referenced.
…s is made; update documentation
1f2d01f
to
625a669
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.
I reran the create_tables_doc function from a previous example and it worked...however, it repeated the table caption over and over in the list of tables in the beginning of the doc and broke it up incorrectly in the document itself (I think). Guess we will need to chat about this next week. I can retest on monday with a fresh mind just in case :)
Thanks for testing. Can you please explain how it's breaking the tables up incorrectly? And what would you prefer the table captions look like? |
|
@sbreitbart-NOAA I think the tables are broken up fine but I wonder if it's possible to add into the caption the fleets that are included in the separated table |
…in parentheses after caption (example: <indices caption> (Fleet 6, Fleet 7))
@Schiano-NOAA I've updated the workflow so that when a table is split, the header values for each table are added in parentheses to the end of the table caption, like this: Is this change sufficient to approve the PR? Or should I make more changes to the workflow? |
This should be good. Let me do a quick test |
What is the feature?
How have you implemented the solution?
create_tables_doc
, then customizing the appropriate chunk in the 08_tables.qmd file so that tables wider than 5" are placed in a landscape-orientation page. Tables between 5-12" wide are forced to shrink in width to 7.5" (this shrinks the text to fit). Tables > 12" wide are split into multiple tables, saved as a new rda, and placed in individual chunks in the 08_tables.qmd doc.Does the PR impact any other area of the project, maybe another repo?