Skip to content

Commit

Permalink
Complete links to other packages
Browse files Browse the repository at this point in the history
  • Loading branch information
hadley committed Mar 3, 2021
1 parent de7d884 commit 2a80830
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 1 deletion.
8 changes: 8 additions & 0 deletions action-layout.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -543,3 +543,11 @@ tags$p(
Note the use of `inline = TRUE`; the `textOutput()` default is to produe a complete paragraph.

To learn more about using HTML, CSS, and JavaScript to make compelling user interfaces, I highly recommend David Granjon's [Outstanding User Interfaces with Shiny](https://unleash-shiny.rinterface.com/index.html).

## Summary

This chapter has given you the tools you need to make complex and attractive Shiny apps.
You've learned the Shiny functions that allow you to layout single- and multi page apps (like `fluidPage()` and `tabsetPanel()`) and how to customise the overall visual appearance themes.
You've also learn a little bit about what's going on under the hood: you now know that Shiny uses Bootstrap, and that the input and output functions just return HTML, which you can also create yourself.

In the next chapter you'll learn more about another important visual component of your app: graphics.
2 changes: 1 addition & 1 deletion action-workflow.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -822,5 +822,5 @@ These workflows might seem a little abstract and easy to dismiss because they're
But I think of workflow as one of my "secret" powers: one of the reasons that I've been able to accomplish so much is that I devote time to analysing and improving my workflow.
I highly encourage you to do the same!

The next chapter on graphics is the first of a grab bag of useful techniques.
The next chapter on layouts and themes is the first of a grab bag of useful techniques.
There's no need to read in sequence; feel free to skip ahead to a chapter that you need for a current app.
2 changes: 2 additions & 0 deletions action.Rmd
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,8 @@ I think everyone should start with Chapter \@ref(workflow), because it gives you
After that, there's no prescribed order and relatively few connections between the chapters: I'd suggest quickly skimming to get the lay of the land (and so you might remember these tools if related problems crop up in the future), and otherwise only deeply reading the bits that you currently need.
Here's a quick run down of the main topics:

- Chapter \@ref(action-layout) details the various ways you can layout input and output components on a page, and how you can customise their appearance with themes.

- Chapter \@ref(action-graphics) shows you how to add direct interaction to your plot and how to display images generated in other ways.

- Chapter \@ref(action-feedback) covers a family of techniques (including inline errors, notifications, progress bars, and dialog boxes) for giving feedback to your users while you app runs.
Expand Down

0 comments on commit 2a80830

Please sign in to comment.