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

[Looking for Feedback] Roadmap #93

Closed
felixse opened this issue Oct 8, 2018 · 12 comments
Closed

[Looking for Feedback] Roadmap #93

felixse opened this issue Oct 8, 2018 · 12 comments

Comments

@felixse
Copy link
Owner

felixse commented Oct 8, 2018

Hey All,

I just wanted to share my plan for the near future of Fluent Terminal. As you might have noticed I'm currently busy with another project, but I should be able to commit my full attention to this one very soon again. Please note that nothing here is set in stone, so if you have something you want to have addressed earlier or have some further ideas please share your thoughts 😄

0.2.2.0

0.2.3.0

Unscheduled:

@hanskokx
Copy link
Contributor

hanskokx commented Oct 8, 2018 via email

@felixse
Copy link
Owner Author

felixse commented Oct 8, 2018

You're right, also added some missing references to the unscheduled items. I think 0.2.3.0 would be a good release for split panes & broadcast, since this one will concentrate on window management.

@hanskokx
Copy link
Contributor

hanskokx commented Oct 8, 2018 via email

@JensMertelmeyer
Copy link

JensMertelmeyer commented Oct 9, 2018

Stupid question:

Refactor multi window to be based on multiple instances

What purpose does that solve?

@bhramchari
Copy link

this discussion might be of interest as there were some comments about getting the app into the store and uwp/runfulltrust/conpty etc, maybe useful for putting it on the roadmap

microsoft/terminal#274 (comment)

@felixse
Copy link
Owner Author

felixse commented Oct 9, 2018

Stupid question:

Refactor multi window to be based on multiple instances

What purpose does that solve?

#81 and #62, but in general multi window is a bit buggy as it is implemented right now.

this discussion might be of interest as there were some comments about getting the app into the store and uwp/runfulltrust/conpty etc, maybe useful for putting it on the roadmap

Microsoft/console#274 (comment)

Thanks for the link, seems like we're lucky that no one had any issues with message ordering so far. But in general this doesn't read like they would be against our current approach.

@JensMertelmeyer
Copy link

JensMertelmeyer commented Oct 9, 2018

Thank you for replying. Can we be sure multi-instances fix #81?

Take note: The following article from Microsoft states that calculator uses "multi-view" instead of "multi-instances" and yet calculator is an app that has the desired behaviour:
https://blogs.windows.com/buildingapps/2018/02/23/windows-community-standup-discussing-multi-instancing-console-uwps-broader-file-system-access/

PS: OneNote is another good example for "Switch back to previous desktop for no apparent reason, then spawn a new window"

@felixse
Copy link
Owner Author

felixse commented Oct 10, 2018

Good point. Just checked this myself, Calculator is multi-view. I would still prefer to implement multi-instance, mainly for stability. But maybe we can fix #81 independent of this.

@hrzafer
Copy link

hrzafer commented Mar 16, 2019

Hi,

I think it would be great, if you could prioritize the following tasks.

1- Documentation.

  • There is need for a little bit more information on why Fluent-Terminal is more preferable over others. Personally, I loved the looks and simplicity. Besides the looks, it is very easy and intuitive to configure Fluent-Terminal.
  • Better installation documentation. Currently there are 3 ways presented. The first two are problematic, only the last one works smoothly.
  • Does the current release makes use of ConPTY? Above ConPTY support is written under 0.2.2.0 roadmap.
  • Simpler versioning. Maybe only major.minor.patch ?

2- Better selection of terminal type. Currently, the only way of starting a terminal other than the default profile is keyboard shortcuts. There is no GUI control for that. It is very easy to forget which ctrl + alt + number point to which profile. I tried using letters, ctrl + alt + c => cmd, ctrl + alt + b => bash, etc. But then I installed conda which brings its own cmd and letter c was already occupied.

ctrl + shitf + p => type command would be a solution. (VS Code style)

3- Split pane would be good but similar functionality can be achieved by setting Open new terminals as to Windows and using windows + arrow keys.

@ericcornelissen
Copy link
Contributor

Just for you information regarding your second point @hrzafer, the GUI will soon have a button to open a new tab (see #196) for now I recommend you enable the "Always use tabs" option (under Settings -> General), this adds a GUI element to open a new tab even if you have only a single tab open 😉

@hrzafer
Copy link

hrzafer commented Mar 17, 2019

@ericcornelissen actually, my second concern is better addressed at #88. I've just realized in #88 that ctrl + shift + T is a little bit closer to what I want. I wonder if this is documented anywhere.

Let me know how I can help with the improvement of the documentation of the project.

Again, I love the looks and simplicity of FT 👍.

@ericcornelissen
Copy link
Contributor

ericcornelissen commented Mar 17, 2019

actually, my second concern is better addressed at #88. I've just realized in #88 that ctrl + shift + T is a little bit closer to what I want. I wonder if this is documented anywhere.

Ah okay, I misunderstood 😅

Let me know how I can help with the improvement of the documentation of the project.

I don't believe there is currently any documentation on the available keyboard shortcuts. Although personally I feel like they all have descriptive names and you can just go through them in the settings, you can write something up I guess (perhaps in the Wiki? I believe you can make a new page). Only problem I foresee is that things might change in the future without the docs being updated...

Also, related to both of your points, @felixse aims to add the relevant keyboard shortcuts to the menu in #196 so perhaps that is all we need 🤔

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants