[manual]: vault backup - 21 files changed | 2024-10-02 17:40:08 | DES…

…KTOP_MSI Affected files: .obsidian/community-plugins.json 00-INBOX/Obsidian Plugin URI.md 00-INBOX/R Shiny Card Based Design.md 00-INBOX/Shebang.md 03-AREAS/Journal/2024-09-27.md 03-AREAS/Journal/2024-09-28.md 03-AREAS/Journal/2024-09-30.md 03-AREAS/Journal/2024-10-02.md 04-RESOURCES/Cheatsheets/Cheatsheet - Windows CPL and MSC Commands.md 04-RESOURCES/Code/PowerShell/PowerShell - Check for Non-Microsoft Signed Services.md 04-RESOURCES/Code/PowerShell/PowerShell - Reset DNS Cache.md 04-RESOURCES/Code/PowerShell/_README.md 04-RESOURCES/Code/R/R - Retrieve a JWT from Auth0.md 04-RESOURCES/Definitions/Acronyms/Client URL (cURL).md 04-RESOURCES/Definitions/Acronyms/Control Panel (CPL).md 04-RESOURCES/Definitions/Acronyms/End User Computing (EUC).md 04-RESOURCES/Definitions/Acronyms/Federal Information Processing Standard (FIPS).md 04-RESOURCES/Definitions/Acronyms/Microsoft Management Console (MSC).md 04-RESOURCES/Definitions/Acronyms/Physical-to-Virtual (P2V).md 04-RESOURCES/Lists/List - Command Line Tools.md 05-SYSTEM/Documents/PDFs/RShiny-CardBasedDesign.pdf
noclocks · Oct 2, 2024 · 58a42d1 · 58a42d1
1 parent 37ad3d8
commit 58a42d1
Show file tree

Hide file tree

Showing 21 changed files with 1,476 additions and 3 deletions.
diff --git a/.obsidian/community-plugins.json b/.obsidian/community-plugins.json
@@ -59,5 +59,6 @@
   "vscode-editor",
   "obsidian-link-converter",
   "image-converter",
-  "nexus-ai-chat-importer"
+  "nexus-ai-chat-importer",
+  "copilot"
 ]
