![]() Kit will pull it from the registry and start. So for instance if the example from above is published, we can just run Kit as: For regular extensions, specify the keyword: package.app = true in the config file to mark your extension as an app that users can launch.Īpp extensions can be published, versioned, etc. ![]() kit file) extensions are considered apps, and a “launch” button is added to it in the UI of the extension browser. kit file as an extension and enables it, ignoring any default app configs, and effectively starting an app. Is the same as: > kit.exe -ext-path C:/abc/ -enable kit files are passed to kit.exe they are treated specially: kit file extension, so that it can be associated with the kit.exe executable and launched with a single click. toml for instance), but the recommendation is to name them with the. They are used as an application entry point, to unroll the whole extension tree. This is used to make a top-level extension which we call an app. In this case the name of the config will be used as the extension ID. Extensions consisting only of a config file, without any code. Single file Extensions are supported - i.e. Python version or kit version can also denote different target. It is common for binary extensions to have packages like: One extension id can have 1 or multiple packages in order to support different targets. 1.2.3-beta.1 Extension Package Id Įxtension package id is extension id plus build metadata. Express compatibility with version change:įor breaking change increment major versionįor backwards compatible change increment minor version A good example of valid and invalid versions: link Can also be part of folder name, but ignored there.Įxtension id example: -1.2.3-beta.1. Used to have different implementations of the same extension. Extension Id Įxtension id consists of 3 parts: -: This example contains a Carbonite plugin and a python module (which contains the bindings to this plugin). Looking at other package managers, like those in the Linux ecosystem, the content of packages can be spread across the filesystem, which makes some things easier (like loading shared libraries), but also creates many other problems.įollowing this convention makes the installation step very simple - we just have to unpack a single folder.Ī typical extension might look like this: This is a convention we are trying to adhere to. Extension in a single folder Įverything that an extension has should be contained or nested within its root folder. There are many variations, you can have an extension whose sole purpose is just to enable 10 other extensions for example, or just apply some settings. The Extension system will find that extension and if it’s enabled it will do whatever the config file tells it to do, which may include loading python modules, Carbonite plugins, shared libraries, applying settings etc. Extensions in-depth What is an Extension? Īn extension is, in its simplest form, just a folder with a config file ( extension.toml).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |