Why not? I would think they share similar characteristics. Long duration, point-to-point movement of blocks of data, asynchronous operation, worthy of notification when completed.
Seems like a slick solution to problems that are a bit of a mish-mash. Things that would be questionable to me would be a render operation that takes like five minutes. Something that exists completely withing the CPU. But maybe a case could be made there too. On Wed, 2010-04-14 at 12:38 +0100, Mark Shuttleworth wrote: > I think the idea of an aggregated "downloads" indicator has merit. > > I'm not sure about other long-running processes, like a copy-to-network > or burn-cd action. > _______________________________________________ Mailing list: https://launchpad.net/~ayatana Post to : ayatana@lists.launchpad.net Unsubscribe : https://launchpad.net/~ayatana More help : https://help.launchpad.net/ListHelp