diff --git a/00-INBOX/Obsidian Plugin URI.md b/00-INBOX/Obsidian Plugin URI.md
@@ -0,0 +1,3 @@
+```
+obsidian://show-plugin?id=<PluginId>
+```
diff --git a/00-INBOX/R Shiny Card Based Design.md b/00-INBOX/R Shiny Card Based Design.md
@@ -0,0 +1,121 @@
+---
+creation_date: 2024-09-30
+modification_date: 2024-09-30
+author: Jimmy Briggs <[email protected]>
+tags:
+  - Type/Note
+  - Topic/Dev
+  - Topic/Dev/R
+  - Topic/Dev/R/Shiny
+  - Status/WIP
+aliases:
+  - R Shiny Card Based Design
+publish: true
+permalink:
+description:
+image:
+cssclasses:
+---
+
+
+# R Shiny Card Based Design
+
+> [!SOURCE] Sources:
+> - *[[05-SYSTEM/Documents/PDFs/RShiny-CardBasedDesign.pdf|RShiny-CardBasedDesign]]*
+
+```table-of-contents
+title: ## Contents 
+style: nestedList # TOC style (nestedList|inlineFirstLevel)
+minLevel: 1 # Include headings from the specified level
+maxLevel: 4 # Include headings up to the specified level
+includeLinks: true # Make headings clickable
+debugInConsole: false # Print debug info in Obsidian console
+```
+
+## Overview
+
+> [!NOTE] About
+> This note summarizes the concepts introduced in a published PDF: [[05-SYSTEM/Documents/PDFs/RShiny-CardBasedDesign.pdf|RShiny-CardBasedDesign]].
+
+The document describes using a card-based design for building dashboards in [[04-RESOURCES/Tools/Tool - R Shiny|R Shiny]]. Card-based design, adopted by companies like Apple and Google, helps create an intuitive and organized [[04-RESOURCES/Definitions/Acronyms/User Experience (UX)|User Experience (UX)]]. The article explains the steps to develop such a design in R Shiny, focusing on:
+
+1. **Data Source Management:** Understanding the data and identifying analysis subjects to guide the application's content.
+
+2. **Divide Contents into Units & Assign Cards:** Classify data into units and select appropriate card types for visualization. It introduces various card types such as basic cards, cards with multiple tabs, cards with sidebars, and user info cards. The article emphasizes using the [[04-RESOURCES/Tools/Tool - R bslib|{bslib}]] package first for card creation and then exploring others like [[04-RESOURCES/Tools/Tool - R shinydashboardPlus|{shinydashboardPlus}]] if needed.
+
+3. **Organization:** Discusses creating the layout for a card-based app using [[04-RESOURCES/Tools/Tool - R Shiny|R Shiny]]'s native layout functions for stability and compatibility. It presents two main layout functions:
+
+    - `fluidRow` from [[04-RESOURCES/Tools/Tool - R Shiny|{shiny}]] for arranging cards in rows using a 12-column grid system.
+    - `layout_column_wrap` from [[04-RESOURCES/Tools/Tool - R bslib|{bslib}]] for automatically distributing cards across rows.
+4. **Decorate:** Talks about enhancing the dashboard with themes and icons using the [[04-RESOURCES/Tools/Tool - R bslib|{bslib}]] package for theme adjustments. It highlights how to change themes easily with `bs_theme()` and the inclusion of icons using [[Tool - FontAwesome|FontAwesome]].
+
+5. **Conclusion:** Recommends using native Shiny functions for layouts and [[04-RESOURCES/Tools/Tool - R bslib|{bslib}]] for card design, decorating with themes, and icons. It also suggests mastering [[04-RESOURCES/Definitions/Acronyms/Cascading Style Sheets (CSS)|CSS]] and [[04-RESOURCES/Code/JavaScript/_README|JavaScript]] for further customization.
+
+The paper provides practical guidance for creating polished, professional dashboards in R Shiny without requiring advanced front-end development skills.
+
+## Diagrams
+
+```mermaid
+graph LR
+    A[Data Source Management] --> B[Divide Contents Into Units & Assign Cards]
+    B --> C[Organization]
+    C --> D[Decorate]
+    D --> E[Deploy]
+```
+
+```mermaid
+graph LR
+    A[Card Type] --> B[Basic card]
+    A --> C[Profile card]
+    A --> D[Metric card]
+    A --> E[Flib card]
+    A --> F[Card with static image]
+    A --> G[Card with multiple tabs]
+    A --> H[Card with sidebar]
+    A --> I[Card with dropdown menu]
+
+    B --> B1[bslib::card]
+    B --> B2[shinydashboardPlus::box]
+
+    C --> C1[shinydashboardPlus::userBox]
+
+    D --> D1[bslib::value_box]
+    D --> D2[summarybox::summaryBox]
+    D --> D3[shinydashboard::infoBox]
+
+    E --> E1[shinydashboardPlus::flipbox]
+
+    F --> F1[bslib::card_image]
+    F --> F2[shinydashboardPlus::box]
+
+    G --> G1[bslib::navset_card_tab]
+    G --> G2[shinydashboardPlus::tabbox]
+
+    H --> H1[bslib::layout_sidebar]
+    H --> H2[shinydashboardPlus::boxSidebar]
+
+    I --> I1[shinyWidgets::dropdownButton]
+    I --> I2[shinydashboardPlus::boxDropdown]
+```
+
+## Resources
+
+***
+
+## Appendix
+
+*Note created on [[2024-09-30]] and last modified on [[2024-09-30]].*
+
+### See Also
+
+- 
+
+### Backlinks
+
+```dataview
+LIST FROM [[R Shiny Card Based Design]] AND -"CHANGELOG" AND -"//R Shiny Card Based Design"
+```
+
+***
+
+(c) [No Clocks, LLC](https://github.com/noclocks) | 2024
diff --git a/00-INBOX/Shebang.md b/00-INBOX/Shebang.md
@@ -0,0 +1,100 @@
+---
+creation_date: 2024-10-02
+modification_date: 2024-10-02
+author: Jimmy Briggs <[email protected]>
+tags:
+  - Type/Note
+  - Topic/Dev
+  - Topic/Dev/Linux
+  - Topic/Dev/Shell
+  - Status/WIP
+aliases:
+  - Shebang 
+publish: true
+permalink:
+description:
+image:
+cssclasses:
+---
+
+
+# Shebang (`#!`)
+
+> [!SOURCE] Sources:
+> - **
+
+```table-of-contents
+title: ## Contents 
+style: nestedList # TOC style (nestedList|inlineFirstLevel)
+minLevel: 1 # Include headings from the specified level
+maxLevel: 4 # Include headings up to the specified level
+includeLinks: true # Make headings clickable
+debugInConsole: false # Print debug info in Obsidian console
+```
+
+## Overview
+
+> [!NOTE] About
+> A shebang (`#!`) tells the [[operating system]] which interpreter to use when executing a script.
+> For example, in a bash script, you might see `#!/usr/bin/bash` at the top of the script.
+
+A **shebang** (#!) tells the operating system which interpreter to use when executing a script.
+
+This specifies that the system should use the [[../04-RESOURCES/Code/Bash/_README|Bash]] shell located at `/bin/bash`. 
+
+While these hardcoded paths work well in many environments, they can sometimes limit the script’s portability. 
+
+That's where `env` becomes useful.
+
+## Environment Based Shebangs
+
+Using `env` in the shebang *ensures that the script dynamically locates the interpreter based on the user's environment*, instead of directly interpreting a hard-coded path. You can let `env` search the system's `PATH` environment variable in order to find the appropriate interpreter.
+
+For example:
+
+```bash
+#!/usr/bin/env bash
+```
+
+instead of 
+
+```bash
+#!/usr/bin/bash
+```
+
+By using `env`, you remove the reliance on a specific path, allowing the system to select the interpreter from wherever it’s defined in the user’s `PATH`. This is particularly helpful in various environments where the interpreter’s path might not be as predictable as you think.
+
+### Key Advantages of Using `env`
+
+1. **Portability Across Systems**  
+    On many Linux distributions and macOS, `/bin` is commonly a symbolic link to `/usr/bin`. This means that `#!/bin/bash` or `#!/usr/bin/python3` will often work without issue. However, in some specialized environments, custom installations, or more niche Unix-like systems, interpreters might be installed in non-standard locations. By using `env`, your script remains adaptable and can locate the interpreter wherever it resides in the `PATH`, regardless of the system setup.
+2. **Flexibility with Virtual Environments**  
+    Many developers, especially in the Python ecosystem, rely on virtual environments to manage dependencies. Virtual environments allow you to isolate the interpreter and its packages for specific projects. By using `env`, the script will automatically use the interpreter from the active virtual environment rather than the system-wide installation, providing greater flexibility and avoiding conflicts.
+3. **Handling Multiple Versions of an Interpreter**  
+    Systems often have multiple versions of the same interpreter (e.g., Python 2 and Python 3, or different Bash versions). When you use `env`, the script will execute with the version that’s prioritized in the user’s `PATH`, ensuring compatibility with the version of the interpreter they intend to use.
+4. **Avoiding Hardcoded Paths**  
+    Hardcoding paths like `/bin/bash` or `/usr/bin/python3` assumes that the interpreter will always be installed in that exact location, which isn’t always the case. Using `env` abstracts this away, ensuring that your script remains functional regardless of where the interpreter is installed.
+
+
+
+## Resources
+
+***
+
+## Appendix
+
+*Note created on [[2024-10-02]] and last modified on [[2024-10-02]].*
+
+### See Also
+
+- 
+
+### Backlinks
+
+```dataview
+LIST FROM [[Shebang]] AND -"CHANGELOG" AND -"00-INBOX/Shebang"
+```
+
+***
+
+(c) [No Clocks, LLC](https://github.com/noclocks) | 2024
diff --git a/03-AREAS/Journal/2024-09-27.md b/03-AREAS/Journal/2024-09-27.md
@@ -0,0 +1,105 @@
+---
+creation_date: 2024-09-27
+modification_date: 2024-09-27
+author: Jimmy Briggs <[email protected]>
+tags:
+  - Type/Journal/Daily
+  - Type/Journal
+  - Topic/Journal
+  - Topic/Journal/Daily
+  - Status/Ongoing
+aliases:
+  - 2024-09-27
+  - September 27th, 2024
+  - Friday 27th September, 2024
+publish: true
+permalink: areas/journal/daily/2024-09-27
+description: Daily Journal Note for 2024-09-27.
+banner_icon:
+banner:
+cssclasses:
+  - daily
+---
+
+
+# [[2024-09-27|Friday, September 27, 2024]]
+
+<< [[2024-09-26]] | [[2024-09-28]] >>
+
+```table-of-contents
+title: ## Contents 
+style: nestedList # TOC style (nestedList|inlineFirstLevel)
+minLevel: 1 # Include headings from the specified level
+maxLevel: 4 # Include headings up to the specified level
+includeLinks: true # Make headings clickable
+debugInConsole: false # Print debug info in Obsidian console
+```
+
+## Daily Journal
+
+> [!NOTE] Personalized daily activity logs.
+
+- `...`
+
+## Daily Discoveries
+
+> [!NOTE] Anything relevant that was discovered on this day (i.e. new tools, technologies, code snippets, ideas, videos, podcasts, people, etc.)
+
+- `...`
+
+## Daily Tasks
+
+> [!TODO]- Todoist Tasks
+> ```todoist
+name: Highest Priority & Date
+filter: "today & ##No Clocks"
+sorting:
+   - priority
+groupBy: project
+```
+
+
+## Metadata & Links
+
+> [!META]- Metadata:
+> - Year:: [[2024]]
+> - Month:: [[2024 September]]
+> - Quarter:: [[2024Q3]]
+> - Week:: [[2024 395524 39]]
+
+> [!log] Created Notes Log:
+> ```dataview
+TABLE file.folder AS Folder
+WHERE file.cday = date(this.file.name) AND file.name != (this.file.name)
+SORT file.folder ASC, file.name ASC
+```
+
+> [!log] Modified Notes Log:
+> ```dataview
+TABLE file.folder AS Folder
+WHERE file.mday = date(this.file.name) AND file.name != (this.file.name)
+SORT file.mtime asc
+```
+
+***
+
+## Appendix
+
+*Note created on [[2024-09-27]] and last modified on [[2024-09-27]].*
+
+### See Also
+
+- 
+
+### Backlinks
+
+```dataview
+LIST FROM [[2024-09-27]] AND -"CHANGELOG" AND -"03-AREAS/Journal/2024-09-27"
+```
+
+***
+
+(c) [No Clocks, LLC](https://github.com/noclocks) | 2024
+
+
+