Will the SeaMonkey 2 download manager also look like the above picture at some future point? Looks nice to me, nicer than what we have now; my feeling toward it is similar in nature if not necessarily in degree to why I prefer the Themes tab of the present add-ons manager to the Themes section of the former Preferences window. (As you undoubtedly know, the present SeaMonkey 2.0a3pre download manager hasn't even got a menu bar.)
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1b3pre) Gecko/20090102 SeaMonkey/2.0a3pre - Build ID: 20090102000540
<< Weekly Status Report, W52/2008 | The roads I take... | Weekly Status Report, W01/2009 >>
More On The New Download Manager
As I mentioned before, I started working on the SeaMonkey UI for the toolkit download manager backend.
In the last few days, I have progressed a lot on that, as one can easily see from the pushlog on the hg repository I created for backing up that work (and having the code out there if someone wants to test).
Here's a current screenshot of my work:
All the commands in the context menu are being activated and deactivated as they should and they are also all working as they should (that is, in SeaMonkey they probably are, opening the home page fails in Minefield, as SeaMonkey's utilityOverlay functions apparently can't open Firefox tabs). Also, the download progress is updated as it should, in the tree as well as the download manager window title.
What's not working yet is the toolbar commands (i.e. search and clear list) as well as sorting. Those are convenient and will of course be implemented before this can go into SeaMonkey (well, we haven't even switched the backend itself yet), but even without those, the download manager is already pretty usable.
If you want to test, just pull the repository, move/copy/symlink the dlmgrui@kairo.at directory in your Firefox profile's extensions/ directory and make sure the symlinks in its communicator/ subdir point to the right SeaMonkey files (or place copies of comm.jar, classic.jar and en-US.jar there).
Having done that, you should be able to launch your Shiretoko or Minefield copy and get this tree-based SeaMonkey download manager whenever the toolkit download manager should else be launched.
Of course, this is an add-on I'm only doing for development of the new SeaMonkey UI, I have no intention of making this a real Firefox add-on but to merge it into SeaMonkey code in the future - once we have the toolkit backend and this isn't WIP but a reviewed patch instead.
In the last few days, I have progressed a lot on that, as one can easily see from the pushlog on the hg repository I created for backing up that work (and having the code out there if someone wants to test).
Here's a current screenshot of my work:
All the commands in the context menu are being activated and deactivated as they should and they are also all working as they should (that is, in SeaMonkey they probably are, opening the home page fails in Minefield, as SeaMonkey's utilityOverlay functions apparently can't open Firefox tabs). Also, the download progress is updated as it should, in the tree as well as the download manager window title.
What's not working yet is the toolbar commands (i.e. search and clear list) as well as sorting. Those are convenient and will of course be implemented before this can go into SeaMonkey (well, we haven't even switched the backend itself yet), but even without those, the download manager is already pretty usable.
If you want to test, just pull the repository, move/copy/symlink the dlmgrui@kairo.at directory in your Firefox profile's extensions/ directory and make sure the symlinks in its communicator/ subdir point to the right SeaMonkey files (or place copies of comm.jar, classic.jar and en-US.jar there).
Having done that, you should be able to launch your Shiretoko or Minefield copy and get this tree-based SeaMonkey download manager whenever the toolkit download manager should else be launched.
Of course, this is an add-on I'm only doing for development of the new SeaMonkey UI, I have no intention of making this a real Firefox add-on but to merge it into SeaMonkey code in the future - once we have the toolkit backend and this isn't WIP but a reviewed patch instead.
Entry written by KaiRo and posted on January 3rd, 2009 00:46 | Tags: download manager, Mozilla, SeaMonkey, SeaMonkey 2 | 9 comments
TrackBack/Pingback
- fsdaily.com: Story added (TrackBack)
- Home of KaiRo: Weekly Status Report, W07/2009 (Pingback)
- Home of KaiRo: Download Progress Dialogs? Eww! (Pingback)
Comments
| Author | Entry |
|---|---|
| from Brussels, Belgium | 2009-01-03 01:07 |
| Webmaster | 2009-01-03 02:42 |
| pd | Apart from the strange use of the standard File Edit View etc menu, this download manager is infinitely better than the pathetic minimalist version inspired by all those Crapintosh-loving Firefox designers and coders. PLEASE! Can you convert this into an extension that replaces the dumbed-down version in Firefox? If not, where is the code, I'll try to do it myself. 2009-01-03 06:17 |
| Webmaster | The "pushlog" link in my post points to the code repository. I have no intention of porting it to a real Firefox extension as my target is to do it for SeaMonkey and I'm using a few SeaMonkey-specific things in the UI, but with some Add-On experience, it shouldn't be hard to port it to a real Firefox extension. 2009-01-03 16:03 |
| Jens Hatlak from Frankfurt, Germany | Clear List and the search bar alone are welcome improvements (and I think the former might deserves a real shortcut). Resumable downloads we get from the new backend which is also nice. One addition I'd like to see is Copy Full Path (of the resulting local file). 2009-01-05 00:44 |
| from The US | 1. Truncated downloads. 2. The inability to continue paused downloads between sessions. And speaking of Mercurial, is there going to be a CVS gateway after the switchover? I prefer to get the latest version from CVS, only updating a few files rather than the whole thing, but cloning an entire repository seems like more hassle than just downloading the source .tar.bz2. 2009-01-10 11:24 |
| Webmaster | AFAIK, we should be better WRT to truncations and cross-session resume with this new backend, but only using it in practice will fully tell. Regarding Mercurial, it's been multiple months already since we switched development to that and abandoned CVS for new development, and no, there's no CVS gateway and there won't be one. It sounds to me a bit as if you are slightly misguided about it though, as of course updating the source to a newer state after an initial clone also downloads only the changes that were made and not the whole tree again. 2009-01-12 17:26 |
| Ah, I might try to get it from Mercurial one of these days, when I have a few weeks to spare for the initial clone. 2009-01-28 01:24 | |
| Webmaster | 2009-01-28 02:29 |