TapirFrom the Tapir palette
Right-click your script and choose Share: add a few words about it and send. Until your palette has it, use Discord.
Three ways to send it
On Discord
Post the script in the #share-a-script channel, with a few words on what it does and which Archicad version you use.
As a pull request
Add a folder marketplace/<name>/ with the script, a listing.json and a README, as the marketplace README describes.
Only the script
The file, your one-line description, the name to credit, and your Archicad and Tapir versions. Nothing from the open project.
Free for everyone
Every shared script is free and open source. Unless you choose another open-source licence, yours is published under the MIT licence: anyone may use, change and share it, as long as they keep your name and the licence with it. It comes without warranty. You stay its author, and its page credits you.
Only share a script you wrote, or one whose author agreed to share it.
What the AI changes.
It keeps what your script does. It changes how, so the script is safe and works in other offices, and lists every change in plain words in the pull request.
Removed, or flagged for a maintainer
- connections to anything other than Archicad on your own computer;
- running other programs or code built from text (
subprocess,os.system,eval,exec); - installing packages while it runs (
pip install); - deleting or overwriting files, and writing anywhere but the project's folder and
Documents/Tapir; - passwords, tokens and keys;
- user names,
C:\Users\…paths, and project, client and office names, in the code and its comments.
Settings instead of your names
- Property names, layers, stories, paths and classification codes you typed in become settings at the top of the script, or fields of its window.
- Built-in properties are found by their ID, so the script works in every language of Archicad.
- Lengths and areas work in metric and imperial units; paths work on Windows and macOS.
No surprises
- It says what it is about to change, and does nothing, saying so, when nothing fits.
- It makes its changes in one Undo step where it can.
- When a property or element type it needs is missing, it shows a clear message instead of crashing.
A README in plain words
- What it does, how to use it, its settings, what it changes, its limits, and Original by you.
- Its category, the Archicad and Tapir versions it works with, and whether it changes the model, writes files or only reads.
What the review checks
Every pull request is reviewed before it is merged, like any other code in Tapir. The review checks that:
- nothing on the Made safe list is left in, unless a maintainer agreed to it;
- the script still does what you wrote it for, and you confirmed that;
- the folder has the files and fields the marketplace format asks for;
- the README is accurate, and the screenshots show no client, project or people.