The hardest part of WYSIWYG editors is always cursor
positioning and selection across mixed content.
How did you handle that? Also curious if you considered
using a canvas-based renderer vs DOM — what made you
go with your current approach?
at this point, a WYSIWYG just seems like a huge step backwards from just using markdown. I love having access to my files in a standard text format this is super easy to parse, and not being locked into whatever weird format that WYSIWYG decides to store it in.<p>I still don't understand why people still use ~~Microsoft Word~~Copilot document writer , I think they have gotten into some weird mindset that their documents require all this weird unnecessary formatting to look "official"
Markdown without formatting isn't usually the nicest to read imo. I actually appreciate a well laid out and formatted document myself.<p>Also wysiwyg doesn't mean it can't be back and forwards compatible with markdown, it might just mean that it's a markdown editor gui with a preview.
Yes. These days, with plain text, pasrsers, Internet, mobile devices and LLM, we really get more than what we see. Only few case where paper print out is still more useful.
I adore anything that avoids using a browser. <3
This took me down the nostalgic memory lane of the planet-source-code days. There were hundreds of such projects in Visual Basic, Delphi, C/C++/MFC etc., and text editors and paint clones were the most popular projects.
I thought the data structure part is solved:<p><a href="https://en.wikipedia.org/wiki/Rope_(data_structure)" rel="nofollow">https://en.wikipedia.org/wiki/Rope_(data_structure)</a>
On MacOS, I'm seeing `ModuleNotFoundError: No module named 'miniword.core.utils'` whether I run `python3 -m miniword` from src/miniword/ or from src/miniword/miniword/.
One feature missing from <i>almost</i> every mainstream word processor: REVEAL CODES! (<a href="https://kb.corel.com/en/127364" rel="nofollow">https://kb.corel.com/en/127364</a>)<p>This is a famous "killer" feature from WordPerfect: the ability to view and edit the low-level formatting for a document. It's invaluable for fixing weird bugs.<p>However, it works only because WP uses the "text-stream" paradigm, where a document comprises a linear stream of text with formatting codes (Bold, Font, Hard Return, etc.) embedded directly at the point at which they're applied.<p>In contrast, Word uses the "nested containers" model (characters inside words, words inside paragraphs, paragraphs inside sections, etc.), where this feature can't be replicated.<p>I didn't look closely at your code, but just thought to mention this feature.
This is great!<p>Curious about the choice of toolkit: what led you to wxPython?
I love seeing new word processor projects!
Looks like a nice project.<p>Looks like you missed a file, though.<p>ModuleNotFoundError: No module named 'miniword.core.utils'<p>I don't see it in my local clone of your repo, nor the repo iteslf.
Love to see wxPython!
[dead]