Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
shinyscreen
Manage
Activity
Members
Labels
Plan
Wiki
External wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container Registry
Model registry
Operate
Environments
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Gitlab will go in to maintenance on Friday 5:30pm since SIU is doing Isilon maintenance and we use isilon shares on the Gitlab
You are on a read-only GitLab instance.
Show more breadcrumbs
Environmental Cheminformatics
shinyscreen
Commits
6c880987
Unverified
Commit
6c880987
authored
4 years ago
by
Todor Kondic
Browse files
Options
Downloads
Patches
Plain Diff
shiny-lessons: Update
* shiny-lessons.org: Update lessons.
parent
23c94e19
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
shiny-lessons.org
+20
-0
20 additions, 0 deletions
shiny-lessons.org
with
20 additions
and
0 deletions
shiny-lessons.org
+
20
−
0
View file @
6c880987
...
...
@@ -18,3 +18,23 @@
- An ordinary list inside reactive values list, if used, will add
dependency on all its members. Even if only some of its members are
used, the dependency is on all the members.
- Recursive dependencies can get ugly. If really needed, do not
depend, but use isolate.
- Do *NOT* change the value of things you depend on. This creates
infinite loops. It may even work, but will be sloooow.
- Single output produced by any input from a group of inputs: separate
observers are needed do differentiate between which of the inputs
have been triggered.
- The only way to detect if the button press was acted upon in a
reactive expression that depends on multiple inputs is to raise a
flag, or write the state of the button when done.
- As development progresses, keep an observer that transforms
shinyscreen mess into the logics of the workflow. Then move out as
much of this as possible into reactive functions. Example,
Shinyscreen underlying script flow was first emulated by an
observer.
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment