Summary
In v2.0.0, I noticed that the tray module now pulls in dependencies such as nucleus-application and window-decoration-tao. These are relatively large dependencies, but they're only needed when using the optional TrayApp functionality.
Would it be possible to split the current module into something like:
tray-core – contains the basic tray API and implementation.tray-app – contains TrayApp and depends on nucleus-application, window-decoration-tao, and any other application-specific functionality.
Motivation
Many applications only need basic system tray support and don't use TrayApp. Splitting the module would:
- Reduce the dependency footprint for users who only need tray functionality.
- Avoid pulling in unnecessary transitive dependencies.
- Make the tray API more lightweight and modular.
- Allow users to opt into
TrayApp only when they need its additional features.
Summary
In
v2.0.0, I noticed that the tray module now pulls in dependencies such asnucleus-applicationandwindow-decoration-tao. These are relatively large dependencies, but they're only needed when using the optionalTrayAppfunctionality.Would it be possible to split the current module into something like:
tray-core– contains the basic tray API and implementation.tray-app– containsTrayAppand depends onnucleus-application,window-decoration-tao, and any other application-specific functionality.Motivation
Many applications only need basic system tray support and don't use
TrayApp. Splitting the module would:TrayApponly when they need its additional features.