[Suggestion] Use standard MD Tables #64

and4po commented 2026年05月20日 17:34:03 +02:00

Hi, thanks for building this great app!
I was asking myself if it would be possible that by default, if any of the styles haven't been changed, tables are standard Markdown tables? I understand that it is easier to manage them in HTML when having different colors or so, but when they are just plain tables, why not following the standard Markdown specification? It ensures that the notes will remain readable for any Markdown app forever.

Thanks!

PS: Just out of curiosity, has been the app heavily built by AI? The commits look a bit strange and the app itself seems to be processing extremely fast... I would like you disclose it as a matter of transparency, the same way the app code is open, and the app is free software, there are people who care about those kinds of things.

Hi, thanks for building this great app! I was asking myself if it would be possible that by default, if any of the styles haven't been changed, tables are standard Markdown tables? I understand that it is easier to manage them in HTML when having different colors or so, but when they are just plain tables, why not following the standard Markdown specification? It ensures that the notes will remain readable for any Markdown app forever. Thanks! PS: Just out of curiosity, has been the app heavily built by AI? The commits look a bit strange and the app itself seems to be processing extremely fast... I would like you disclose it as a matter of transparency, the same way the app code is open, and the app is free software, there are people who care about those kinds of things.

ArkHost commented 2026年05月20日 18:02:55 +02:00

Hi, thanks for the feedback and for using the app.

Regarding the tables: valid point about portability. Currently, the editor saves tables as HTML to easily support dynamic features like cell styling, backgrounds, and specific alignments without breaking the layout. Detecting when a table is completely plain and dynamically switching between standard Markdown pipe syntax and HTML on save is a solid idea, but it adds code and parser complexity. Because of this, it is not an immediate priority, but I will keep this issue open to track it for the backlog.

Regarding the AI question: yes, I use AI assistance extensively. It helps me quickly research optimal approaches, write boilerplate, and speed up development or find bugs. This is why development cycles are faster and commit styles might look a bit different.

Thanks again for the feedback and the suggestion.

Hi, thanks for the feedback and for using the app. Regarding the tables: valid point about portability. Currently, the editor saves tables as HTML to easily support dynamic features like cell styling, backgrounds, and specific alignments without breaking the layout. Detecting when a table is completely plain and dynamically switching between standard Markdown pipe syntax and HTML on save is a solid idea, but it adds code and parser complexity. Because of this, it is not an immediate priority, but I will keep this issue open to track it for the backlog. Regarding the AI question: yes, I use AI assistance extensively. It helps me quickly research optimal approaches, write boilerplate, and speed up development or find bugs. This is why development cycles are faster and commit styles might look a bit different. Thanks again for the feedback and the suggestion.

ngaluru commented 2026年06月18日 10:51:09 +02:00

HTML-tables in MD-files contradict the proclaimed "so i built it: plain Markdown, stored on your own disk."
I think it is a bug. I registered here to create one but found this "Suggestion"...

HTML-tables in MD-files contradict the proclaimed "so i built it: plain Markdown, stored on your own disk." I think it is a bug. I registered here to create one but found this "Suggestion"...

ArkHost commented 2026年06月28日 16:02:56 +02:00

Hello,

This has been addressed in the last version 1.3.3.

Closing this issue.

Hello, This has been addressed in the last version 1.3.3. Closing this issue.