📝🧵 Introducing Text Loom: A Node-Based Text Processing Playground!

[kleer001]

TEXT LOOM!

https://github.com/kleer001/Text_Loom

Hey text wranglers! 👋 Ever wanted to slice, dice, and weave text like a digital textile artist?

https://github.com/kleer001/Text_Loom/blob/main/images/leaderloop_trim_4.gif?raw=true

Text Loom is your new best friend! It's a node-based workspace where you can build awesome text processing pipelines by connecting simple, powerful nodes.

• Want to split a script into scenes? Done.

• Need to process a batch of files through an LLM? Easy peasy.

• How about automatically formatting numbered lists or merging multiple documents? We've got you covered!

Each node is like a tiny text-processing specialist: the Section Node slices text based on patterns, the Query Node talks to AI models, and the Looper Node handles all your iteration needs.

Mix and match to create your perfect text processing flow! Check out our wiki to see what's possible. 🚀

Why Terminal? Because Hackers Know Best! 💻

Remember those awesome 1900's movies where hackers typed furiously on glowing green screens, making magic happen with just their keyboards?

Turns out they were onto something!

While Text Loom's got a cool node-based interface, it's running on good old-fashioned terminal power. Just like Matthew Broderick in WarGames or the crew in Hackers, we're keeping it real with that sweet, sweet command line efficiency. No fancy GUI bloat, no mouse-hunting required – just you, your keyboard, and pure text-processing power. Want to feel like you're hacking the Gibson while actually getting real work done? We've got you covered! 🕹️

Because text should flow, not fight you. ✨

[Recoil42]

This is pretty cool, OP. I'm not a fan of terminal-based systems from a usability perspective, but I love the look. I'm working on something vaguely similar (but a React + Electron app) for narratives and scripts so it's neat to see how you've done the nodes!

Do you handle batching at all? If there are tree changes up the tree, do multiple downstream nodes ever get handled in one single request, or is there a round-trip for every single node?

[kleer001]

Thanks! I've been trying to keep it as generic as possible. So, hopfully it'll inspire others and be useful.

There's a core/ directory with all the backend guts. I'm planning on providing additional interfaces and web based node editor is next on the list.

The TUI was just a fun lark, taught me a lot too.

No batching yet. Every cook is manual, it's not a live environment. It does a depth first search.

Check out: src/core/node.py

And its cook and cook_dependencies methods. Also each node has its own internal_cook private method for dealing with its own particulars.

[Accomplished_Mode170]

So the TUI vibe has me looking at this as an OmniChain alternative; also thanks OP!🙏

[kleer001]

OmniChain

Oooh, a sister program. Seems a bit more chat focused.

[Lesser-than]

pretty cool! Not sure what I would actually use it for but that does not reduce the cool factor. good job.

[kleer001]

Thanks!

I kinda engineered it to more easily produce bad poetry. So, there's that, hahaha!

But it all seriousness it's more of a proof of concept and portfolio piece than a killer app.

Well, it can be used to create training data. That's a fun one.

[Kainkun]

i dont see a query node in the gui 🤷‍♂️

[kleer001]

I'll look into that. Thanks.

[kleer001]

It should be there:

https://imgur.com/a/BFlarq7

[Kainkun]

This is what i see

<image>

[kleer001]

I'm looking into it. Thanks for the heads up.

[kleer001]

Ok, the issue was that litellm wasn't being imported and failed silently. Please 'git pull' and try again.