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/browser/build-dev-browser.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,18 +47,18 @@ Your `LoopWorkspace fork` is at `https://github.com/username/LoopWorkspace` wher
47
47
If you're building `dev`, you can skip ahead to [Add `Branch`](#add-branch). If you're building a feature branch, copy the branch name into your paste buffer to minimize typographical errors.
48
48
49
49
50
-
```{ .bash .copy }
51
-
feat/pod-keep-alive
52
-
```
53
-
54
-
```{ .bash .copy }
50
+
```{ .bash .copy title="Add Dana and Medtrum pumps to dev branch" }
55
51
feat/dev-dana-medtrum
56
52
```
57
53
58
-
```{ .bash .copy }
54
+
```{ .bash .copy title="Add Dana and Medtrum pumps, Eversense CGM to dev branch" }
59
55
feat/eversense
60
56
```
61
57
58
+
```{ .bash .copy title="Add Dana, Medtrum and All Omnipod Types, Eversense CGM to dev branch" }
59
+
feat/omnipodkit
60
+
```
61
+
62
62
### Add `Branch`
63
63
64
64
Each step in the list below matches with the number in the graphic. In the top half of the graphic, the left side shows the initial display and the right side shows the display after making the indicated selections:
Copy file name to clipboardExpand all lines: docs/version/development.md
+54-2Lines changed: 54 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,7 +25,7 @@ Please check the [development channel in zulipchat](https://loop.zulipchat.com/#
25
25
In addition to the main and dev branches, which are tightly controlled and only updated through a formal pull request and approval process, there are also some feature and update branches. These branches are subject to more frequent updates, so users testing these branches should follow along in zulipchat for information.
26
26
27
27
* The `update_dev_to_M.m.#` is where the next version of dev is tested before becoming part of `dev` and later being released as `main`
28
-
* The branches starting with `feat/` have one or more special features, like support for new pumpsor CGM
28
+
* The branches starting with `feat/` have one or more special features, like support for new pumps, CGM or the new universal pump manager for all types of Omnipods
29
29
30
30
The graphic below shows the `main` and `dev` branches along with some feature branches and an update branch.
31
31
@@ -48,6 +48,7 @@ The table below lists active branches. Note that updates may occur and be announ
48
48
| dev | 3.14.0 | 14 May 2026 | code is currently the same as `main`|
49
49
|[feat/dev-dana-medtrum](#feature-branch-dana-and-medtrum-support) <br>- SHA `638d351`| 3.14.0 | 14 May 2026 | - adds support for Dana and Medtrum pumps<br> - SHA for DanaKit is `c544c42`<br> - SHA for MedtrumKit is `6060747`<br>**Medtrum User Interface Redesigned** to be more like the Omnipod User Interac.<br>Several fixes added for MedtrumKit, not yet in DanaKit |
50
50
|[feat/eversense](#feature-branch-eversense-support) <br>- SHA `08e0e20`| 3.14.0 | 14 May 2026 | - adds experimental support for Eversense (includes Dana and Medtrum pumps support - same SHA as above)<br>- this branch is ready for use to evaluate and report back<br> - SHA for Eversense is `d243638`|
51
+
|[feat/omnipodkit](#feature-branch-omnipodkit-pump-manager)<br>- SHA `TBD`| 3.14.0 | TBD May 2026| The new OmnipodKit pump manager, controls all Types of pods. Initially only the Eros and DASH pod types are available for feature branch testers<br> - SHA for OmnipodKit is `TBD`<br>**Please read [Feature Branch: OmnipodKit Pump Manager](#feature-branch-omnipodkit-pump-manager)**|
51
52
52
53
!!! important "Eversense Support"
53
54
The Eversense CGM is now supported by the *Loop* app in a feature branch. To simplify maintenance, the branch which supports Eversense also supports the two new pumps: Dana and Medtrum.
@@ -66,6 +67,7 @@ The table below lists active branches. Note that updates may occur and be announ
66
67
For full instructions on building different branches, review these pages:
67
68
68
69
*[Browser Build: Build a Version in Development](../browser/build-dev-browser.md#build-development-version){: target="_blank" }
70
+
* For short-cut instructions on adding the feature branch: [Feature Branch](../browser/build-dev-browser.md#feature-branch){: target="_blank" }
69
71
*[Mac Xcode: Build a Version in Development](../build/build-dev-mac.md#build-other-branches){: target="_blank" }
70
72
71
73
#### Browser Build
@@ -76,6 +78,12 @@ Use the page linked above to add the desired branch name (from the table above)
76
78
77
79
For Mac Xcode build, the lines you need to copy and paste into a Terminal window are explicitly provided below:
78
80
81
+
```{ .bash .copy title="Download and build the feat/omnipodkit branch" }
@@ -100,9 +108,53 @@ The version number in the feature branch will match either the `dev` branch vers
100
108
* Each feature has an associated repository that contains the feature
101
109
* When updates to the feature are added, the SHA for the feature branch and the SHA for the submodule(s) which support that feature will be reported in the table above and can be found by examining the LoopWorkspace repository for that feature branch
102
110
111
+
### Feature Branch: OmnipodKit Pump Manager
112
+
113
+
You need to build the `feat/omnipodkit` branch if you want to test the new `All Omnipod Types` pump manager. Build instructions are found here: [How to Build Feature Branches](#how-to-build-feature-branches).
114
+
115
+
This pump manager comes with improved user interface and user experience for Omnipod Classic (Eros) and DASH pods including
116
+
117
+
* Some layout adjustments
118
+
* Some new labels
119
+
* Some reworked sub-menus with added information or features
120
+
* WARNINGS
121
+
- no translations added yet so English only for the initial roll-out
122
+
- no pod-keep-alive function added yet
123
+
124
+
The next time you change a pod, delete the pump manager you are using and add a new pump. See [Change Pump Type](loop-3/add-pump.md#change-pump-type){: target="_blank" } for detailed instructions.
125
+
126
+
* Select `All Omnipod Types` as your new pump manager.
127
+
* Go through the onboarding of selecting notifications and reminders and insulin type.
128
+
* You will then be presented with a screen to select the type of pod.
129
+
* Choose the Classic (Eros) or DASH Pod type
130
+
131
+
The underyling control code should be the same, but we want more people testing it to ensure this works as well as the older pod managers. The developers have been using it on themselves before making this publicly available.
132
+
133
+
!!! warning "Do not use with iPhone 16 or 17e and Atlas pods"
134
+
The new OmnipodKit does not have the pod-keep-alive feature incorporated. For now, if you use an iPhone 16 (any model) or iPhone 17e and have Atlas pods (the newer version for DASH pods), stick with the old Omnipod DASH selection.
135
+
136
+
!!! question "Why OmnipodKit?"
137
+
When the initial work to add DASH to the supported pumps was started in 2021, a completely separate pump submodule was created distinct from the Classic (Eros) pump submodule. In other words, OmniBLE handled DASH and OmniKit handled Eros.
138
+
139
+
A significant portion of the two repositories serve the same function. Whenever a fix or improvement was added to OmniBLE, it was duplicated and added to OmniKit. Having a universal pod manager saves significant developer resources.
140
+
141
+
OmnipodKit provides the individual support needed for different `Pod Types` while using a single copy of code for most of the logic and user interface.
142
+
143
+
The improvements that have been going on in the background landed in the new pump manager only - and were not replicated in the OmniKit or OmniBLE repositories.
144
+
145
+
This will be a significant time saver for developers moving forward for updating code and adding support for new types of pods.
146
+
147
+
!!! tip "feat/omnipodkit supports other plugins"
148
+
For the convenience of the developers and testers, this feature branch, feat/omnipodkit, also supports the new pump and cgm managers that are found in the other feature branches.
149
+
150
+
In other words:
151
+
152
+
* Eversense is available as a CGM
153
+
* Dana and Medtrum are available as a pump, in addtion to OmnipodKit and all the older pump managers
154
+
103
155
### Feature Branch: Pod Keep Alive Feature
104
156
105
-
The feat/pod-keep-alive branch has been deleted. It was updated and incorporated into the released code.
157
+
The feat/pod-keep-alive branch has been deleted. It was updated and incorporated into the released code. Please build the `main` branch over your existing app. All your selections will remain as you configured them when building the `feat/pod-keep-alive` branch.
106
158
107
159
See [Pod Keep Alive Feature](../loop-3/omnipod.md#pod-keep-alive-feature){: target="_blank" }.
0 commit comments