![]() ![]() To distribute your theme to others you will need to compress it into a zip archive. These are playPause(), forward() and back(). Themes can control playback by calling methods of the window.Player object. If you wish your theme to display at a different size then implement the function and return a single rectangle object. By default themes are shown in a window that is 480 pixels wide and 200 high: anything larger than that will be cut off. The windowSize() function allows you to customise the size of the theme. Below is an example implementation of updateWithNewTrack: function updateWithNewTrack ( trackDictionary, paused, stopped ) This function is called by Swinsian when a track starts to play and you should use it to update the page with the new tags and artwork values. ![]() The index.html page must include a Javascript function called updateWithNewTrack(). The index.html page may reference other resources such as images in the Contents/Resources directory. The SwinsianThemeVersion value should be 2. The ThemeName value should be replaced with the name of your theme - this is the name that will show up in the Swinsian preferences window. The CFBundleIdentifier / 'Bundle Identifier' value should be something unique for example your name followed by the theme name. You should replace the values in the example file with ones appropriate for your theme. The ist file contains several fields that describe the theme. ![]() The proper location for these is shown in the file layout below: Info property list There are two files that must be present in every theme: the property list file that describes the theme (ist) and the main html file (index.html). ![]() To view the contents right click and select Show Package Contents. Themes are standard OS X bundles (folders that the system treats like files). Download it from the link below and expand the zip file: The easiest way to get started writing your own theme is to modify the example theme. Creating custom themesĭesktop art themes are written in HTML and Javascript. You can use themes to customise how the track tags and artwork are displayed. All other labels are treated as patches that do not change the API.Swinsian allows you to display information about the current track on your desktop. The issue-labels input allows to define issues labels that should be considered as minor versions (API extensions). This is useful when generating or applying tags. The tag input allows to use a custom tag for tagging. This output is unavailable, when the tag input is used. The previous latest tag before this action ran. Optional A comma-separated list of issue labels that changes the bump level from patch to minor (Default: enhancement). Will not perform any version bumping, but adds the provided tag. Optional Custom tag to be added to the current SHA. Optional A comma-separated list of branch names or regular expressions. This is useful when tagging of merge requests. This input is useful if subsequent steps manipulate a different branch, which should get tagged. This is useful if the triggering action's branch is different to the final action. Optional Sets a branch to perform the action on. Optional If not FALSE (case insensitive), then the action adds a v to prefix the tag. Valid values are major, minor or patch (Default: patch) with-v It is very handy if a build or cleanup steps will extend the initial commit or merge request. This input is useful if the release version has to be known for other steps before actually tagging the final commit. Optional If the value is not FALSE (case insensitive), the action performs all steps, but omit the actual tagging. Required The github token for accessing the repository. This action has been inspired by anothrNick/github-tag-action, but is written completely in javascript and runs directly within the runner.Īutotag-action uses Octokit for tagging and does not depend on checking out the repository. autotag-action also supports prereleases for non-release branches and custom tags. If a commit message fixes an issue (using fixes #issuenbr style messages), then autotag-action will check wether the corresponding issue was labled as enhancement that triggers a minor release, or a bug fix that will be treated as a patch. Use #major, #minor, or #patch tags in your commit messages and autotagger will increase your version tags accordingly. This action scans your commit messages for fixed issues and semver changes. It helps you to stay on top of your release management and release your code quickly and often through GitHub's tag-based release functions just by pushing to your repository. A lightning fast autotagger for semver-tagging. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |