Addons are sourced from github, but otherwise there is nothing specific to github about them.
They must comply with some basic rules, see https://code.jsoftware.com/wiki/Addons/Developers_Guide but otherwise are free form. Jqt isn't needed. > I inadvertently overwrote the main file in my github-based installation when I built with the Jqt project build. Addons should be installed under ~addons with two-level subdirectories. The github installation should write to the target directory. Your Jqt project can also write to that directory, but it doesn't have to. On Fri, Jun 25, 2021 at 6:31 PM John Ference <john.fere...@gmail.com> wrote: > I'd like to create an add-on in the way that is envisioned as the standard > for J package manager. I'd also like to store this package on github. > > There are multiple files in the package I've created. > > 1) I first created a project in Jqt, with the 'new project' template. I > followed the process to build with Ctrl+F9 and run with F9. > Building created a single file that was loaded to ~addons/. > > 2) Then I realized that the ‘build’ concept with .jproj didn’t seem to fit > with the GitHub repo approach. > In the github repo approach, all files are referenced by path, > relative to ~addons/. > > These two approaches don't appear to mesh: > I inadvertently overwrote the main file in my github-based > installation when I built with the Jqt project build. > > What is the expected usage / future vision for how projects (created via > Jqt project templates) relate to Github-based package installation? Ideally > the template in Jqt accommodates that method, and an example could be > documented. > > Thank you, > John > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm > ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
