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
The only way to really stave those off is to be stupidly customisable
Expected behavior
What I did with my PR was to make sure I was reusing the web ui as much as I could and still allow for skinning. I also used the web channel to communicate and not let the qml part communicate itself with the server especilly because of the v2 coming up. This also help with keeping the web ui and the QML part in sync #10539
Smallest useful scope
A simple QT launcher with basic qml support for customising a couple of things
Why this matters
You have a lot of people wanting a lot of different things from this project. We are already seeing a bunch of forks and people customising things and wanting customisations that don't make sense for the larger project. Some people want this to behave like vim some people want to have this plug into their issue workflow with a kanban board.
By making things extensible you get to pick good ideas from a bunch of different people making their own versions of the app. You also will have less people waiting on integrating their feature of choice and possible being upset with the project at not moving as fast as they like.
Excitement is also a really powerful thing and if people are able to make their own customisation they want they are going to spread the word about this project further
Captured on Linux/Hyprland from the isolated ~/.t3-validation/ environment at 189f425b5. The individual windows are 1500 × 1020. These are live Qt clients showing the same existing validation thread, not mockups. Images are GitHub attachments, not committed assets.
Default shell, before customization
Dashboard
Rosé palette, icon rail, carded conversation and composer, and the open widget drawer.
Glass
Unified toolbar, traffic-light window controls, and a rounded frame. Screenshot from a Macbook pro
Minimal
The web palette with the title bar moved to the bottom.
Terminal
Tokyo Night palette, monospace chrome, a compact status line, and the terminal drawer open.
Entire workspace 5
The terminal example at its normal window size on the desktop. The application is not maximized or fullscreen.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Before submitting
Area
apps/desktop
Problem or use case
The excitement about skinning and adding plugins in Omarchy is really impressive and the capabilies of QML to do hot updates and easy rearranging
There are other compeating products popping up doing a slight twist on what you are doing and you are just going to get more of those like:
https://www.codeagentswarm.com/en/guides/t3-code-vs-codeagentswarm
The only way to really stave those off is to be stupidly customisable
Expected behavior
What I did with my PR was to make sure I was reusing the web ui as much as I could and still allow for skinning. I also used the web channel to communicate and not let the qml part communicate itself with the server especilly because of the v2 coming up. This also help with keeping the web ui and the QML part in sync
#10539
Smallest useful scope
A simple QT launcher with basic qml support for customising a couple of things
Why this matters
You have a lot of people wanting a lot of different things from this project. We are already seeing a bunch of forks and people customising things and wanting customisations that don't make sense for the larger project. Some people want this to behave like vim some people want to have this plug into their issue workflow with a kanban board.
By making things extensible you get to pick good ideas from a bunch of different people making their own versions of the app. You also will have less people waiting on integrating their feature of choice and possible being upset with the project at not moving as fast as they like.
Excitement is also a really powerful thing and if people are able to make their own customisation they want they are going to spread the word about this project further
Contribution
For more context
https://quickshell.org/
https://plugins.omarchy.org/
Screenshots
Captured on Linux/Hyprland from the isolated
~/.t3-validation/environment at189f425b5. The individual windows are 1500 × 1020. These are live Qt clients showing the same existing validation thread, not mockups. Images are GitHub attachments, not committed assets.Default shell, before customization
Dashboard
Rosé palette, icon rail, carded conversation and composer, and the open widget drawer.
Glass
Unified toolbar, traffic-light window controls, and a rounded frame. Screenshot from a Macbook pro
Minimal
The web palette with the title bar moved to the bottom.
Terminal
Tokyo Night palette, monospace chrome, a compact status line, and the terminal drawer open.
Entire workspace 5
The terminal example at its normal window size on the desktop. The application is not maximized or fullscreen.
All reactions