Re: [tm-dev] Terminal (was Re: Master branch is TM 3.7?)

["Stieber, Uwe" <Uwe.Stieber@xxxxxxxxxxxxx>]

Hi,

> True. I wonder what the typical usage is. How many Terminals do users have
> open anyway?

There are many different use cases out there, and connecting to a remote host via SSH or Telnet is just one of it. If you are connecting to a  partitioned system, probably with multiplexed consoles, you can have easily a lot of consoles/terminals. People wants to know which consoles are connected and active. Doing this in a stacked view, like the Eclipse Console view or the deprecated Terminal view, is a pain. Having each console opening in a separate view is not a solution either. People wants to control how many views they have and which consoles they want to see side by side. 

I agree that we might approach the Terminal view from different ends and that there are different needs and preferences. Nobody ever said that the tabbed Terminals view is solving all issues, and the stacked approach isn't the perfect approach either. At the end, what's might be needed is a Terminals view that is capable of operating tabbed or stacked, and the user can configure each view instance individually, or globally via the Eclipse preferences.

>Having the Local terminal always open would be good too.

We do this in our product, so it can be achieved easily, but, this might be something each product builder sees different, so it should be the product builder's decision if or if not a Local terminal is always open or not.

Just my 2 cents.

Best regards, Uwe 

> -----Original Message-----
> From: tm-dev-bounces@xxxxxxxxxxx [mailto:tm-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Doug Schaefer
> Sent: Montag, 02. Februar 2015 18:14
> To: TM project developer discussions
> Subject: Re: [tm-dev] Terminal (was Re: Master branch is TM 3.7?)
> 
> On 2015-02-02, 3:02 AM, "Rob Stryker" <rstryker@xxxxxxxxxx> wrote:
> 
> >On 01/08/2015 04:42 AM, Doug Schaefer wrote:
> >>
> >> Now, if the tabs act like Views, that makes me wonder why we wouldn¹t
> >> want a View per terminal. In the past, we¹ve implemented an Open
> >> Terminal menu item on a Target/Remote Connection that always opened a
> >> new view (which is why I tricked myself into thinking this was the
> >> default behaviour). Seems like that would be even simpler.
> >
> >I believe I read another comment (either on list or in a jira, I
> >forget) indicating they preferred tabs because having multiple views
> >open for terminals to multiple systems will clog the workbench. I don't
> >have a strong preference over 'tabs' vs  a dropdown to select the
> >active terminal (similar to console), but I do agree that having each
> >connection in its own view will lead to a very cluttered feel.
> 
> True. I wonder what the typical usage is. How many Terminals do users have
> open anyway? I work with one remote machine at a time typically. Having the
> Local terminal always open would be good too. Potentially it could get messy,
> yes.
> 
> >
> >I suppose maximum flexibility would be to allow behavior similar to
> >console view, where there's a dropdown to select a console but you also
> >have the ability to open a second view if you wish.
> 
> :). That¹s what the old terminal did. I actually like that as it¹s one design language
> the user needs to learn to do Terminal and Console. I just worry that it¹s not very
> discoverable like tabs are.
> 
> Interesting thought experiment - What¹s the difference between a Console and a
> Terminal? I don¹t think it¹s that much.
> 
> Doug.
> 
> _______________________________________________
> tm-dev mailing list
> tm-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit https://dev.eclipse.org/mailman/listinfo/tm-dev