#2434 closed enhancement (wontfix)
replace Sugar-specific activity startup notification protocol with XDG startup notification
Reported by: | sascha_silbe | Owned by: | tomeu |
---|---|---|---|
Priority: | Unspecified by Maintainer | Milestone: | |
Component: | Sugar | Version: | Git as of bugdate |
Severity: | Major | Keywords: | |
Cc: | Distribution/OS: | ||
Bug Status: | New |
Description
By replacing our custom startup notification protocol with the XDG startup notification protocol we make it easier to interoperate with Sugar. It means one thing less to implement when modifying existing applications to run under Sugar (i.e. as an activity).
It's also a step towards better integration of non-Sugar ("legacy") applications.
Change History (4)
comment:1 Changed 13 years ago by sascha_silbe
- Type changed from task to enhancement
comment:2 Changed 13 years ago by sascha_silbe
comment:3 Changed 10 years ago by dnarvaez
- Resolution set to wontfix
- Status changed from new to closed
Integration with "plain" X applications hasn't really improved in the last few years. We are moving towards a web based toolkit. I don't think this is worth the effort at this point. Still patches welcome etc.
Note: See
TracTickets for help on using
tickets.
FWIW, we don't need to change anything on the activity side: GTK already automatically handles the "launchee" side as long as at least one window gets opened and startup notification doesn't get explicitly disabled on that window.