All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Niteesh G. S." <niteesh.gs@gmail.com>
To: qemu-devel@nongnu.org
Cc: kwolf@redhat.com, ehabkost@redhat.com, armbru@redhat.com,
	wainersm@redhat.com, stefanha@redhat.com,
	John Snow <jsnow@redhat.com>
Subject: Fwd: GSoC Intro - TUI interface for QMP
Date: Sat, 22 May 2021 00:32:00 +0530	[thread overview]
Message-ID: <CAN6ztm9JKPo05_qJo1cFGq2P6f1DzB9vu+VZ054e9MdHVkRLog@mail.gmail.com> (raw)
In-Reply-To: <CAN6ztm-J2GoQKkLb=Az0H2Q8UKK4oE3PgXg7g14=T53sQAUyDg@mail.gmail.com>

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

Hello all,

I am Niteesh, one of the students selected under Google Summer of Code 2021
to work on the project* Interactive, asynchronous QMP TUI.*
Link to my proposal:
https://docs.google.com/document/d/1o_U9txCyqZDYIqqhj4V0IEO9-20KY2pb4egi75ueXco/edit?usp=sharing

The goal of this project is to get an interactive and asynchronous TUI
interface
that is capable of connecting to the AQMP server and communicate with it.

My experience with async stuff and AQMP is writing a chat application to
better understand python's asyncio and trying to connect the UI to AQMP.
The UI built for chatting basically worked as a primitive interface to send
and
receive QMP commands. The below video demonstrates this.
https://github.com/gs-niteesh/Async-Chat-App/blob/master/qemu.mp4

By end of this summer, I would like to get a basic TUI with some desirable
features working. Some of the features I would like to get working are
1) Syntax checking
2) Syntax highlighting
3) Code completion
4) Logging

I would like to hear some of the features you would like to have and also
your
advice's on implementation.

PS: If you are seeing the mail twice, sorry, I forgot to include the
mailing list
in the first time.


Thanks,
Niteesh

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

       reply	other threads:[~2021-05-21 19:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAN6ztm-J2GoQKkLb=Az0H2Q8UKK4oE3PgXg7g14=T53sQAUyDg@mail.gmail.com>
2021-05-21 19:02 ` Niteesh G. S. [this message]
2021-05-24 13:32   ` Fwd: GSoC Intro - TUI interface for QMP Stefan Hajnoczi
2021-05-24 17:34     ` John Snow
2021-06-02 11:08       ` Bruno Piazera Larsen
2021-06-11 14:06       ` Vladimir Sementsov-Ogievskiy via
2021-05-26 15:35     ` Fwd: " Niteesh G. S.
2021-06-01 23:47       ` John Snow
2021-06-08 15:01         ` Markus Armbruster
2021-06-08 15:49           ` John Snow
2021-06-09 11:56             ` Markus Armbruster
2021-06-09 17:06               ` John Snow
2021-06-10  7:19                 ` Markus Armbruster
2021-06-09 12:07             ` Daniel P. Berrangé
2021-06-10 14:35               ` John Snow
2021-06-09 12:03           ` Daniel P. Berrangé

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=CAN6ztm9JKPo05_qJo1cFGq2P6f1DzB9vu+VZ054e9MdHVkRLog@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=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.