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 opening ecode with a blank document (bypass welcome tab) #279

Open
whatbh opened this issue May 15, 2024 · 3 comments
Open

Allow opening ecode with a blank document (bypass welcome tab) #279

whatbh opened this issue May 15, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request ready for release

Comments

@whatbh
Copy link

whatbh commented May 15, 2024

Currently when opening new ecode window brings users to a "welcome page" and having to press Ctrl+T to open new file. I would love to have an option to allow users to open new ecode window with a blank document readily.

Out of the scope, I anticipate that in the future, a dedicated "Preferences" page or maybe a config file in a markup/serialization format would greatly facilitate these kind of opinionated fine-tuning, instead of leaving them scattering among the menus?

Compliment Lastly, I want to say thank you very much for making this too-good-to-be-true editor available. To me, this one is awesome in many way, it preserve most of the ergonomics from Sublime Text so I never have to leave behind my muscle memory. I also come with a lot of batteries included, like a minimap and, to my surprise, a built-in terminal emulator.
@SpartanJ SpartanJ self-assigned this May 15, 2024
@SpartanJ SpartanJ added the enhancement New feature or request label May 15, 2024
@SpartanJ
Copy link
Owner

Currently when opening new ecode window brings users to a "welcome page" and having to press Ctrl+T to open new file. I would love to have an option to allow users to open new ecode window with a blank document readily.

Sure, I'll add the option, sounds reasonable, also, it used to be like that before the "Welcome Page" existed.

Out of the scope, I anticipate that in the future, a dedicated "Preferences" page or maybe a config file in a markup/serialization format would greatly facilitate these kind of opinionated fine-tuning, instead of leaving them scattering among the menus?

Yes, my idea is to provide a "Settings Panel" in the future, but I'll also probably give direct access to the editor settings file as many other editors do. Menus will keep existing though but I might move some of the options to the settings panel. Also plugins will have a preferences GUI (currently are only managed via a JSON file). Small tip: if you're configuring the editor from the menus you can press "shift" while setting an option and the menu will be kept open. IDK how to communicate that to the users, but it's important since otherwise it's annoying to configure multiple settings at once.

Lastly, I want to say thank you very much for making this too-good-to-be-true editor available. To me, this one is awesome in many way, it preserve most of the ergonomics from Sublime Text so I never have to leave behind my muscle memory. I also come with a lot of batteries included, like a minimap and, to my surprise, a built-in terminal emulator.

Thank you very much for the compliments! I really appreciate it.

@whatbh
Copy link
Author

whatbh commented May 16, 2024

...also, it used to be like that before the "Welcome Page" existed.

Good to know about this one 😛

Small tip: if you're configuring the editor from the menus you can press "shift" while setting an option and the menu will be kept open. IDK how to communicate that to the users, but it's important since otherwise it's annoying to configure multiple settings at once.

Mindblown! TBH knowing this transforms my (and probably others) experience with menus significantly. Keeping menus open like this add great convenience setting up options, maybe even for options that would otherwise buried deep in Setting panel or JSON file.
I am no expert but personally I think I would have know this sooner if there some note like this directly in the menu.

Screenshot 2024-05-16 153242

SpartanJ added a commit to SpartanJ/eepp that referenced this issue Jun 3, 2024
Set the tooltip on tab editor split
When changing folder update/save the last folder
Allow disabling welcome screen (SpartanJ/ecode#279).
@SpartanJ
Copy link
Owner

SpartanJ commented Jun 3, 2024

Added the option to disable the Welcome Screen:
Screenshot_20240602_233653
Screenshot_20240602_233725

(And also the "Hold Shift" suggestion, I'm not convinced but I'll leave it there for the moment).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ready for release
Projects
None yet
Development

No branches or pull requests

2 participants