u/Efficient_Lead3565 — reddlx

The workflow: paste anything, HTML scraped from a site, CSV from an ERP export, ASCII from terminal output, pipe-delimited text. It drops it into a live visual editor. Drag columns, merge cells, split text, transpose. Then generate clean code into a Monaco editor instance.
The SQL export is the thing I use most. Paste a CSV, get INSERT INTO statements ready to run. Most table tools skip this.
Zero dependencies, zero install, runs entirely in the browser. MIT licensed.
Would genuinely love to know: what table format causes you the most pain in your workflow? I want to know what input cases are broken.
Live: Table Formatter and Node Editor
GitHub: TAFNE

u/Efficient_Lead3565 — 8 days ago

▲ 2 r/roastmystartup+1 crossposts

I built a browser-native tool and want the harshest feedback possible.

Table formatter and Node Editor (TAFNE): https://ginexys.com/tools/table-formatter

A tool part of the Ginexys Native Developer Tool pipeline.
I’m not looking for reassurance. I want you to tell me what is confusing, broken, unnecessary, or missing entirely. If the naming, layout, empty state, or workflow fails to make the use case obvious, call it out. Phase 1 on both is fine. I mainly want to learn where the idea is weak.
If you want the most useful roast, please focus on:
• What problem you think each tool solves.
• Where the UI makes you hesitate.
• What you expected to happen that didn’t.
• What would make you abandon it immediately.
• What existing tool this should be compared against

u/Efficient_Lead3565 — 4 days ago

▲ 3 r/ElectricalEngineering

open-source schema editor that ingests the image, identifies the symbols, traces the connections, and outputs a structured JSON graph you can actually query and edit

u/Efficient_Lead3565 — 14 days ago

▲ 2 r/coolgithubprojects+1 crossposts

Ginexys, a suite of developer tools designed to run entirely locally.

Current Tools:

• Schematic Engine: A visual node-based editor for mapping out logic and systems.

• TAFNE (Table Formatter): Import CSV/TSV and instantly generate clean HTML/Markdown tables or JSON.

The Tech Stack:

• Local-first: Everything happens in your browser/machine.

• Lightweight: Built with Svelte and TypeScript.

• Open Source: MIT.

Source & Docs: https://github.com/carnworkstudios

u/Efficient_Lead3565 — 15 days ago

▲ 3 r/HTML

A flat table has one coordinate system: the nth <td> in the mth <tr> is at visual position (m, n). Trivial.

Once you introduce rowspan and colspan, the DOM coordinate and the visual coordinate diverge. A cell with colspan="3" sits at DOM position (row 0, child 1) but occupies visual positions (0,1), (0,2), and (0,3). A cell below it, in the same row at DOM child 1, is visually at column 4, not column 1. DOM child index is now a lie.

Every feature that touches column position needs to know the visual coordinate, not the DOM coordinate. Crosshair highlighting, column drag-and-drop, transpose, selection, all of them.

I solved this with VisualGridMapper, a class that does a single O(n) pass over the table and builds a 2D array where grid[row][col] points to the DOM element occupying that visual cell. The tricky part is rowspan: a cell that spans 3 rows occupies slots in rows it doesn't appear in the HTML. The mapper handles this with a while loop that checks whether a slot is already claimed before filling it.

The grid entry includes an isOrigin flag. It's true only at the cell's actual DOM position, false at phantom slots. Features check isOriginbefore acting, so spanning cells never get moved or processed twice.

All column-aware features in TAFNE are built on top of this mapper. Without it, anything involving merged cells would silently corrupt the table.

[GitHub](github.com/carnworkstudios/TAFNE)

github.com

u/Efficient_Lead3565 — 19 days ago