[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [orion-dev] Need help with creating an extension point
|
My personal opinion and expectation is that we would have one single page that understands all console commands. When I work on the command line locally, I expect that I don't need to need different consoles for each set of commands (eg- git vs vmc commands). From an implementation side, it might be easier to keep the consoles separate, but for a user this is an unnecessary complication.
Besides, even if we went with a separate console per extension, they would still all need to recognize the basic commands (eg- cd, ls, pwd, ...).
So, from a user's point of view, I would prefer to see #1 or #2 below.
On Mon, Mar 5, 2012 at 8:11 AM, John Arthorne
<John_Arthorne@xxxxxxxxxx> wrote:
Stepping back a bit, I'm wondering what
the overall UI experience of the command line will be, and how it will
fit with other pages. Ignoring any security or architectural limitations
for a minute, would it look like:
1) A console "Section" embedded
in other Orion pages, such as the editor or navigator.
2) A single Orion console page (say
http://orionhub.org/console/).
This single page would allow you to interact with all the various console
extensions you have available.. Git, Cloud deployment, Rails console, etc.
3) Individual console pages for various
tasks. For example, http://mygithost.org/console
to interact with a Git repository, http://cloudfoundry.org/console
to interact with a deployed cloud application, etc.
4) Something else?
