Tapir / Community / Roadmap

What's next.

Tapir grows from requests. Most new commands, components and fixes start as a message from someone who needed them in their own work.

How to ask for a feature.

Four steps from "I need this" to a Monday release.

  1. Say what you want to do

    Post it on Discord or open an issue on GitHub. Describe the task in Archicad, not only the command: "number the doors along a line", "read the area of every zone". A Discord message that reads like a feature request becomes a GitHub issue by itself, labelled enhancement.

  2. Asking for a part of the Archicad API?

    The API coverage page lists every function of the Archicad API and whether Tapir has a command for it. Use the Archicad API request issue form to ask for one that is missing.

  3. The issue bot picks it up

    A clear, wanted request is built like a fix: the bot writes it and opens a pull request, and you are asked to try it. A large one is split into parts. When the design is open, the bot describes the choices and a maintainer decides.

  4. It ships on a Monday

    Merged changes are released every Monday. The release notes list them, and the add-on offers to update itself.

What is being asked for now

Already here.

Asked for on the old site's "What's cooking" list, and now part of Tapir.

Still open.

Two ideas from the old list that nobody has asked for in an issue yet. Want one? Open the issue.

Idea

Clearer error messages in Python

Tracebacks and command errors that say what went wrong and how to fix it, so a script is easier to troubleshoot.

Ask for it
Idea

Tapir scripts in CI

Running Tapir scripts automatically, for example in a GitHub Actions pipeline.

Ask for it
Missing something in your work?

Tell us what you want to automate

Open an issue, or describe it on Discord and the bot files it for you.