Steve Dodier wrote: > > Imo, it should be ok to use a notify-osd notification + a systray icon for > updates as soon as they're available, and to pop-up the window only on > extreme cases : > @ Steve: The pop-up window seems like a reasonable option in the scenario's you've given... But i feel that automatic Pop-ups in any form should be discouraged... IMO pop-up/under are a security flaw. NO window Should populate the window list unless the user has opened it... [A Daemon process should NOT open new programs on its own without asking for user's permissions or explicit user settings] A better alternative would be a Notification system that allows interaction/ morphing alert box [So these could present the user with the options to either download&Install now or To dismiss] *And repeating the notifications at the time of user's choice*... which makes the need for a systray icon[as a remainder] unnecessary. Also the DX team has made it very clear that systray icon WILL NOT return... I had been very vocal here opposing the change but i went with it... And *even though it might not have been the intended purpose* for the removal of the icon, *I have found the icon removal useful* ... *Now I dont think much about the updates* , there is no icon nagging me about the updates. Just think about the "Updates" , its just a sugar-coated word for "oops-the-devs-didnt-realize-this-mistake-earlier" , Updates are for the flaws which wasnt realized while baking the release... and to be fair to all devs ,no OS can EVER do it perfectly without a need for updates. So, instead of drawing so much attention to these updates , making it easy for the end-user to not pay much attention is a more ideal way of thinking. As mpt has said that they are looking for a decent solution,This is what i'v proposed in Ayatana, with Hopes the DX Team takes notice ==For updates to be less intrusive to the user== * From an idea proposed by David Siegel , And further expanding it.... When the user receives the updates notification,user "chooses to download & Install the packages" , * Installation of Updates the dont require restart are done immediately, * Before starting the installation of package+dependencies, which requires a restart, the user is warned that this particular package requires a reboot. * User either chooses, "install now" or "during next boot" . For good implementation of this, updates need to be clearly marked as 1:security 2:critical>solves a major crash/freeze issue of the package / major improvement of package responsiveness 3:non-critical>minor tweaks to performance So when the user is presented with the update requiring reboot,he is told that [1]"This update solves a crash/freeze problem seen in this package/Gives you major improvement of package responsiveness" [2] "This update is a non-critical update" [3] "This is a security Update" * So the user decides , if he has the problem, he can do the update immediately... If not, delay it for the next boot. * If the user later decides to update before the reboot, he should be able to do so from the update manager, where a reminder says"Install pending updates". * The same can be done for the firefox updates too... download the updates when the user accepts and since it requires restart of the browser , WAIT till the browser is closed and then install the updates. So no need to restart the browser. * When the user has chosen not to download updates , These notification repeat again at a later time[10mins/30mins/1hr/4hrs/1day/7days],which the user chooses from a drop-down menu and if the user tries to shutdown before updating he is reminded again via the same alerts. Cheers, mac_v