On Mon, Oct 19, 2009 at 20:18, Wade Brainerd <[email protected]> wrote: > On Mon, Oct 19, 2009 at 3:04 PM, Tomeu Vizoso <[email protected]> wrote: >> On Mon, Oct 19, 2009 at 20:01, Wade Brainerd <[email protected]> wrote: >>> ....Side note: Since the Journal displays the progress bar as files >>> are downloaded, wouldn't it be cool if Browse just handed the download >>> off to the Journal? That would allow the download to continue even >>> after Browse stops. It would also allow the download to be resumed if >>> the machine is restarted, network connection lost, etc. Worthy >>> Journal feature request? >> >> This was the desired user experience, but mozilla's architecture made >> it quite hard without losing the ability to download inside existing >> http sessions. > > I see what you mean about sessions. Is there some way to detect > whether a download is dependent on the browser session? > > Another option, though it would not allow later resuming, would be to > let the Browse instance keep running even after the activity has > "stopped". It would just hide its main window and send some other > termination notice to the Sugar shell. The activity failure notice > patch might be a good start; Browse could just send a > NotifyActivityEnded message to the shell without terminating its > process.
Yes, we could do something like that, though I'm afraid we would risk trading considerable fragility to fundamental use cases in exchange of lower gains. Though this largely depends on the effort put, so if someone is so inclined... Regards, Tomeu -- «Sugar Labs is anyone who participates in improving and using Sugar. What Sugar Labs does is determined by the participants.» - David Farning _______________________________________________ Sugar-devel mailing list [email protected] http://lists.sugarlabs.org/listinfo/sugar-devel
