Example:
http://fiddle.md/c74bgs3vthgqm8mtt9kx3z
Not perfect, but wouldn't take much to make it play nicely?
61–70 of 71 posts
Example:
http://fiddle.md/c74bgs3vthgqm8mtt9kx3z
Not perfect, but wouldn't take much to make it play nicely?
Shameless plug: I worked on a similar tool mdocs [1]. The main difference is that is opensource, it supports authentication and authorization [2] similar to Google Docs. The authorization part allows you to share documents at company level. It is a 100% client-side application, it uses Firebase as backend and Auth0 for authentication. [1] https://auth0.github.io/mdocs2 [2] https://dl.dropbox.com/s/w6bmji4t698v8qn/ss-…
Shameless plug: I worked on a similar tool mdocs [1]. The main difference is that is opensource, it supports authentication and authorization [2] similar to Google Docs. The authorization part allows you to share documents at company level. It is a 100% client-side application, it uses Firebase as backend and Auth0 for authentication. [1] https://auth0.github.io/mdocs2 [2] https://dl.dropbox.com/s/w6bmji4t698v8qn/ss-…
Interesting, looks like Firebase syncs the who record at a time, how do you avoid conflicts with 2 people editing at the same time?
My first attempt was using a library called ot.js [2], I changed it to support an async db since it only supported a in-memory store and I adapted to use mongodb. The experiment is in [3] and it has some bugs still.
Then I found out the guys at firebase adapted ot.js client side to work with their own db, and created something called Firepad [4]. So, I used that instead which was more stable and I added auth and authn.
[1]: https://en.wikipedia.org/wiki/Operational_transformation
[2]: https://github.com/Operational-Transformation/ot.js/
Shameless plug: I worked on a similar tool mdocs [1]. The main difference is that is opensource, it supports authentication and authorization [2] similar to Google Docs. The authorization part allows you to share documents at company level. It is a 100% client-side application, it uses Firebase as backend and Auth0 for authentication. [1] https://auth0.github.io/mdocs2 [2] https://dl.dropbox.com/s/w6bmji4t698v8qn/ss-…
[3] http://mdocs.io/
As soon as the content is over a page long, the "preview" doesn't really work, since what is supposed to be previewed is out of bounds. I had developed a few years ago a markdown editor with live preview, with a mechanism that synchronized the source and the preview, scroll-wise, so the preview would always display the part that was being edited. It didn't take off (at all) so I let it go, but I wish there would be a…
stackedit.io handles this part of it pretty well. Looking at this, I was wondering why this team didn't just fork that for their intended collaboration use-case (which is neat!).
The beauty of Markdown is that it's simple text; this is distracting and a little unpleasant.
Earlier quoted context omitted.
> Markdown lacks a proper standard http://commonmark.org/ . Of course, you might already know about this, and just be playing the https://xkcd.com/927/ card. On that topic, does anyone know what flavour of markdown is being used here (in fiddle.md)?
We use marked - https://github.com/chjj/marked - with some slight modifications.
Got it working with on-the-fly yUML diagrams. Example: http://fiddle.md/c74bgs3vthgqm8mtt9kx3z Not perfect, but wouldn't take much to make it play nicely?
Earlier quoted context omitted.
I can see how you might feel that way about some of it. But I actually do not really find that to generally be the case. And plenty of it is far nicer than Mdown. However, this is jumping into completely subjective territory; you, of course, do not have to like rst, just as I do not have to like mdown. So, I will stick with my original sentiment of wishing these services would support the thing I like :)
My syntax comment was a bit abstract, apologies about this. I'm referring to RST's strictness and how painful it is to deal with, for example, something as simple as links. I don't really care which way you bold or italicize words, really...
Rst feels like a happy medium between mdown and LaTeX for me, which is actually very much how I use it. I use it in situations where I would have used LaTeX in the past (instances where mdown surely wouldn't cut it). Of course, there are some times (e.g., tables, figures and bibliographies) where LaTeX is the only sensible option, but for anything simpler, I'd still prefer the power that Rst gives me.
Additionally, I actually really like most of how Rst does URLs. It is definitely less simple than mdown, but it's so much more powerful and generalized.
Got it working with on-the-fly yUML diagrams. Example: http://fiddle.md/c74bgs3vthgqm8mtt9kx3z Not perfect, but wouldn't take much to make it play nicely?
Hey, I'm one of the people behind Fiddle.md. I think your example works very well, what do you feel is missing?
I'm using it today for a sales document, it's sweet.
Well, there are some more complex yUML diagrams on the yUML samples page that don't work. It's probably yUML's fault because the syntax isn't quite "proper". But it would be nice if fiddle.md had a way of embedding yUML DSL. E.g.
==== yUML Class Diagram ==== [Company]->[User] [Company]->[Record] [User]-.-[note: A regular user] ==== end ====