From: Jonas Baggett <jonas17b@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: WYSIWYM editor on top of ConTeXt / Lout
Date: Sun, 3 Dec 2017 08:57:56 +0100 [thread overview]
Message-ID: <a0332755-0987-cc4e-be50-c4a5a0f1bec5@gmail.com> (raw)
In-Reply-To: <CADs1X49C+Mmk_5B72sJ8mS+X7f0COfJj_EmcwBbfMkR4GE3p8w@mail.gmail.com>
> Hi Jonas,
> A desktop editor, not so much. But it'd be wonderful to have a cloud
based
> one with Git integration. I've rolled my own with floobits and my own VM,
> but that doesn't scale and I can't share it with my students.
>
> What you describe has already been worked on by overleaf in terms of a
> realtime option instead of a code option. Maybe extending their work
would
> be a good place to start?
> Cheers,
> -Brian
Hi Brian,
The type of users that I would like to target, will be those writting
rather classical documents of more than 10 - 12 pages and wanting to be
able to focus much more on the content than in the formatting but still
have good looking results. Typically students or professional that are
used to write reports with Word but would be interested to use a more
productive editor, but not ready to move too far away from WYSIWYG.
I didn't made a definitive choice yet, but I believe that being able to
use the editor offline, independantly of the user internet connection,
is almost like a must have. But what sounds interesting, as a nice to
have, would be an editor that can both work in a cloud workflow which
enables features like instant collaborative editing, and a git-like
workflow where user can work offline, then publish online, and if
needed, resolve conflicts.
In regards to the realtime option of overleaf, I guess that after each
change of the document, it runs LaTeX to export the document to PDF. The
template edition mode would do something different as first it won't be
updated realtime: it is only when the user switch to the template
edition mode that the template as well as the contents will rendered on
screen by the editor, without doing any export to PDF.
Cheers,
Jonas
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-12-03 7:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-02 7:42 Jonas Baggett
2017-12-02 8:40 ` Brian Ballsun-Stanton
2017-12-02 10:57 ` Gour
2017-12-03 8:25 ` Jonas Baggett
2017-12-03 7:57 ` Jonas Baggett [this message]
2017-12-02 9:47 ` Siep Kroonenberg
2017-12-02 12:55 ` Henning Hraban Ramm
2017-12-03 7:23 ` Jonas Baggett
2017-12-03 13:21 ` Roger Mason
2017-12-07 6:42 ` Jonas Baggett
2017-12-07 11:19 ` Floris van Manen
2017-12-07 12:26 ` Aditya Mahajan
2017-12-07 12:42 ` Roger Mason
2017-12-07 13:55 ` William Adams
2017-12-07 13:56 ` William Adams
2017-12-03 17:00 ` Aditya Mahajan
2017-12-05 17:42 ` Jonas Baggett
2017-12-05 23:01 ` Jan Tosovsky
2017-12-06 19:33 ` Marcin Borkowski
2017-12-06 21:03 ` Jan Tosovsky
2017-12-07 6:32 ` Marcin Borkowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a0332755-0987-cc4e-be50-c4a5a0f1bec5@gmail.com \
--to=jonas17b@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).