Hello friends!

Hello friends!

Those of you who missed GitHub flavoured Markdown support, and code highlighting can log into http://beta.checkvist.com and see how it works.

Another thing to try are changes in multi-line text editing. Now when you edit a multi-line text, Enter starts a new line, and Ctrl (or Meta) Enter submits the text. On one-line list items, Enter works as Submit. 

As usual, we'll be glad to hear about the bugs and glitches. If anything looks or behaves ugly, we'll fix it. The main server update is planned for the end of the week (hopefully).

Thanks!

Comments

  1. Philippe Demoulin19 January 2015 at 12:56

    I start to play with.
    Image, link, lists, code text, these work
    I didin't just find how to create a footnote:
    Foonote[^1]
    [^1]: this is a footnote

    ReplyDelete
  2. Kirill Maximov (KIR)20 January 2015 at 12:48

    Thanks for trying this, Philippe Demoulin !
    We haven't added footnote support. Do you think it is needed? Footnotes are not a part neither of basic Markdown, nor its GitHub variation.

    Still, I'm glad other syntax works for you :)

    ReplyDelete
  3. Philippe Demoulin21 January 2015 at 00:15

    Yes, I agree that footnote is not in the standard flavours of MD.
    Well, I use footnotes very often. The main problem with MD footnotes in an outliner environment is: where are you
    * allow the footnote text to be enter ? Just below the text it refers too (shift+enter) ? At the end ? But the latter means thta you have to parse the whole document to discover the footnotes !
    * render the footnotes ? In the last entry of the document... perhaps a new entry Checkvist has to create/update on-the-fly ? What to do if the user open a new line ? Move the footnotes rendered entries below ?

    Sorry for other readers: I use "line", "entry"... instead of the commonly used "task" and so on... but I use Checkvist as an outliner (http://outliners.scripting.com/) not as a task manager

    ReplyDelete
  4. Kirill Maximov (KIR)22 January 2015 at 04:51

    Hello Philippe,

      Thanks a lot for your thoughts. Initially after your mentioning of footnotes I tried to quickly support them in Checkvist. But I immediately realized that there are questions like the ones you've mentioned - how to render them correctly, where to add them?

      Which led me to the thought of using footnotes with Markdown export (which I'm working on now). If an outline is exported to a valid Markdown document, the question with footnotes can be resolved, for instance you can reference footnotes in your list items, and have a final section in your outline which would contain footnote texts.

      Would you find Markdown export useful, what do you think?

    ReplyDelete
  5. Philippe Demoulin22 January 2015 at 08:25

    Yes.. because Checkvist > export_plain_text > cut&paste Byword/Marked... you have a significant amount of work to obtain a correct rendering.
    Main troubles:
    (1) the "(open)" at the end of each line... yes, I know Checkvist is not a outliner at its foundation LOL
    (2) what about the two trailing spaces for breaking the line ?
    However, I'm still exploring the plain_text way

    ReplyDelete
  6. Kirill Maximov (KIR)22 January 2015 at 08:58

    To avoid (open) at the end of each line, you can un-select checkbox "task status" in the export dialog.
    Regarding two trailing spaces - we can add them during Markdown export - it will be a separate option in the export dialog. 

    Actually, for Markdown export, we thought to provide an option to export top-level list items as Markdown headers, up to specified depth. For instance, you can set that top level items will be exported with prefix # and second level items with prefix ##. The depth (0..6) can be specified in the export options.

    The idea is that one can outline, say, an article or a blog post; add content/text paragraphs, and export the ready Markdown document.

    ReplyDelete

Post a Comment

Popular posts from this blog

Hello friends

Hello friends, Recently we've got a request to introduce a shortcut to move items to the first/last position on the current level of hierarchy: https://checkvist.uservoice.com/forums/2121-general/suggestions/15758854-shortcut-to-send-an-item-at-the-top-of-the-current And this bring me to a thought to use the current shortcut (Ctrl+Home/Ctrl+End) for this purpose. But with an extension - if an item is already on the top position on the current hierarchy level, Ctrl+Home would move item one level up (and put it at the beginning of this level). This will break the current behaviour (moving item to the beginning of the list), but probably will make this shortcut more useful. What do you think? https://checkvist.uservoice.com/forums/2121-general/suggestions/15758854-shortcut-to-send-an-item-at-the-top-of-the-current
Read more

I'm really enjoy using checkvist, you are adding great features very quickly.

I'm really enjoy using checkvist, you are adding great features very quickly.  What I feel is missing is more use cases.  How are people using Checkvist?  What are some recommend workflows?  How many lists do you have? User Stories will not only help those of use already using Checkvist to be more effective, but attract more non-technical customers. I like to keep my lists at a minimum.  I only split out for sharing but I'd prefer not to. Here are my lists: * Inbox:  This is where zapier based integrations go.  I have Jira tickets and emails tagged with "!action" going to list which I process daily. * The List:  This is my primary list.  Everything is here.  I use sub-nodes for different areas. * Honey Do:  This is the list my wife and I share to make sure we know what we both want done around the house. * "Client Project" - I have a few Lists I share with clients (Free lance web developer). I"m looking to write a more detailed blog post. How are your l
Read more