I'm concerned about creating an API at the last minute, without time to review the rest of the problem space. The emblem API that is re- discussed in parallel, shows that APIs and design guidelines need to go together or else we risk making even more last minute changes.
I'd rather provide a non-documented, use-at-your-own-risk-if-your- not-U1, API for this release. And promote the API to public status for O, once all the ramifications of this case are well understood. The case in question is the one of service-oriented applications that lack permanent windows. The underlying infrastructure (bamf, launcher, libunity) is still heavily based on the assumption that an application has an open window. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/747677 Title: [FFE] Need API to set urgency from background process -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
