|
1 |
| -# Xtreme-Apps |
2 |
| -Bundle of external apps tweaked for Xtreme |
| 1 | +# Momentum-Apps |
| 2 | +Bundle of external apps tweaked for [Momentum Firmware](https://github.com/Next-Flip/Momentum-Firmware). |
| 3 | + |
| 4 | +> [!IMPORTANT] |
| 5 | +> These apps are already included with all Momentum Firmware releases. |
| 6 | +> This repository serves only as a way to keep them updated and maintained easier. |
3 | 7 |
|
4 | 8 | ### Why?
|
5 |
| -Apps we use for Xtreme are all modified (some lots more than others). This includes: |
6 |
| -- Removing duplicate icons that are part of firmware to **support our Asset Packs system** |
| 9 | +Many apps included in Momentum are modified (some lots more than others). This includes: |
| 10 | +- Removing/tweaking icons and/or their usages to **support our Asset Packs system** |
7 | 11 | - Removing duplicate keyboard implementations to **use our extended system keyboard**
|
8 | 12 | - With our system keyboard also **support our CLI command `input keyboard`** to type with PC keyboard
|
9 |
| -- **Moving location of save files** or changing how they are saved |
10 |
| -- **Changing application display names** to fit our scheme |
| 13 | +- **Moving location of save files** to a more appropriate location or changing how they are saved |
| 14 | +- **Changing application display names** to fit our naming scheme |
11 | 15 | - **Changing how some menus work/look** or adding **new exclusive menus and features**
|
12 |
| -- **Improving or extending functionality** and better integrating with Xtreme firmware |
| 16 | +- **Improving or extending functionality** and better integrating with the firmware |
13 | 17 | - **Updating and fixing apps** that were abandoned by the original developers
|
14 | 18 |
|
15 | 19 | ### How?
|
16 |
| -**Apps made by the Xtreme team are kept as plain code here. For all others we use git subtrees to pull updates from elsewhere but also keep our own tweaks.** |
| 20 | +**Apps made by the our team are developed right here, the latest versions will always originate from this repository.** |
| 21 | + |
| 22 | +**For all other apps we use git subtrees to pull updates from the creator's repository / other sources such as [@xMasterX's pack](https://github.com/xMasterX/all-the-plugins), while also keeping our own tweaks and additions.** |
| 23 | + |
17 | 24 | We didn't want to have fork repos for each single app since it would get out of hand very quick. Instead, we opted for subtrees.
|
18 | 25 |
|
19 |
| -Subtrees work in a very peculiar way, where they pull and compare commit history from a remote repo and apply it to a subdirectory of this repo. |
20 |
| -That's why the commit history for our repo is so huge, it contains all the commits for all the apps, plus our edits. |
| 26 | +Subtrees work in a very peculiar way: they pull and compare commit history from a remote repo and apply it to a subdirectory of this repo. |
| 27 | +That's why the commit history for this repo is so huge, it contains all the commits for all the apps, plus our edits. |
21 | 28 |
|
22 |
| -To make updating more manageable, we have added another layer on top of subtrees: |
| 29 | +To make updating more manageable, we have added some scripts on top of subtrees: |
23 | 30 | - add a new app with `.utils/add-subtree.sh <path> <repo url> <branch> [subdir]`, this will pull the history and create `path/.gitsubtree` to remember the url, branch and subdir
|
24 | 31 | - run `.utils/update-subtree.sh <path>` to pull updates for a subtree
|
25 | 32 | - or run `.utils/bulk-update-subtrees.sh` to do it for all subtrees
|
0 commit comments