You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new feature is some behavior that is not existing already. If what you describe is a slight variation of something already existing please use a enhancement request.
Thanks for taking the time to fill out this feature request 🤗
Please make sure there aren't any open/closed request for this topic 😃
Is this the right place to report this request?
Please note that projects have their own repositories and issue trackers:
Is your feature request related to a problem? Please describe.
Currently, Pharo's UI does not allow users to freely drag and reposition windows or panels. This limitation makes it difficult to customize the workspace, especially when working with multiple tools like the debugger, playground, and browser side by side.
Describe the solution you'd like
A feature that allows users to:
Drag windows and panels freely within the Pharo environment.
Dock or snap windows to predefined areas to better organize the workspace.
Save and restore custom layouts, allowing users to maintain a preferred UI arrangement.
Describe alternatives you've considered
Floating windows could be used, but they are not as flexible as fully draggable UI elements.
Some IDEs use tiling window managers to allow splitting views instead of dragging.
Expected development cost
Medium to high effort, depending on how the current UI system is structured.
Requires changes in the window management system to support dragging and docking.
[Optional]Additional context
Many modern IDEs (e.g., Visual Studio Code, JetBrains, Eclipse) offer flexible layouts, improving productivity.
If this feature is already partially available, it could be framed as an enhancement request instead.
The text was updated successfully, but these errors were encountered:
A new feature is some behavior that is not existing already. If what you describe is a slight variation of something already existing please use a enhancement request.
Thanks for taking the time to fill out this feature request 🤗
Please make sure there aren't any open/closed request for this topic 😃
Is this the right place to report this request?
Please note that projects have their own repositories and issue trackers:
Pharo Launcher -> https://github.com/pharo-project/pharo-launcher
Virtual Machine -> https://github.com/pharo-project/pharo-vm
Spec -> https://github.com/pharo-spec/Spec
GTK -> https://github.com/pharo-spec/Spec-Gtk and https://github.com/pharo-spec/gtk-bindings
NewTools (Debugger, Playground, CodeCritiques, Spotter, New File Browser, New Finder, New Settings Browser) -> https://github.com/pharo-spec/NewTools
Roassal -> https://github.com/ObjectProfile/Roassal3
Is your feature request related to a problem? Please describe.
Currently, Pharo's UI does not allow users to freely drag and reposition windows or panels. This limitation makes it difficult to customize the workspace, especially when working with multiple tools like the debugger, playground, and browser side by side.
Describe the solution you'd like
A feature that allows users to:
Drag windows and panels freely within the Pharo environment.
Dock or snap windows to predefined areas to better organize the workspace.
Save and restore custom layouts, allowing users to maintain a preferred UI arrangement.
Describe alternatives you've considered
Floating windows could be used, but they are not as flexible as fully draggable UI elements.
Some IDEs use tiling window managers to allow splitting views instead of dragging.
Expected development cost
Medium to high effort, depending on how the current UI system is structured.
Requires changes in the window management system to support dragging and docking.
[Optional]Additional context
Many modern IDEs (e.g., Visual Studio Code, JetBrains, Eclipse) offer flexible layouts, improving productivity.
If this feature is already partially available, it could be framed as an enhancement request instead.
The text was updated successfully, but these errors were encountered: