|
1 | 1 | <script lang="ts"> |
| 2 | + import { page } from '$app/stores' |
| 3 | +
|
2 | 4 | import Markdown from '@nick-mazuk/ui-svelte/src/typography/markdown/markdown.svelte' |
| 5 | + import Seo from '@nick-mazuk/ui-svelte/src/utilities/seo/seo.svelte' |
| 6 | +
|
| 7 | + import luaLogo from '$lib/assets/images/lua-logo.png' |
3 | 8 |
|
4 | 9 | const content = `# Adding Scripts |
5 | 10 |
|
6 | | -Just create a pull request. All scripts must have in their [PluginDef](http://jwmusic.nu/jwplugins/wiki/doku.php?id=jwlua:development#connect_to_finale_jw_lua): |
| 11 | +> To add scripts, you'll need a GitHub account. If you don't have one, you can [sign up here](https://github.com/signup). |
| 12 | +
|
| 13 | +Once you've written your script, you'll be able to add it to the repository. |
| 14 | +
|
| 15 | +This guide assumes that you're not familiar with Git or GitHub (which is totally ok). However, if you are familiar with them, feel free to skip down to [Adding your script](#adding-your-script). |
| 16 | +
|
| 17 | +## Background on Git and GitHub |
| 18 | +
|
| 19 | +Git is a version control system that developers use to keep track of changes to their code. It's a very popular system, and it's used by a lot of companies. GitHub is a website that lets you host your code and make it available to others, and it uses Git to track the changes in the code. |
| 20 | +
|
| 21 | +Overall, you can think of it kind of like Google Docs. You can write code, and others can read it, and you can make changes to it. And everything is synced up so everyone knows what the "correct" version of the code is. And the way in which this is done is through forks, commits, and pull requests. |
| 22 | +
|
| 23 | +Here's what those terms mean. |
| 24 | +
|
| 25 | +### Forks |
| 26 | +
|
| 27 | +A fork is a copy of this repository that you can make changes to. In this guide, you're going to fork this repository (which is literally creating a line-by-line clone) and saving that fork onto your computer. That way, you can make changes to the code and then push those changes back to the original repository. |
| 28 | +
|
| 29 | +Forking a repository is a lot like just copying a Google Docs file. |
| 30 | +
|
| 31 | +### Commits |
| 32 | +
|
| 33 | +Commits are snapshots in time. They are save points. Once you edit, add, or delete several files, you "commit" them to group those changes together. Note that this is different than saving an individual file. You can save changes as many times as you want, but you only "commit" them once to—well—commit the changes. |
| 34 | +
|
| 35 | +### Pull requests |
7 | 36 |
|
8 | | -- finaleplugin.Author |
9 | | -- finaleplugin.Version (beta versions OK) |
10 | | -- finaleplugin.RevisionNotes (if there are revisions and/or bug fixes) |
11 | | -- Name, undo text, and description (in the \`return\` statement) |
| 37 | +By now you may have realized that you've made changes to a copy of this repository, not the original one. Pull requests allow you to merge those changes back into the original repository. |
12 | 38 |
|
13 | | -Note: All scripts added to the repo will have a CC1 license. See [LICENSE](https://github.com/Nick-Mazuk/jw-lua-scripts/blob/master/LICENSE) for specific terms. This is to encourage widespread use and encourage other JW Lua coders to build off your scripts. |
| 39 | +As part of the pull request process, other collaborators can review your code. This isn't a test to pass, but rather it's just a constructive step to help improve the quality of your contributions. Once your pull request is merged, you've contributed! |
14 | 40 |
|
15 | | -## Naming scripts |
| 41 | +--- |
16 | 42 |
|
17 | | -Let's follow a unified syntax to help organize everything. Use snake case: |
| 43 | +In addition to this guide, there great resources for learning [Git](https://youtu.be/USjZcfj8yxE) and [GitHub](https://youtu.be/nhNq2kIvi9s) out there in case you'd like to learn more. |
18 | 44 |
|
19 | | -\`\`\` |
20 | | -✓ articulation_delete_from_rests.lua |
| 45 | +## Adding your script |
21 | 46 |
|
22 | | -✖ articulationDeleteFromRests.lua |
| 47 | +> In short, you'll create a pull request to add your script to the \`/src\` directory. This section will walk you through that process. |
23 | 48 |
|
24 | | -✖ articulationdeletefromrests.lua |
| 49 | +When using Git and GitHub, you can either use the terminal or GitHub Desktop, which is a desktop application that provides a nice interface for Git. In thie guide, we'll be using GitHub Desktop. You can download it at [https://desktop.github.com](https://desktop.github.com/). |
25 | 50 |
|
26 | | -✖ articulation-delete-from-rests.lua |
| 51 | +Make sure you download GitHub Desktop and sign in to your GitHub account. You only need to do this once. |
27 | 52 |
|
28 | | -✖ articulation_Delete_From_Rests.lua |
29 | | -\`\`\` |
| 53 | +Checkout [GitHub's documentation](https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/overview/getting-started-with-github-desktop#part-1-installing-and-authenticating) for this for more detail. |
30 | 54 |
|
31 | | -Each word should take things from general to specific. So anything dealing with articulations should start with "articulations". Anything with page layout should start with "layout". See the [JW Lua docs for Category Tags](http://jwmusic.nu/jwplugins/wiki/doku.php?id=jwlua:finaleplugin_properties#categorytags_string) to find an good starting place.` |
| 55 | +And if you get stuck, you can always [get help](/docs/getting-started/getting-help). |
| 56 | +
|
| 57 | +### 1. Clone the repository |
| 58 | +
|
| 59 | +You will only need to clone the repository once. If you've already cloned it (e.g., you already contributed a script), you can skip this step. |
| 60 | +
|
| 61 | +1. Once you've signed into GitHub Desktop, go to the repository on GitHub. [https://github.com/Nick-Mazuk/jw-lua-scripts](https://github.com/Nick-Mazuk/jw-lua-scripts) |
| 62 | +2. You should see a bright green button that says "Fork". Click it! Then click "Open with GitHub Desktop." |
| 63 | +3. This will bring up a dialog in GitHub Desktop. Note the folder where it says "Local Path." This is the location GitHub desktop saves your fork of the repository on your computer. You will need this later. |
| 64 | +4. Click "Clone" to fork the repository. This will save a copy of the repository on your computer. |
| 65 | +5. Success! You've now cloned the repository. |
| 66 | +
|
| 67 | +### 2. Add your script |
| 68 | +
|
| 69 | +Once you've written your script, you'll now be able to add it to the repository. |
| 70 | +
|
| 71 | +You may wish to double-check your script with the [script checklist](/docs/getting-started/script-checklist) before adding it. Don't worry, though. If there's something you missed, we'll help you out. |
| 72 | +
|
| 73 | +1. Find the cloned repository on your computer. This is the "Local Path" you noted earlier. |
| 74 | +2. Inside the repository folder, you should see another folder named \`src\`. This is where all the scripts are stored. Add your script file (e.g., \`note_resize.lua\`) to this \`src\` folder. |
| 75 | +3. Go back to GitHub Desktop. You should now see that one file was added. |
| 76 | +4. Next, let's name the commit. In the lower left corner of GitHub Desktop, you should see a text field that either says "Summary (required)" or "Add [script name]". This is is the name of your commit. Go ahead and make sure it says "Add [script name]" (e.g., "Add note_resize.lua"). |
| 77 | +5. Finally, let's commit the change. Again, in the lower left corner of GitHub Desktop, you should see a blue button that says "Commit to master". Click it! |
| 78 | +6. Success! You've now committed your change to the repository. |
| 79 | +
|
| 80 | +### 3. Create a pull request |
| 81 | +
|
| 82 | +Creating a pull request is the final step in adding your script to the repository. A pull request will merge your changes into the original repository. |
| 83 | +
|
| 84 | +If you've already contributed, skip the first three items and move to item #4: click "Push origin". |
| 85 | +
|
| 86 | +1. Go back to GitHub Desktop. At the top, you should see a button that says "Push origin". Click it! |
| 87 | +2. You'll receive a prompt to fork the repository. Select "Fork This Repository." |
| 88 | +3. Next, GitHub Desktop will ask you how you plan to use the fork. Select "To contribute to the parent project" because you want to contribute to the main repository for these scripts. |
| 89 | +4. Click the same "Push origin" button. This will sync your changes with GitHub's servers. |
| 90 | +5. Go to Branch > Create Pull Request in the menu bar. This will take you to github.com to create the pull request. |
| 91 | +6. On GitHub.com, click "Create Pull Request" |
| 92 | +7. Add a descriptive title and description, then press "Create Pull Request" |
| 93 | +8. Success! You've now created a pull request! |
| 94 | +
|
| 95 | +We will now review your script and merge it into the main repository. We may ask for some changes before it is merged, but we'll help you through that process if needed. |
| 96 | +` |
32 | 97 | </script> |
33 | 98 |
|
| 99 | +<Seo |
| 100 | + title="Adding Scripts" |
| 101 | + siteName="JW Lua Scripts Docs" |
| 102 | + description="Use Finale faster than the blink of an eye. Simplify workflows to just one click. All for free, forever." |
| 103 | + canonicalUrl="{`https://jw-lua-scripts-docs.vercel.app/${$page.path}`}" |
| 104 | + openGraph="{{ |
| 105 | + image: { |
| 106 | + src: `https://jw-lua-scripts-docs.vercel.app${luaLogo}`, |
| 107 | + width: 630, |
| 108 | + height: 630, |
| 109 | + }, |
| 110 | + }}" |
| 111 | +/> |
| 112 | + |
34 | 113 | <Markdown content="{content}" headerIds /> |
0 commit comments