4D Method Runner

Run a 4D project method with the right runtime.

Choose the Runtime First

• Use tool4d for most test-like runs, especially when --dataless is acceptable.
• If it is unclear whether the method needs the full runtime, try tool4d first. If that run fails for reasons that look specific to tool4d or missing database/runtime support, then switch to the full 4D runtime.
• Use the full 4D runtime when the method depends on a real data file, database state, UI/runtime features missing from tool4d, or the user explicitly says tool4d is insufficient.
• Do not try to discover the 4D runtime automatically. Ask the user for the path to 4D.app, the inner 4D binary, or 4D.exe.

Prefer this fallback strategy because it is usually faster than deciding up front from incomplete context.

Finding tool4d

tool4d can be located in two ways:

1. Environment Variable