mirror of
https://github.com/SteamDeckHomebrew/decky-plugin-template.git
synced 2025-12-02 20:08:08 -06:00
typos
This commit is contained in:
parent
36389449ff
commit
12ebab3e0a
2 changed files with 5 additions and 5 deletions
|
|
@ -29,11 +29,11 @@ sudo npm i -g pnpm
|
|||
3. Consult the [decky-frontend-lib](https://github.com/SteamDeckHomebrew/decky-frontend-lib) repository for ways to accomplish your tasks.
|
||||
- Documentation and examples are still rough,
|
||||
- While decky-loader primarily targets Steam Deck hardware so keep this in mind when developing your plugin.
|
||||
4. If you want an all encompassing demonstration of decky-frontend-lib's capabilites check out [decky-playground](https://github.com/SteamDeckHomebrew/decky-playground). It shows off almost all of decky-frontend-lib's features.
|
||||
4. If you want an all encompassing demonstration of decky-frontend-lib's capabilities check out [decky-playground](https://github.com/SteamDeckHomebrew/decky-playground). It shows off almost all of decky-frontend-lib's features.
|
||||
|
||||
#### Other important information
|
||||
|
||||
Everytime you change the frontend code (`index.tsx` etc) you will need to rebuild using the commands from step 2 above or the build task if you're using vscode or a derivative.
|
||||
Every time you change the frontend code (`index.tsx` etc) you will need to rebuild using the commands from step 2 above or the build task if you're using vscode or a derivative.
|
||||
|
||||
Note: If you are receiving build errors due to an out of date library, you should run this command inside of your repository:
|
||||
|
||||
|
|
@ -64,7 +64,7 @@ More information on the bin folder can be found below in the distribution sectio
|
|||
### Distribution
|
||||
|
||||
We recommend following the instructions found in the [decky-plugin-database](https://github.com/SteamDeckHomebrew/decky-plugin-database) on how to get your plugin up on the plugin store. This is the best way to get your plugin in front of users.
|
||||
You can also choose to do distribution via a zip file containing the needed files, if that zip file is uploaded to a URL it can then be downloded and installed via decky-loader.
|
||||
You can also choose to do distribution via a zip file containing the needed files, if that zip file is uploaded to a URL it can then be downloaded and installed via decky-loader.
|
||||
|
||||
**NOTE: We do not currently have a method to install from a downloaded zip file in "game-mode" due to lack of a usable file-picking dialog.**
|
||||
|
||||
|
|
@ -86,7 +86,7 @@ pluginname-v1.0.0.zip (version number is optional but recommended for users sake
|
|||
plugin.json [required]
|
||||
main.py {required if you are using the python backend of decky-loader: serverAPI}
|
||||
README.md (optional but recommended)
|
||||
LICENSE(.md) [required, filename should be roughly similair, suffix not needed]
|
||||
LICENSE(.md) [required, filename should be roughly similar, suffix not needed]
|
||||
```
|
||||
|
||||
Note regarding licenses: Including a license is required for the plugin store if your chosen license requires the license to be included alongside usage of source-code/binaries!
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ const Content: VFC<{ serverAPI: ServerAPI }> = ({}) => {
|
|||
layout="below"
|
||||
onClick={(e) =>
|
||||
showContextMenu(
|
||||
<Menu label="Menu" cancelText="CAAAANCEL" onCancel={() => {}}>
|
||||
<Menu label="Menu" cancelText="CANCEL" onCancel={() => {}}>
|
||||
<MenuItem onSelected={() => {}}>Item #1</MenuItem>
|
||||
<MenuItem onSelected={() => {}}>Item #2</MenuItem>
|
||||
<MenuItem onSelected={() => {}}>Item #3</MenuItem>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue