@wyndlass/app-sdk 1.1.1 → 1.1.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -75,6 +75,8 @@ Ask what should play where, and when. Then `campaign.save` at the place and time
|
|
|
75
75
|
|
|
76
76
|
Raise `version` in `app.json`, then pack and import again (steps 4 and 5). Layouts that name no version take the new one once it is approved and checked. A layout whose app element pins a `version` (the item's) moves only when you save it with the new one: show the person first.
|
|
77
77
|
|
|
78
|
+
**Where it is placed comes from `app.list`, never a guess.** Each of the organization's apps says which layouts place it and how many screens show it now. Tell the person: those layouts and screens take the new version by themselves. Asked to place or schedule it again, say where it is already, and make another layout or campaign only if they want one.
|
|
79
|
+
|
|
78
80
|
## Rules every app keeps
|
|
79
81
|
|
|
80
82
|
Screens or the CMS enforce each of these:
|
|
@@ -42,7 +42,7 @@ It answers `<zip>: uploaded (<n> bytes). Import it with app.import.` Never read
|
|
|
42
42
|
|
|
43
43
|
## 4. `app.list`
|
|
44
44
|
|
|
45
|
-
Lists Wyndlass's apps, then the organization's own: each with its item (`med_…`), and its newest versions, each:
|
|
45
|
+
Lists Wyndlass's apps, then the organization's own: each with its item (`med_…`), the layouts that place it ("Placed in 1 layout: Lobby (med_…)", or "Placed in no layout you may read"), how many screens show it now, and its newest versions, each:
|
|
46
46
|
- **"being checked, then approved with its import"** or **"…, then held for review":** Wyndlass is scanning and checking it. Call `app.list` again in a little while;
|
|
47
47
|
- **"refused by its checks: <reason>":** fix the cause ([contract.md](contract.md), Limits), raise `version`, pack and import again;
|
|
48
48
|
- **"held for review: a person approves it in the CMS":** give the person the link `app.import` gave, and say why it is held. Wait for them; never approve it yourself;
|
|
@@ -80,6 +80,7 @@ Ask what should play where, and when. Never at the organization's top place unle
|
|
|
80
80
|
2. Import it: steps 1 to 4.
|
|
81
81
|
3. **Layouts that name no version** (`app: {"id": "med_…"}`) take the new one once it is approved and checked.
|
|
82
82
|
4. **A layout that pins one** (`app: {"id": "med_…", "version": <n>}`, the item's version) keeps it. To move it, `layout.save` with the new item version, after showing the person the change.
|
|
83
|
+
5. **Say where it plays from `app.list`:** its layouts and its screens now. They need no new layout or campaign. Make one only when the person asks for another, after telling them where the app is already.
|
|
83
84
|
|
|
84
85
|
## When a screen doesn't show it
|
|
85
86
|
|