This is great. It works well for some docx files I have that don't work well in LibreOffice or any other non MS word. I do also have one that splits across 2 pages that I got down to 1 in MS word.
Thank you for developing this AND thanks a ton for making it Open Source with the MIT license.
Very cool!! I'll give it a spin! I've been using a similar approach for building a tool for agents to drive a running instance of MS word. The closed-testing loops are very powerful with agents.
I had this problem too - I just found that the inconsistency of the the LLM vision + pressure of either having to write OOXML from scratch, or control the app via computer use just didn't really give great results (mostly words fault). Ultimately, for non browser DOCX creation I had more success using some kind of IR that compiles to OOXML.
edit: not to toot my own horn here - but I am definitely squeezing out more perf on longer documents. My upper end bench mark document was ~500 pages and key presses, new line creation etc. all sits around 20ms with this package.
This is great. It works well for some docx files I have that don't work well in LibreOffice or any other non MS word. I do also have one that splits across 2 pages that I got down to 1 in MS word.
Thank you for developing this AND thanks a ton for making it Open Source with the MIT license.
Yep all of that was exactly my problem too lol - if you have any docs that render poorly make an issue and I'll work on supporting it.
Very cool!! I'll give it a spin! I've been using a similar approach for building a tool for agents to drive a running instance of MS word. The closed-testing loops are very powerful with agents.
I had this problem too - I just found that the inconsistency of the the LLM vision + pressure of either having to write OOXML from scratch, or control the app via computer use just didn't really give great results (mostly words fault). Ultimately, for non browser DOCX creation I had more success using some kind of IR that compiles to OOXML.
I’m impressed! Did you fork Eigenpal docx editor and build on top?
No this was built ground up.
edit: not to toot my own horn here - but I am definitely squeezing out more perf on longer documents. My upper end bench mark document was ~500 pages and key presses, new line creation etc. all sits around 20ms with this package.
Thanks for this. Looking fwd to try it out.
May I inquire about privacy? All stays local in browser?
yes, projects are saved to local storage in the demo.
Rad. Thanks for sharing! Will give it a spin and check out the repo.
I didn’t know I wanted this until now. Great work.
This is excellent.
Deserves a lot more Github stars!
[dead]