[Feature]: [important] reset or default size of the window!

[alexsupa597]

Feature description

Currently, the application appears to lack a fundamental window sizing configuration. Upon launch, the terminal interface defaults to occupying nearly the entire screen real estate. While this might align with specific use cases, it creates suboptimal initial user experience - particularly for supporters who appreciate the application's core functionality but find the overwhelming window dimensions disruptive to their workflow.

A suggested enhancement would be implementing:

1. Default window size presets
2. Remember-last-size functionality
3. Screen-adaptive scaling (e.g., 70% of display area by default)

This quality-of-life improvement could significantly enhance first-time user experience while maintaining flexibility for power users.

Implementation Suggestion

No response

Anything else?

No response

[esimkowitz]

We already support changing the default window size: https://docs.waveterm.dev/config

Additionally, your last window is always preserved so its size should be remembered. I'm not sure I agree that new windows should spawn with the last window size, though, that seems to go against the behavior of most other apps and I think would be more jarring.

As for adaptive window scaling, that's an interesting idea, could be a good first issue. Can you open this as a separate feature request? I'm not a huge fan of issues with multiple asks, makes it harder to track.

[alexsupa597]

Thank you for the response. Perhaps I didn't explain clearly enough.

1. When users use our app, they generally aren't accustomed to operating software features through configuration files like "settings.json"; users aren't particularly concerned about the underlying code logic.
   People prefer having operational entry points - for example, iTerm2 specifically provides a [Window] menu bar for users to set window properties.
2. Having an adaptive window size should only serve as a fallback solution when users haven't set default window dimensions. I believe having dedicated functional entry points for our various settings would give higher priority to configuration options.
3. We recommend reviewing the default window placement strategy to better align with user expectations. Currently, new windows initialize at the screen's top-left corner, which differs from most applications' center-aligned approach. This requires manual repositioning for optimal workflow placement. A centralized default position would better serve:
   Immediate visibility upon launch
   Reduced cursor travel distance
   Consistency with platform UI conventions
   This adjustment could significantly enhance the initial interaction experience while maintaining existing customization capabilities.

[esimkowitz]

Thanks for the clarification, can you still separate these into separate actionable feature requests? It helps us track these better

[esimkowitz]

What os are you using? I've tested on Windows, Ubuntu, and macOS and the app doesn't initialize in the top-left corner...