-
Notifications
You must be signed in to change notification settings - Fork 443
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
Comments
I'd like to see split panes on the actual roadmap. Do we have a feature
request for broadcast input? I think that should come along with split
panes, ideally.
--
Hans Kokx
…On October 8, 2018 3:43:21 PM Felix ***@***.***> wrote:
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.1.0
Finished:
Additional Keybindings to switch to certain tabs (#70)
Improved scrolling in settings (#66)
Tab theme colors (#73)
Fixed a crash when pasting something that was not text (#86)
Allow editing built-in profiles (#57)
In Progress:
Keybindings to create new terminals with specific profiles (#85)
Default color scheme for profile (#28)
Open:
Activity indicators on tabs (#60)
Improve displaying of long titles in tabs (#79)
Improve CLI interface of flute.exe to improve interoperability (#87)
Improved installation (#92)
Update to latest xterm.js
0.2.2.0
Add support for ConPTY (requires 1809)
Admin rights for powershell/CMD (Might be tied to 1809)
0.2.3.0
Refactor multi window to be based on multiple instances (this will raise
minium target version to 1803)
Jumplist support (#88)
Unscheduled:
Support new search APIs of xterm.js
Localization
Split panes
Always on top windows
Built-In SSH support
Switch to Azure DevOps CI
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
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. |
👍
--
Hans Kokx
…On October 8, 2018 4:08:54 PM Felix ***@***.***> wrote:
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.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Stupid question:
What purpose does that solve? |
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 |
#81 and #62, but in general multi window is a bit buggy as it is implemented right now.
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. |
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: PS: OneNote is another good example for "Switch back to previous desktop for no apparent reason, then spawn a new window" |
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. |
Hi, I think it would be great, if you could prioritize the following tasks. 1- Documentation.
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 + 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 |
@ericcornelissen actually, my second concern is better addressed at #88. I've just realized in #88 that 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 👍. |
Ah okay, I misunderstood 😅
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 🤔 |
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:
The text was updated successfully, but these errors were encountered: