will
52d94303bc
ci / test (push) Has been cancelled
Public demo snapshot of an in-house pyRevit extension for precast concrete shop-ticket QC (37 checks / 46 checklist rows) and a standalone panel handling solver (PCI Chapter 8). - No client, job, plant or product data: knowledge layers ship as structural templates only. - Ticket QC's model-read escalation targets a LAN model server endpoint (configurable), not a cloud provider. - Built from the private development repo via tools/make_dist.py.
25 lines
1.3 KiB
YAML
25 lines
1.3 KiB
YAML
title: "Ticket\nQC"
|
|
# DEV. A fresh IronPython engine for every press: `lib/vibe` is re-imported
|
|
# on each click, so an edit to a module this button uses is visible without
|
|
# a Revit restart. It trades press latency (engine construction instead of
|
|
# engine reuse) for restart-freedom, and it is the hottest button here --
|
|
# 51 commits to its six modules in the seven days to 2026-08-30.
|
|
#
|
|
# Read docs/architecture-migration.md section 8 before trusting or removing
|
|
# this. Two things it says that are not obvious: pyRevit's DEFAULT is already
|
|
# a clean engine, and this extension gets one today only because
|
|
# extension.json has no `url:` and so is never registered as a package --
|
|
# add a url and every button silently switches to the shared engine. This key
|
|
# is the pin against that, not a new capability.
|
|
#
|
|
# REMOVE IT PER BUTTON as that button stabilises: delete the two lines below.
|
|
engine:
|
|
clean: true
|
|
# No tooltip and no author on purpose. pyRevit renders both on hover;
|
|
# the owner wants nothing there. Guarded by
|
|
# WillTools.extension/tests/test_button_tooltips.py -- do not add them back.
|
|
#
|
|
# Two lines, short ones. A large ribbon button is as wide as its widest line
|
|
# of text, so a long title makes one button dwarf its neighbours -- which is
|
|
# exactly what the owner objected to. Keep every line under ~9 characters.
|