ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Jan Tosovsky" <j.tosovsky@email.cz>
To: "'mailing list for ConTeXt users'" <ntg-context@ntg.nl>
Subject: Re: WYSIWYM editor on top of ConTeXt / Lout
Date: Wed, 6 Dec 2017 22:03:51 +0100	[thread overview]
Message-ID: <009601d36ed5$b9295720$2b7c0560$@email.cz> (raw)
In-Reply-To: <87efo78xcr.fsf@wmi.amu.edu.pl>

On 2017-12-06 Marcin Borkowski wrote:
> On 2017-12-06, at 00:01, Jan Tosovsky <j.tosovsky@email.cz> wrote:
>> On 2017-12-02 Jonas Baggett wrote:
>>>
>>> This is a blog post I recently published:
>>> https://jonas17b.wixsite.com/monsite/home/wysiwym-editor-on-top-of-context-lout
>>> It is about some ideas I have for a WYSIWYM editor like LyX, but it
>>> would be designed for using more than 1 backend (e.g. ConTeXt, Lout),
>>> and to give a much better user experience.
>>
>> Visual editing of complex structures is hard to implement. For XML based
>> publishing there is just single serious tool!
>> https://www.oxygenxml.com/xml_author/docbook_editor_structured_editing.html
> 
> Strange nobody mentioned Org-mode!
> 
> Also, this:
> https://emacs.cafe/emacs/guest-post/2017/06/26/hierarchy.html (works
> with JSON OOTB, but most probably could be used to edit XML).

I meant visual editing (WYSIWYM), see e.g. https://www.youtube.com/watch?v=-3z2sYEaLHM 

Jan



___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2017-12-06 21:03 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
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 [this message]
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='009601d36ed5$b9295720$2b7c0560$@email.cz' \
    --to=j.tosovsky@email.cz \
    --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).