You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/build/build-loop.md
+13-4Lines changed: 13 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -4,14 +4,18 @@ Now that all of your setup for the building blocks are done, now we can jump int
4
4
5
5
## Download Loop Code
6
6
7
-
You’ll need to download the Loop code in order to build the app on your computer. Click on ONE of the links below to download your Loop source code. **We recommend Master branch be used to build your Loop.**
7
+
You’ll need to download the Loop code in order to build the app on your computer. Click on ONE of the links below to download your Loop source code. Wondering which to choose? Read the blue box below **<u>ESPECIALLY IF YOU ARE AN OMNIPOD USER</u>**
[Loop: Dev branch](https://github.com/LoopKit/Loop/archive/dev.zip)
12
13
</p></br>
13
14
14
-
Master vs Dev? What is the difference? The Loop code resides in [GitHub](https://github.com/LoopKit/Loop) within a repository. A repository is kind of like a project's bookshelf, holding various books versions (aka branches) of a project. The master branch is considered a stable version. Any new features or options are first tested in a dev (short for "development") branch of the Loop. New or inexperienced users should not build from the dev branch of Loop, as there is a greater likelihood of encountering bugs or glitches. If you hear of "new features in dev", these are things that may be eventually merged into the master branch once any bugs are worked out.
15
+
!!!info "MASTER VS DEV -- Which to choose?"
16
+
Master vs Dev? What is the difference? The Loop code resides in a website called [GitHub](https://github.com/LoopKit/Loop). The various projects in GitHub use "repositories". A repository is kind of like a project's bookshelf, holding various books versions (aka branches) of a project. The master branch is considered a stable version of the project. Any new features or options are first tested in a dev (short for "development") branch of the Loop. If you hear of "new features in dev", these are things that may be eventually merged into the master branch once any bugs are worked out. New or inexperienced users should not build from the dev branch of Loop, as there is a greater likelihood of encountering bugs or glitches.
17
+
18
+
**Omnipod support in Loop is considered experimental and in-development. If you want to build a version of Loop that supports Omnipod, you will need to select the Dev branch download above.** Keep in mind, dev branch represents a greater likelihood of encountering bugs or glitches. As you encounter those, please check the docs first to see if that issue is already answered. If you think you truly are seeing strange behavior, report the bug to Loop's GitHub by [creating a "New Issue" here](https://github.com/loopkit/loop/issues). You can also look through the list of known issues already reported, as there is a chance your issue has already been seen by others.
15
19
16
20
17
21
!!!info ""
@@ -143,11 +147,13 @@ There is SUPER valuable information contained in these documents that really nee
143
147
* How to use override targets
144
148
* What the difference is between insulin models
145
149
146
-
Once your build is successful, please do the following:
150
+
### Once your build is successful, DO NOT JUST GO ENTERING SETTINGS IN BY YOURSELF!
151
+
152
+
Instead, work step-by-step to make sure you get through these pieces of helpful information:
147
153
148
154
* Read the [Jaeb Observational Study page](https://loopkit.github.io/loopdocs/build/jaeb-study/)
149
155
* Read the [Health Permissions page](https://loopkit.github.io/loopdocs/build/health/) to make sure you get your Loop data recording properly
150
-
*Use the all the pages listed under the Operate tab of this site to read up; starting with following the directions at [App Setup/Loop Settings](https://loopkit.github.io/loopdocs/operation/loop-settings/settings/) as you input your initial Loop settings and get started. Keep that page open and follow its step-by-step explanation of the settings.
156
+
*Start with following the step-by-step directions for setting up your Loop correctly. THIS IS IMPORTANT! There are safety considerations in how you setup your app...so please follow along with the setup guides. [Loop App Overview and Setup Pages](https://loopkit.github.io/loopdocs/operation/overview/)</br></br>
151
157
152
158
And longer term:
153
159
@@ -161,6 +167,9 @@ Many of the greatest challenges in starting Loop can be helped by reading the pa
161
167
162
168
If the build is successful, your brand new Loop app will have a screen open immediately on the iPhone asking about allowing Loop notifications and Health App access. Allow Loop to send you notifications. In the next screen that follows that, click on the `Turn All Categories On` line and then click `Allow` in the upper right corner.</br></br>
163
169
170
+
And now that you're built, I'm going to remind you again to use the guides to help you setup and understand your Loop app:
171
+
[Loop App Overview and Setup Pages](https://loopkit.github.io/loopdocs/operation/overview/)</br></br>
172
+
164
173
!!! info "First time builders"
165
174
If this is the first time you have installed an app on your iPhone using your developer account, you may get a warning like below. Don't worry, Loop installed on the phone but needs you to do an extra step on the phone before Loop app can open. Just follow the directions shown in the warning for what you need to do on your iPhone, and the issue resolves very quickly. Click ok and you can safely disconnect your iPhone from the computer. (If you don’t get a warning and the Loop app installs but does not open, you may still need to go to Settings->General->Device Management and enable trust for your Developer Account.)
0 commit comments