> (I know, “ASCII art” colloquially means more than just the ASCII range.)

I recall "ASCII art" always referring to art made with the 7-bit character set, and art made with the extended CP437 characters (and including color, etc.) always being called "ANSI art".

They sort of are.

I think the confusion arises because the IBM PC ASCII (code page 437) included comprehensive box-drawing characters between hexidecimal character positions B3 and DA. These weren't adopted into Unicode in the same character positions, but the box-drawing characters were definitely part of the commonly understood ASCII character set.

But I think that this ASCII tree editor should have a toggle option for basic vs extended ASCII, by utilising +, -, and | characters.

My understanding of ASCII was influenced by tools like ASCIIDraw and ASCIIFlow, which I used them like almost 10 years ago. Inside my mind there's a voice with the same opinion of yours, but I still quite used to call plain-text drawings as "ASCII". LOL

Indeed! I was disinclined to even look at this project because it said ASCII when the box-drawing characters are obviously a lot more suitable. It should say “text-only” or “plain-text” or similar instead.

That's pretty neat! My motivation is to manipulate tree structures to provide them to LLM. Retree does the opposite, taking tree text as input to create a real file system hierarchy. Next time I want to create a new project based on the tree I edited through ASCII Tree Editor, I can use retree to do this.

Thank you, I'm glad you find it useful! The reason I didn't implement auto-parsing in the text editor is that I want it to avoid affecting the tree component on the left side. Sometimes, I like to write something before copying the tree. It's like a scratchpad for me to finalize the text I want. Also, since it's auto-generated, if it were also auto-parsed, it could cause an infinite loop whenever anything is changed.

Drag-and-drop functionality was actually the first thing I considered. However, I want to keep the code clean and avoid involving too many third-party libraries. So, I came up with this method to make reordering easy while keeping it simple to implement.

I will submit it to Superlaunch, although I feel that it might not be valuable enough to be considered a product :)

Thank you for bringing this issue to my attention. I forgot to publish it to GitHub Pages, which caused the reorx.github.io/asciitreeman link to be inactive (I've just fixed that). However, the main link for this news should be working, as it is deployed on Cloudflare. If you cannot see it, it is likely an edge CDN problem with Cloudflare.

Totally agree and I've already mentioned that in the post, the prompts are in CLAUDE.md and spec.md, actually, my purpose of providing the repo url is for anyone interested to check the prompt, not the source code.

For your convenient, here's the link (it's written in Chinese, that what I really forget about): https://github.com/reorx/asciitreeman/blob/master/spec.md