Skip to content
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

Support for other editors/local editting #55

Open
4 tasks
kochrt opened this issue Jun 30, 2022 · 10 comments
Open
4 tasks

Support for other editors/local editting #55

kochrt opened this issue Jun 30, 2022 · 10 comments

Comments

@kochrt
Copy link
Member

kochrt commented Jun 30, 2022

I'm going to try to use this issue to keep track of requests for local development and support in other tools. If one path becomes more apparent or gains more momentum than others I'll break it back out into its own issue.

Right now I'm seeing a few common requests:

  • Obsidian.md
  • VS Code
  • Deploy locally (dockerize markwhen)
  • CLI

In my current position (that is, having a full time job that is not markwhen (yet!)), I have to prioritize my time, and I think that priority should be the website, as it has the most reach and is the easiest for people to get started on.

However, I'm supportive of these other endeavors, though I won't be able to give them as much attention, at least right now.

I was thinking in the meantime the most helpful thing would be a CLI that takes a markwhen document and outputs HTML? That way people can do whatever they want with the html (host it themselves, etc) or potentially use it as the preview view in VS Code/Obsidian?

I want to enable everyone else but I also want to focus on the website for the time being.

@kochrt
Copy link
Member Author

kochrt commented Jul 6, 2022

Parser: https://github.com/mark-when/parser

@zekenie
Copy link

zekenie commented Jul 16, 2022

I was just thinking about what a natural fit this would be for Obsidian!

@kochrt
Copy link
Member Author

kochrt commented Aug 1, 2022

VS code extension - it's quite basic right now (no editing from the timeline, only one page, no filtering) but it is a start

@huyz huyz mentioned this issue Oct 2, 2022
@huyz
Copy link

huyz commented Oct 2, 2022

I'm going to take a stab at an Obsidian plugin and I plan to Support standard Markdown headings and other Obsidian/Markdown syntax

@RoyiAvital
Copy link

That would be great!
Hopefully with traction, even GitHub will embrace it as well.

@kochrt
Copy link
Member Author

kochrt commented Nov 23, 2022

@huyz Check out the vscode branch, it might be helpful? It's just some commits on top of the main branch to make it work with vscode.

@ekristen
Copy link

ekristen commented Feb 2, 2023

I'd love to see Obsidian support. VSCode extension works nice.

@kochrt
Copy link
Member Author

kochrt commented Feb 3, 2023

Tracking obsidian support in #103

@joaosimuai
Copy link

This is amazing, thank you. Is it a big stretch to add support for the different markdown editors e.g. Logseq?

@FeralFlora
Copy link

Is this the place for VS code extension bug reports? I couldn't find anywhere else to put them. The issue I faced was that checking off subtasks in the Event detail view does not get stored in the plain text. As soon as I navigate away from the event view, the checkmark disappears and no change happens on the timeline.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants