Hi, There has been quite a lot of merge since last time lots of minor tweaks/bugs fixes but also some big changes. Let’s take a look a this! What’s new ? Tweaks/Bugs fixes I’m not going to list and explain each one since there are more or less 20 of them. Tweak wikilink regex The wikilink regex (used for linked note) was not properly done, which meant that sometimes it was grabbing things that it should have. For exemple an bash if statement (if [[ -z $mystring ]]; then) inside a block of ...
    • takeheart@lemmy.world
      1·
      9 months ago

      So I wanted to give Klevernotes a try tonight but:

      1. it doesn’t show up in Discover when searching for any of the terms Klevernotes, Klever Notes, or just klever. On the command line apt search klevernotes returns an empty result set.
      2. the install on Linux link on https://apps.kde.org/klevernotes/ doesn’t work either. It opens Discover but yields the error message Could not open appstream://org.kde.klevernotes because it was not found in any available software repositories. Please report this issue to the packagers of your distribution.
      3. I tried building it myself via the instructions on the GitHub repo but got stuck among the way. Building binaries is a bit beyond my expertise unfortunately.

      I’m on Kubuntu 22.04 with KDE Plasma 5.24.7 in case that matters. Can also file an official bug report as the error message suggests if you advocate for it.

      • louis_sch@lemmy.kde.socialOP
        1·
        9 months ago

        Thanks you for wanting to give it a try, and also to explain the issue clearly without being agressive, that really nice to see.

        Klevernotes is a new project (± 1 year old) and doesn’t have a package right now (working on flatpak). So it’s pretty normal to not find it in Discover nor apt.

        You guessed it right, you need to compile the project to test it.

        I can try to guide you on how to use kde-src build to build klevernotes, but that might be a bit overkill since it will build every dependencies (useful for devs, a bit less for user). Or I can let you know when the flatpak is ready.

  • sonnenzeit@feddit.de
    5·
    9 months ago

    Didn’t even know that this existed. Will have to try. Thumbs up for using mark up which makes it easy to export/import notes.

    • louis_sch@lemmy.kde.socialOP
      3·
      9 months ago

      It’s pretty knew and still in incubator, so it’s not well known.

      I started the project partially to learn markdown, and I quickly found out that this was a really cool format to deal with

      Let me know what you think about it when you try it ;-)

  • Pantherina@feddit.de
    2·
    9 months ago

    Cool app! I use Markdown a lot but think it makes little sense for writing notes. You want the text you write resemble what you mean, its for yourself not some latex project others should read.

    So I prefer Nextclouds editor a lot. Using something similar would be revolutionary, for sure an efficient Qt/Iced app is nice, but its nothing new.

    • David Zaslavsky@techhub.social
      5·
      9 months ago

      @Pantherina @louis_sch Markdown *does* resemble what you mean though. Like, that’s part of the intent of Markdown (and also part of why it became so popular), that the raw markup is readable and lends itself to being understood in the same way as the formatted version. The markup for emphasis actually looks like emphasis; the markup for a list looks like a list; likewise for a section header, or a table or footnote if you’re using a variant that supports those, or so on. So I don’t think that particular argument that Markdown is not good for note-taking holds up very well.

      • Pantherina@feddit.de
        1·
        9 months ago

        Sorry “display what you mean” is of course a “WYGIWYM” triggerword. I mean notes should have bold headers, not hashtags. It is readable but its strange to use. Why not use plain text then? I think the separation between writing and viewing is strange, as this makes little sense for stuff you write and read alone.

        • louis_sch@lemmy.kde.socialOP
          2·
          9 months ago

          I can understand the use case for WYSIWYG and I have thought about it many time, but I have not found a good enough solution to integrate it into the app.

          At the beginning, I made the choice to use the Markdown format for a pretty selfish reason. This was just a private project for me to learn both C++ and markdown. Now that it kind of got out of hand in that regard (I’m pretty happy about it), I really don’t regret Markdown.

          Your note are stored directly on your drive in a markdown file, which mean that, if for whatever reason you want to open it outside of the app, you can, without any issue.

          Now, for the editor/preview. Both can be disable (not at the same time), so you can just focus on the editor, or just focus on the final result. You can also just print your note as a Pdf, I’ve wrote some school project paper like this lol.

          I hope it makes sens, it’s a bit early here, let me know if you want more info :-)

          • Pantherina@feddit.de
            2·
            9 months ago

            Did you try Nextcloud notes? I think it is pretty cool.

            Does it use Pandoc or something else for the PDF conversion? Very cool!

            • louis_sch@lemmy.kde.socialOP
              2·
              9 months ago

              I don’t have next cloud but yes I saw their note app. This kind of wysiwyg is ok imo, and that’s what I would do if I had a solution for this issue (still searching to this day).

              Nop, I grab the pdf directly from the preview which is basicly a Web page

              • Pantherina@feddit.de
                2·
                9 months ago

                I am also not sure how this could work, their approach is very different and likely more messy. Switching between codeview and WYSIWYG view also has some issues, like backspace not switching to the previous line etc.

        • David Zaslavsky@techhub.social
          0·
          9 months ago

          @Pantherina “I mean notes should have bold headers, not hashtags.” OK, but that reflects what *you* want from a notes app, not what everyone wants. And of course that’s totally fine, you can get that from a notes app that has WYSIWYG formatting if you find that it works for you. But I would suggest that it doesn’t make sense for you to enter a discussion about a Markdown notes app and tell a bunch of people, for many of whom that app probably works pretty well, that they’re making a bad choice to use it because it doesn’t offer the behavior you want.

          For what it’s worth, I think a lot of people use Markdown notes apps in a way that you might not be considering. Like, this separation between writing and viewing that you’re talking about simply doesn’t exist in my note-taking workflow. I usually just read the raw markup, possibly with some minimal formatting added on by whatever app I’m using.

          • Pantherina@feddit.de
            1·
            9 months ago

            But I would suggest that it doesn’t make sense for you to enter a discussion about a Markdown notes app and…

            I dont. I just think that writing inline Markdown formatting is really nice and better than clicking buttons, and at the same time I think that Nextcloud Notes has a pretty nice concept.

            So it you view the raw code always, what is the benefit of markdown here? I dont see how

            ### Header

            Is better than

            --- Header ---

            Which is what I normally use as header formatting in scripts etc.

            • Iαη@mastodon.cloud
              1·
              9 months ago

              @Pantherina @diazona @louis_sch
              Having an option to choose should keep twice as many people happy. The markdown apps I use, don’t show any formatting marks, and have style icons. Lots of us outside the IT world are used to this wysiwyg way.

    • louis_sch@lemmy.kde.socialOP
      2·
      9 months ago

      I have no problem with supporting Windows. However this means that I should build it and try it on Windows, which is not my top priority when it comes to OS support right now.

      Flatpak is currently giving me enough problem tbh :/