It would be nice if KJots had the option to use markdown instead of plain text. The addition of markdown and/or basic formatting capabilities (which KNotes already has) is probably the only thing missing from KJots to make it an extremely handy diary/notekeeping/knowledge bank program.
The addition of Markdown editing would require the implementation of either of the two:
a WYSIWYM markdown editor or
a more simple implementation with two modes (markdown view and source view) which would toggle between an source editor part with markdown highlighting and a read-only markdown preview part (we already have that)
Any other idea is of course welcome.
It would be nice if KJots had the option to use markdown instead of plain text. The addition of markdown and/or basic formatting capabilities (which KNotes already has) is probably the only thing missing from KJots to make it an extremely handy diary/notekeeping/knowledge bank program.
The addition of Markdown editing would require the implementation of either of the two:
- a WYSIWYM markdown editor or
- a more simple implementation with two modes (markdown view and source view) which would toggle between an source editor part with markdown highlighting and a read-only markdown preview part (we already have that)
Any other idea is of course welcome.
I discovered KJots only recently thanks to the work of @mio, but I immediately started using it. Having support for markdown or some other formatting would be a great addition. WYSIWYG would be good, but source/view panels could be an alternative if WYSIWYG is too complex to implement.
I discovered KJots only recently thanks to the work of @mio, but I immediately started using it. Having support for markdown or some other formatting would be a great addition. WYSIWYG would be good, but source/view panels could be an alternative if WYSIWYG is too complex to implement.
Hm, I've just discovered KnowIt and it just does everything I need from a note-taking app, better so than KJots. And yes, it already has basic formatting.
@MicheleC and @mio you might want to check it out ;)
P.S. And I also remember we have BasKet which is even more feature-rich.
Hm, I've just discovered [KnowIt](https://mirror.git.trinitydesktop.org/gitea/TDE/knowit) and it just does everything I need from a note-taking app, better so than KJots. And yes, it already has basic formatting.
@MicheleC and @mio you might want to check it out ;)
P.S. And I also remember we have BasKet which is even more feature-rich.
@blu.256 Thanks Philippe, I didn't know it either and I agree it has more functionality than kjots. I have not looked at the code of the two apps, but the GUI has a lot of similarities, I wouldn't be surprise the code base is also similar in parts.
@mio: looks like the same improvements you made for KJots Find dialog could be applied to Knowit as well. There the Find dialog is still the simple one. What do you think?
@blu.256 Thanks Philippe, I didn't know it either and I agree it has more functionality than kjots. I have not looked at the code of the two apps, but the GUI has a lot of similarities, I wouldn't be surprise the code base is also similar in parts.
@mio: looks like the same improvements you made for KJots Find dialog could be applied to Knowit as well. There the Find dialog is still the simple one. What do you think?
This is actually something that I want to implement for R14.1.4. I had though of using TDEMarkdown initially, but then discovered it's read-only. Which why I'm now replacing KEdit with KTextEdit (#88) so that rich text can be enabled afterwards :-)
As far as Markdown support goes, my preference would be for adding a WYSIWYG markdown editor that supports both Ctrl-based and markdown-based formatting (i.e. Ctrl+B and ** start/end bold text). Although, this should probably exist separate from an individual program and be something people can reuse for their program.
looks like the same improvements you made for KJots Find dialog could be applied to Knowit as well. There the Find dialog is still the simple one. What do you think?
It shouldn't be too difficult, the code does seem similar. I can take a better look after it's been added to KJots. Alternatively, would it be worth adding the functionality to KTextEdit directly instead? That way all programs using KTextEdit support a common find/replace.
This is actually something that I want to implement for [R14.1.4][0]. I had though of using TDEMarkdown initially, but then discovered it's read-only. Which why I'm now replacing KEdit with KTextEdit (#88) so that rich text can be enabled afterwards :-)
As far as Markdown support goes, my preference would be for adding a WYSIWYG markdown editor that supports both Ctrl-based and markdown-based formatting (i.e. `Ctrl+B` and `**` start/end bold text). Although, this should probably exist separate from an individual program and be something people can reuse for their program.
> looks like the same improvements you made for KJots Find dialog could be applied to Knowit as well. There the Find dialog is still the simple one. What do you think?
It shouldn't be too difficult, the code does seem similar. I can take a better look after it's been added to KJots. Alternatively, would it be worth adding the functionality to KTextEdit directly instead? That way all programs using KTextEdit support a common find/replace.
[0]: https://mirror.git.trinitydesktop.org/gitea/TDE/tde/wiki/General-roadmap-for-R14.1.4
Although, this should probably exist separate from an individual program and be something people can reuse for their program.
Yes, that would be nice to do.
Alternatively, would it be worth adding the functionality to KTextEdit directly instead?
Uhm, although it is tempting, I think the find dialog GUI is something on top of the text editor widget/component. So I am not so sure that would be the right call. @blu.256 what is your opinion on this?
> Although, this should probably exist separate from an individual program and be something people can reuse for their program.
Yes, that would be nice to do.
> Alternatively, would it be worth adding the functionality to KTextEdit directly instead?
Uhm, although it is tempting, I think the find dialog GUI is something on top of the text editor widget/component. So I am not so sure that would be the right call. @blu.256 what is your opinion on this?
It would be nice if KJots had the option to use markdown instead of plain text. The addition of markdown and/or basic formatting capabilities (which KNotes already has) is probably the only thing missing from KJots to make it an extremely handy diary/notekeeping/knowledge bank program.
The addition of Markdown editing would require the implementation of either of the two:
Any other idea is of course welcome.
I discovered KJots only recently thanks to the work of @mio, but I immediately started using it. Having support for markdown or some other formatting would be a great addition. WYSIWYG would be good, but source/view panels could be an alternative if WYSIWYG is too complex to implement.
Hm, I've just discovered KnowIt and it just does everything I need from a note-taking app, better so than KJots. And yes, it already has basic formatting.
@MicheleC and @mio you might want to check it out ;)
P.S. And I also remember we have BasKet which is even more feature-rich.
@blu.256 Thanks Philippe, I didn't know it either and I agree it has more functionality than kjots. I have not looked at the code of the two apps, but the GUI has a lot of similarities, I wouldn't be surprise the code base is also similar in parts.
@mio: looks like the same improvements you made for KJots Find dialog could be applied to Knowit as well. There the Find dialog is still the simple one. What do you think?
This is actually something that I want to implement for R14.1.4. I had though of using TDEMarkdown initially, but then discovered it's read-only. Which why I'm now replacing KEdit with KTextEdit (#88) so that rich text can be enabled afterwards :-)
As far as Markdown support goes, my preference would be for adding a WYSIWYG markdown editor that supports both Ctrl-based and markdown-based formatting (i.e.
Ctrl+B
and**
start/end bold text). Although, this should probably exist separate from an individual program and be something people can reuse for their program.It shouldn't be too difficult, the code does seem similar. I can take a better look after it's been added to KJots. Alternatively, would it be worth adding the functionality to KTextEdit directly instead? That way all programs using KTextEdit support a common find/replace.
Yes, that would be nice to do.
Uhm, although it is tempting, I think the find dialog GUI is something on top of the text editor widget/component. So I am not so sure that would be the right call. @blu.256 what is your opinion on this?