WonderPhi Office for organizations — perpetual single-organization commercial license

Everything below is identical to the retail product. What's different: your license covers the entire buying organization (unlimited machines, VMs, containers, cloud instances) with no seat count, no annual renewal, no telemetry, no activation. Redistribution / SaaS / hosted-service exposure require a separate OEM arrangement.

Easy Setup — No Package Manager, No Account, No Cloud

Single Python file. Python 3.8+ standard library only — nothing to pip install. Run with:

python wpo-recipe.py

Sample plan files ship with the download and run out of the box. Pair with WonderPhi Compute to execute the generated plans in parallel.

WonderPhi Office — 10 batch recipes for Microsoft Office

Ten hand-written recipes that automate Word, Excel, and PowerPoint via COM. Convert 500 .docx files to PDF in a coffee break. Extract every table from every spreadsheet in a folder. Batch-render slide decks. No macros, no VBA, no ribbon-hunting.

What it is, in plain English

Each recipe drives Word, Excel, or PowerPoint the exact same way a person would (open document, do something, save, close) — but scripted, one file per plan-line, running in parallel across your cores. No macros embedded in files. No third-party parsers to trust. Office does the work; the recipe just tells it what to do, on repeat, for a whole folder.

How you use it — three steps

1. Run the recipe file. python wpo-recipe.py in the folder that contains your input files, or wherever you want the plan written.
2. Point at the target. The recipe asks (or reads from a text file) what the input is — a folder, a list of hostnames, a CSV, whatever the recipe expects. It writes a plan file: one shell command per line.
3. Hand the plan to Compute. Drop the generated plan.wpc.txt into the WonderPhi Compute inbox, and every command runs in parallel across your cores. Read the honest log when it's done.

Worked examples — three of the 10 recipes in this library

word-to-pdf — convert every .docx in a folder

COM opens Word, converts each document to PDF, closes it, moves to the next. Parallel: as many Word instances as you have cores.

python wpo-recipe.py word-to-pdf --input ./documents --output ./pdfs

# generated plan:
# powershell -Command "$w = New-Object -ComObject Word.Application; ..." (one per file)

excel-to-csv — export the active sheet of every workbook to CSV

Reads every .xlsx/.xls in the target folder, exports the active sheet as CSV.

python wpo-recipe.py excel-to-csv --input ./workbooks --output ./csv

ppt-to-images — render every slide of every deck to PNG

One folder per deck. One PNG per slide. Useful for indexing decks, thumbnailing, or feeding to OCR.

python wpo-recipe.py ppt-to-images --input ./decks --output ./slides --width 1920

Under the hood — the honest technical picture

COM (Component Object Model) is Microsoft's standard for programmatic control of Office apps. This recipe library generates PowerShell one-liners that instantiate a Word/Excel/PowerPoint COM object per plan-line and drive it. Each plan-line spawns its own Office instance — Windows handles the isolation.

• No VBA, no macros. Nothing gets embedded in the files you process.
• PowerShell + COM. The generated plan-lines are one-liner PowerShell commands. You can read them; you could type them by hand.
• Office does the work. The recipe never parses Office file formats itself — it delegates to the real thing. So .docx quirks that trip up open-source parsers don't trip this up.
• Isolation per file. One crashed conversion doesn't take down the whole batch.
• Zero Python dependencies. Standard library only. The tools you need are Office itself and Python 3.8+.

How it compares to the manual way

What you need

• Windows 10 / 11. COM automation is Windows-only.
• Microsoft Office installed on the machine that will run the plan. Any recent version (2016+, 365).
• Python 3.8+ to generate the plan file. Standard library only.
• WonderPhi Compute to run the plan in parallel across cores.

What's in the download

• wpo-recipe.py — the recipe generator (Python 3.8+, standard library only)
• README.md — per-recipe reference for humans
• INDEX.md — alphabetical list of every recipe with a one-line description
• samples/ — ready-to-run demo input files for every recipe
• LICENSE.txt — perpetual single-user license, personalized with your name and order number at delivery

Common questions

License & support — Industrial variant

Perpetual, non-exclusive, non-transferable Industrial license. Covers all machines, VMs, containers, and cloud instances operated by a single organization (the legal entity named on the purchase receipt plus wholly-owned subsidiaries). No seat count, no machine limit, no renewals, no activation, no telemetry.

Employees, contractors, and consultants under the organization's direction may operate the software solely for the licensed organization's benefit. Rights end when their engagement ends.

Not permitted without a separate arrangement: redistributing the software; hosting it publicly; embedding it in a product/SaaS/PaaS you sell to third parties; sublicensing.

Support: email chris@cri-one.com.

Every download's LICENSE.txt is personalized at checkout with your organization name, order number, and issue date. USA sales.