You are browsing as a guest. Sign up (or log in) to start making projects!

Open comments for this post

2h 40m 58s logged

the polish commit (that didn’t polish enough)

okay so this commit looks massive and impressive on paper. I touched basically everything. and the code changes are real. but I need to be honest: the app still looks and feels terrible.

like, genuinely bad. the UI is broken in ways that make me want to close the window and pretend I never opened it.

but the changes are real so let me document them anyway.


layout tuning

repulsion went from 1000 to 8000, attraction from 0.01 to 0.004, ideal_length from 50 to 220. notes were clumping into an unreadable blob. the physics are better now even if you can’t tell because the rendering is fighting itself.


theme overhaul

flattened the entire theme system into one struct with semantic names. every hardcoded color replaced with CSS vars. dark and light themes. toggle in settings. this part actually works correctly and I’m proud of it even though nobody can see it because the layout is broken.


TipTap editor

replaced the textarea with TipTap via JS eval. StarterKit with bold/italic/strike/code/headings/lists. toolbar with format buttons. sends HTML back via dioxus.send(). this is genuinely nice when it works. which is actually most of the time wow.


manual linking, note list, auto-linking on save, context menu, keyboard shortcuts, zoom controls, empty state

all implemented. all technically functional. all look like they were designed by someone who has never seen a GUI before. (me. I’m that someone. i am not good at RSX, which is funny because it SHOULD just be a different form of HTML. you would think.)


what I learned

dioxus-desktop’s webview is not a browser with devtools. iterating on UI by recompiling a Rust binary every time you move a div 2 pixels is actual torture. I should have designed the UI in plain HTML first, gotten it looking right in a real browser with real devtools, and THEN ported it to rsx.

I did not do that. I have been doing it backwards this entire time. smh my silly head.

next step: HTML mockup first, then port. the backend is solid. the architecture is clean. the UI just needs to catch up.

still broken but less broken than before. progress? maybe?

onwards (to HTML mockups) :}

0
2

Comments 0

No comments yet. Be the first!