public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Benjamin Doron" <benjamin.doron00@gmail.com>
To: devel@edk2.groups.io
Cc: marcello.bauer@9elements.com
Subject: [edk2-devel] Refactoring the UEFI shell
Date: Tue, 19 Mar 2024 13:43:50 -0400	[thread overview]
Message-ID: <CAONYkK8Du-LLdj7PBVz8yxUAkUedr=kypv_tvSBHD3z73PoQWw@mail.gmail.com> (raw)

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

Hi all,
We're planning to refactor the shell into a library so that shell apps
possibly used in the field for testing can be easily adapted for automation.

Our plan is:

   - Refactor ShellInfoObject into base internals and interactive elements
   - Migrate functions that imply interactivity into a new library class,
   and write some stubs in a LibNull
   - Refactor last shell app files (file interface, shell env var) into
   another (or same) library
   - Implement non-interactive functions, as required
   - Write an example implementation in MdeModulePkg/Application/


We're looking for thoughts and ideas on our approach, as well as opinions
on the concept.

Best regards,
Benjamin


-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116903): https://edk2.groups.io/g/devel/message/116903
Mute This Topic: https://groups.io/mt/105028827/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



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

             reply	other threads:[~2024-03-19 17:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-19 17:43 Benjamin Doron [this message]
2024-03-27 10:27 ` [edk2-devel] Refactoring the UEFI shell Sheng Lean Tan
2024-04-03  7:58   ` Yoshinoya

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-list 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='CAONYkK8Du-LLdj7PBVz8yxUAkUedr=kypv_tvSBHD3z73PoQWw@mail.gmail.com' \
    --to=devel@edk2.groups.io \
    /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