Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow Multiple Terminals #26

Open
nahtnam opened this issue Nov 6, 2018 · 10 comments
Open

Allow Multiple Terminals #26

nahtnam opened this issue Nov 6, 2018 · 10 comments
Labels
enhancement New feature or request
Projects

Comments

@nahtnam
Copy link

nahtnam commented Nov 6, 2018

I am trying to create a demo where I start a server and then curl the API. It would be nice if I could open a new terminal session (it would look pretty cool if it shows up as a tab at the top) and switch back and forth while adding responses to each one independently

@rafaelcamargo rafaelcamargo added the enhancement New feature or request label Nov 6, 2018
@rafaelcamargo rafaelcamargo added this to To do in Roadmap Nov 7, 2018
@rafaelcamargo rafaelcamargo moved this from To do to Not Planned in Roadmap Nov 7, 2018
@mostafaebrahimi
Copy link
Contributor

@rafaelcamargo Hi again.
What's your idea to handle tab?

@mostafaebrahimi
Copy link
Contributor

@rafaelcamargo I think you must add a tab component that need to handled by application.
Because of backward compatibility you need to have default write() command() response() but you can
consider that every things happened in a tab.
So by calling write() or command() response() considered that client want to write to default tab and here you can add new function in application that call openTab(name) or openTab(id) that creates new tab and writing was happened in that tab.(you can handle switch tab by openTab(name) like openApplication()

@nahtnam
Copy link
Author

nahtnam commented Nov 13, 2018

I agree with @mostafaebrahimi. I think that API would be most consistent and convenient

@rafaelcamargo
Copy link
Member

@mostafaebrahimi The way is fine. Tab must certainly be a new component to be orchestrated by an application.

Regarding the API, I think tab could be a new option for the method openApp:

gdemo.openApp('editor', { tab: 'tabName' }).end();

If no tab is specified, the default one is used.

However, how would you handle window title in the application? After creating the tab component, I could have more than just one open file in the editor for example. 🤔

What's your thoughts?

@mostafaebrahimi
Copy link
Contributor

@rafaelcamargo I have an opinion about editor but not about terminal yet.We can impact editor like usual editors.if we have tabs so we add tabs row to desktop and we implement every tabs like that we have single editor-application in that tab.
What's your idea?

@mostafaebrahimi
Copy link
Contributor

@rafaelcamargo I think some changes we need here:

  1. create new method openTab that creates new tab(editor-applicaiton) or find application and open it
  2. create new Animation for handle tabs(like animtaion in openApplication that scale - here switch -)

@mostafaebrahimi
Copy link
Contributor

@rafaelcamargo What's your thought?

@rafaelcamargo
Copy link
Member

@mostafaebrahimi So, I am still figuring out how to solve that, but the approach discussed above seems to be really fair. Since this feature is a little complex, I'll focus on getting that done on this weekend and will resume my thoughts on this issue on the next week 👍

@quinton-ashley
Copy link

I am interested in this feature too! It would be great to have tabs in the editor for different files. Has progress been made on this?

@rafaelcamargo
Copy link
Member

Hi @quinton-ashley!

No, this feature is not in development yet. Since I'll be working the next weeks on another glorious project to release it, I'd be very happy If you consider you're be able to offer this contribution ✌️

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Roadmap
  
Not Planned
Development

No branches or pull requests

4 participants