All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Niteesh G. S." <niteesh.gs@gmail.com>
To: John Snow <jsnow@redhat.com>,
	armbru@redhat.com,  Stefan Hajnoczi <stefanha@redhat.com>,
	kwolf@redhat.com, ehabkost@redhat.com,  wainersm@redhat.com,
	qemu-devel@nongnu.org, vsementsov@virtuozzo.com
Subject: RFC: Implementation of QMP documentation retrieval command
Date: Wed, 16 Jun 2021 21:18:26 +0530	[thread overview]
Message-ID: <CAN6ztm8D4VMf7p-trHNHoOA+1kAXXufTTaHpbyNXZ5qO2_uuPg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]

Hello,

We now have a reasonably working prototype that is capable of
sending/receiving
commands/responses, syntax highlighting, and a simple notification system.
The
prototype can be found here
https://gitlab.com/niteesh.gs/qemu/-/tree/aqmp-tui-prototype
Working on this prototype gives us a lot of hints on things to worry about
and other
ideas that were worth implementing. Our next goal is to start working on
the real TUI
based on this prototype.

One requested feature of the TUI was to show documentation for the commands
typed.
To achieve this, a QMP command that lets us query the documentation from
QEMU has
to be implemented and some discussion has already been done on it in a
previous thread.
I request all continue that discussion here and suggest ideas regarding
implementation.
The goal is to come up with something small and simple which can also be
improved upon
after the summer.

I have a simple implementation of the command that returns dummy
documentation here
https://gitlab.com/niteesh.gs/qemu/-/commit/796a41fb2840b9f3484c6fd5672e6fceb73acaef

Thanks,
Niteesh.

[-- Attachment #2: Type: text/html, Size: 2477 bytes --]

             reply	other threads:[~2021-06-16 15:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-16 15:48 Niteesh G. S. [this message]
2021-06-21 14:58 ` RFC: Implementation of QMP documentation retrieval command Philippe Mathieu-Daudé
2021-06-21 18:26   ` Niteesh G. S.
2021-06-22  9:35     ` Stefan Hajnoczi
2021-06-22 10:26       ` Daniel P. Berrangé
2021-06-22 11:04         ` Vladimir Sementsov-Ogievskiy
2021-06-22 18:57       ` Niteesh G. S.
2021-06-23  8:44         ` Stefan Hajnoczi

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=CAN6ztm8D4VMf7p-trHNHoOA+1kAXXufTTaHpbyNXZ5qO2_uuPg@mail.gmail.com \
    --to=niteesh.gs@gmail.com \
    --cc=armbru@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=vsementsov@virtuozzo.com \
    --cc=wainersm@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.