Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Thino取消对<br>的依赖之后,感觉很不好,建议恢复原来的样子 #516

Closed
1 task done
whong1618 opened this issue Apr 7, 2024 · 3 comments
Labels
discuss/vote Discuss the rationale for fr and bugs and the details of their implementation

Comments

@whong1618
Copy link

whong1618 commented Apr 7, 2024

Feature Requested | 请求的功能

闪念笔记类型的Thino作为Obsidian的插件,其优势就是和Obsidian的兼容性和格式设计上基本的一致性。

在Thino没有取消对<br>的依赖之前,使用感觉很好:
在Thino编辑器编辑的内容,所见即所得,
编辑器中的格式和最后卡片的格式以及在每日Thino里浏览的格式基本保持一致

而且每日笔记最后生成的笔记md文件里,也基本上和卡片保持一致的格式,
不管是笔记md文件的编辑模式,还是阅读模式,都基本一致,与Obsidian其他md笔记编辑体验具有很好的一致性。

然而Thino新版本,取消了对<br>的依赖,用什么缩进来自动换行。
在Markdown里格式里,缩进是由特殊用途的。

使用Obsidian的Thino做笔记,对我一个大的吸引力就是可以使用Markdown的格式语法来写笔记,所见即所得。而<br>作为换行,其实很通用,有时候也很好用。

现在的新版本,取消了对<br>的依赖,在Thino编辑器里,现在两行之间不换你在编辑器中换多少行,最后呈现在Thino卡片里的,都是不认的,间隔2行、3行、4行的原文本,最后呈现的都是一样的间隔。

灵活性失去了,用户编辑器中的所写和最后的呈现出现了格式上的不一致。
笔记md文档,也因为换行<br>的失去,而在阅读模式里,更是塌缩到了一块。想要体现多个空行,得手动添加<br>,其实这并不利于用户使用体验。

感觉没有取消对<br>的依赖之前的设计,使用体验更好,能更好地 与Obsidian格式兼容,同时更好的体现了编辑窗口中的所见即所得。

希望开发者能好好考虑一下,以真正使用者的实际体验以及Thino赖以与对手区别的优势考虑,最好能恢复之前的设计。

Relevant Screenshot | 相关截图

No response

Checklist | 检查清单

  • The feature would be useful to more users than just me. 该功能对于不仅仅是我自己的用户来说是有用的。
@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically...


Title: Feature Request: After Thino canceled its dependence on
, I felt very bad. It is recommended to restore it to its original appearance.

Feature Requested | Requested feature

As a plug-in for Obsidian, the advantage of Thino, a flashnote type, is its compatibility with Obsidian and its basic consistency in format design.

Before Thino removed its dependence on
, it felt good to use:
What you see is what you get when editing content in the Thino editor.
The format in the editor is basically the same as the format of the final card and the format browsed in daily Thino.

Moreover, the note md file generated at the end of the daily notes basically maintains the same format as the card.
Whether it is the editing mode or reading mode of note md files, they are basically the same, and have good consistency with other md note editing experiences in Obsidian.

However, the new version of Thino has eliminated the dependence on
. What indentation should be used to automatically wrap lines?
In Markdown formatting, indentation is used for special purposes.

One of the big attractions for me when using Obsidian's Thino to take notes is that you can use Markdown's formatting syntax to write notes, and what you see is what you get. As a line break,
is actually very versatile and sometimes useful.

The new version now eliminates the dependence on
. In the Thino editor, there is no switching between two lines. You change as many lines as you want in the editor. The last ones displayed in the Thino card will not be recognized. The original text separated by 2 lines, 3 lines, and 4 lines is finally presented with the same interval.

Flexibility is lost, and there are formatting inconsistencies between what is written in the user editor and what is finally rendered.
The note md document also collapsed into one piece in the reading mode due to the loss of line breaks
.

It feels like the previous design did not eliminate the dependence on
, the user experience is better, it is better compatible with the Obsidian format, and it better reflects the WYSIWYG in the editing window.

I hope the developers can think about it carefully and restore the previous design based on the actual experience of real users and the advantages that distinguish Thino from its opponents.

Relevant Screenshot |

No response

Checklist | Checklist

  • The feature would be useful to more users than just me.

@Quorafind
Copy link
Owner

之前的设计会导致所有任务相关内容,其它插件无法识别。所有代码块、引用、callout 等,外部插件都无法识别。

@Issues-translate-bot
Copy link

Bot detected the issue body's language is not English, translate it automatically...


The previous design would cause all task-related content to be unrecognized by other plug-ins. All code blocks, references, callouts, etc. are not recognized by external plugins.

Repository owner locked and limited conversation to collaborators Apr 8, 2024
@Quorafind Quorafind converted this issue into discussion #517 Apr 8, 2024
@juestchaos juestchaos added the discuss/vote Discuss the rationale for fr and bugs and the details of their implementation label Apr 8, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
discuss/vote Discuss the rationale for fr and bugs and the details of their implementation
Projects
None yet
Development

No branches or pull requests

4 participants