Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Monosketch

monosketch.io

Post reply on HN
Print view View original

131–140 of 144 posts

Re: Monosketch

#131

Post by dchuk »

tristanMatthias wrote: post #56
dchuk wrote: post #55

Pretty cool (and the linked in the comments monodraw I’m buying today it looks great too). I’ve actually been tinkering with a web app (as a test bed for various spec driven dev frameworks with Claude code) a wireframing tool for TUI apps. Conceptually similar to figma almost, infinite canvas and all that jazz, but has premade components for the Ink TUI library (idea would be to support a few popular TUI frameworks e…

Love this idea. Would be cool to have a wysiwyg for https://ratatui.rs

Yeah my thought was to eventually cover Ink, ratatui, charm (and bubbletea /lipgloss), and opentui

It’s pretty simple to do this now with the frameworks you can use to spec work and execute on it with Claude code. I’ll keep chipping away at it and launch it at some point

Re: Monosketch

#132

Post by iamtuna »

SAI_Peregrinus wrote: post #59

That circuit schematic in the header is wrong enough to look like an AI-generated hallucination of what a schematic is from the "human with extra fingers" stage of image generation. Inconsistent symbol styles, missing pin labels, a shorted capacitor in the upper-left, etc.

Ha! Good eye. That circuit was actually replicated from the Google Typograms example here: https://google.github.io/typograms/#circuits - so any schematic errors are faithfully reproduced from the original

I used it as a demo to show what MonoSketch can create, but you're right that it's not electrically sound. Maybe I should switch to a different example that won't make electrical engineers wince!

Re: Monosketch

#133

Post by iamtuna »

It's Tuna, the creator of MonoSketch here!

Thank you all for the warm reception! I honestly went back and forth about sharing this project - I kept feeling like it wasn't ready yet, with critical features still missing and UI/UX I'm not satisfied with.

But this response has been incredibly encouraging! I'm taking notes on all the feedback around export visibility, rectangle interactions, multi-project workflow, accessibility, and more.

It's really motivating to see people finding MonoSketch useful despite its rough edges. This kind of feedback is exactly what helps make it better.

Thank you!

Re: Monosketch

#134

Post by lsaferite »

GlacierFox wrote: post #111
meatmanek wrote: post #96

Earlier quoted context omitted.

https://github.com/tuanchauict/MonoSketch/blob/main/LICENSE

Why have you sent me the licence page for Monosketch? I'm commenting on comment about Monodraw...

I would assume they sent that because they were suggesting to support FOSS over closed-source software.

Re: Monosketch

#136

Post by efreak »

Sharlin wrote: post #106
wingmanjd wrote: post #21

Earlier quoted context omitted.

Doesn't it have those characters via extended ASCII? I seem to recall making boxes with characters back in my BASIC class.

As brazzy said, there's no such thing as extended ASCII. There's just a huge number of ASCII-compatible eight-bit encodings. The original IBM (and DOS) character set, hardwired into ROM, is the one you're thinking of, and went by various names such as "Personal Computer, MS-DOS United States, MS-DOS Latin US, OEM United States, DOS Extended ASCII (United States), PC-ASCII" [1]. DOS 3.3, in 1987, was the first version…

> Why the apparently arbitrary numbers, I'm not sure, but Claude and ChatGPT both claim the codes were simply drawn from a more general-purpose sequence of product numbers used at IBM at the time.

Claude and chatgpt are (probably) wrong. Wikipedia has 3 citations for the following statement:

> Originally, the code page numbers referred to the page numbers in the IBM standard character set manual

The reason they're so high is because code pages were assigned to EBCDIC first.

Re: Monosketch

#137

Post by efreak »

subjectsigma wrote: post #130
kens wrote: post #90

Earlier quoted context omitted.

My unpopular opinion is that programming is stuck in the 1970s: a lot of programmers use a 1970s-style terminal window to enter 1970s OS commands, which run on a 1970s processor architecture (which is slowly getting replaced by a 1980s architecture). They use a 1970s editor (which is much superior to the other 1970s editor) to write programs in a 1970s language. ASCII diagrams are just a symptom of this. Hardware is…

I was thinking about this the other day - I watched a video about the acme editor and it was showing off text editing in a shell buffer, much like M-x shell. I realized I haven’t yet found a terminal emulator that will let you select text with a mouse while you’re editing in the shell. It’s such a simple thing that would be so useful, especially on a Mac where CUA bindings don’t conflict with terminal escape codes. i…

Windows Terminal allows this, afaik. It might be a feature of clink, but I feel like I've seen it in powershell and cmd both. Not sure if it's available in traditional console window, I rarely use those much these days though (sudo on windows is nice, the only reason to use an elevated window is for multiple commands, like browsing system directories you don't have access to; I just wish it had a different 'official' name)

Re: Monosketch

#138

Post by Sharlin »

efreak wrote: post #136
Sharlin wrote: post #106

Earlier quoted context omitted.

As brazzy said, there's no such thing as extended ASCII. There's just a huge number of ASCII-compatible eight-bit encodings. The original IBM (and DOS) character set, hardwired into ROM, is the one you're thinking of, and went by various names such as "Personal Computer, MS-DOS United States, MS-DOS Latin US, OEM United States, DOS Extended ASCII (United States), PC-ASCII" [1]. DOS 3.3, in 1987, was the first version…

> Why the apparently arbitrary numbers, I'm not sure, but Claude and ChatGPT both claim the codes were simply drawn from a more general-purpose sequence of product numbers used at IBM at the time. Claude and chatgpt are (probably) wrong. Wikipedia has 3 citations for the following statement: > Originally, the code page numbers referred to the page numbers in the IBM standard character set manual The reason they're so…

Yeah, I later found that quote on Wikipedia too. Though I don't think the cited source is super reliable either, or just folklore ("Oh, 'code page' refers to actual deadtree pages"). All the IBM documentation I could find showed big gaps in the sequence of code pages.

But I just now found the list at [1], I don't know why I didn't notice it before. It's certainly comprehensive! There's been some real detective work to be done in compiling that list. The gaps are much smaller, though still exist, eg. from 40 to 251. The 300s are rather sparse, there are only a few 4xx codes, and then there's a jump from 500 to 8xx (with some 7xx assigned later I think).

In any case, I agree that the LLMs seem to have hallucinated the "more general sequence" part. The code page IDs, or more formally CCSIDs, always were a specific set of 16-bit ID numbers. Why exactly the various gaps exist is probably lost in history by now, if there ever even were any particular reasons.

[1] https://en.wikipedia.org/wiki/Code_page

Re: Monosketch

#139

Post by SAI_Peregrinus »

iamtuna wrote: post #132
SAI_Peregrinus wrote: post #59

That circuit schematic in the header is wrong enough to look like an AI-generated hallucination of what a schematic is from the "human with extra fingers" stage of image generation. Inconsistent symbol styles, missing pin labels, a shorted capacitor in the upper-left, etc.

Ha! Good eye. That circuit was actually replicated from the Google Typograms example here: https://google.github.io/typograms/#circuits - so any schematic errors are faithfully reproduced from the original I used it as a demo to show what MonoSketch can create, but you're right that it's not electrically sound. Maybe I should switch to a different example that won't make electrical engineers wince!

It makes me instantly assume the software is low-quality.

Re: Monosketch

#140

Post by trcf23 »

satvikpendem wrote: post #129
trcf23 wrote: post #126

Earlier quoted context omitted.

But the point is to have something easy to read both for humans and LLM, no? It’s harder to read mermaid in a terminal or a markdown file…

Mermaid diagrams automatically render on Markdown and IDE chat windows as in VSCode or Cursor. So you get the best of both worlds, a graph you can look at a ND manipulate with the mouse but also in a format LLMs can read.

Ah thanks I didn’t know that…
Post reply on HN