_mql

8 ms·

31.
Reproducible science for people who don't code – an idea(medium.com)
2 points by _mql 10y ago|0 comments
32.
by _mql 10y ago
Thank you very much for your comments! A few notes from the authors: Texture's first goal is its use at publishers, during their review and QC processes. Word or InDesign submissions are converted to JATS using the converter from Open
33.
Texture – As open as LaTeX and as simple as a classic word processor(substance.io)
112 points by _mql 10y ago|39 comments
34.
by _mql 11y ago
For the scientific editor mobile is not a priority atm. However we work on better mobile support for Substance in general. Beta 5 is dedicated to that among other things.
35.
by _mql 11y ago
You are right. I may have broken that with the last update. Will be fixed soon. Generally, LensWriter is still in experimental state but we are working with publishers to integrate into their workflows. During April there will be a push on
36.
by _mql 11y ago
Just published an example that shows realtime collab capabilities: http://substance.io/examples/collabwriter/
37.
by _mql 11y ago
I think the approaches of Substance and ProseMirror are quite similar. We map DOM coordinates to model coordinates and the other way around. That way we can use the native DOM for cursor navigation (not trivial to implement), but all input
38.
by _mql 11y ago
Hi Mickael! Each content type consists of the following pieces: - Node (model) [1] - Component (visual representation) [2] - Converter (optional, used to map from and to XML/HTML) [3] The verbose output for heading1 you see is just the
39.
by _mql 11y ago
Thank you for sharing this on HN. Just wanted to add our introduction blog post, which may clarify some of the questions asked here. https://medium.com/@_mql/build-your-own-editor-with-substanc... And some usage exampl
40.
by _mql 11y ago
Hi! To clarify: Substance is compatible with Browserify and Webpack. It runs in Node and in the browser. It doesn't come as one big module, instead it lets you deep require individual files so your bundle only includes what you explici
41.
by _mql 12y ago
Hi! I'm the developer behind the original version of Prose: http://developmentseed.org/blog/2012/june/25/prose-a-content... I'm no longer involved in the development. However, I do understand y
42.
DIY Publishing with Substance and Github Pages(substance.io)
1 points by _mql 13y ago|0 comments
43.
How to build a web-based editor that actually works?(docs.google.com)
2 points by _mql 13y ago|0 comments
44.
Substance.Chronicle implements versioning for JS strings, arrays, objects.(interior.substance.io)
2 points by _mql 13y ago|0 comments
45.
ELife Lens is a novel way of seeing content(lens.elifesciences.org)
1 points by _mql 13y ago|0 comments
46.
Substance Surface brings reliable text manipulation to the web(interior.substance.io)
1 points by _mql 14y ago|0 comments
47.
Substance.io needs your help(pledgie.com)
2 points by _mql 14y ago|0 comments
48.
Substance Document is an open standard for digital documents(interior.substance.io)
36 points by _mql 14y ago|3 comments
49.
by _mql 14y ago
Haha, no. ;) We started with a test suite, but once Prose launched we had a lot of users reading and writing files to GitHub using GitHub.js (almost 5000 GitHub users have logged in at least once). So it was implicitly tested by the crowd.
50.
by _mql 14y ago
SEO is totally up to the website developer. The version Google sees is a generated static version of your Jekyll-site specification (layouts, posts, configuration etc.). So SEO is not in the scope of the project.
51.
by _mql 14y ago
https://github.com/prose/prose/issues/140
52.
by _mql 14y ago
I agree on over-engineered semantic formats. HTML used to be a document representation format. But for me it has turned into a presentation format, with all the DOM manipulation etc. This is perfectly fine, I just had to realize it. Now i j
53.
by _mql 14y ago
It's meant to be very strict about semantics (LaTeX actually isn't - it has a lot of style-related commands), and it will be extensible (so you can add your own content types). It's based based on a JSON document model that is describing a
54.
by _mql 14y ago
Using this thread to extend the discussion about digital content authoring... Prose relies on Markdown, the current de-facto standard for content authoring on the web. But what comes after? If you ask me the answer is clearly: Semantic Rich
55.
by _mql 14y ago
Hehe. ;) No worries, feel free to pick some styles, if helpful.
56.
by _mql 14y ago
There's only support for Markdown right now, but you should be able to edit any textfile in a repository. There might be some remaining flaws though, so please submit issues and help us fix them.
57.
by _mql 14y ago
Planned feature: https://github.com/prose/prose/issues/120 For now, please enter the URL manually to access repos that live within organisations. http://prose.io#:org/:repo/:branch In future we'll also allow browsing user and organisati
58.
by _mql 14y ago
We'll do some optimizations for iPad if we get time. However, this would be a great piece for getting involved. One blocker I see is that CodeMirror does not work well with iPad touch events yet.
59.
by _mql 14y ago
Can you create an issue on Github and describe the problem step-by-step? There might be some edge cases we haven't covered yet. http://github.com/prose/prose
60.
by _mql 14y ago
Glad you like the UI. See Gatekeeper, regarding authentication. https://github.com/prose/gatekeeper

More ›