Project status:
GPL 3.0
(program only)

Additional info

The project is currently under development.

Expected arrival of an alpha build: Unknown, but no sooner than 2012.


All about SuperPipe

Isn't SuperPipe just another download manager?

Not really. A lot of the others concentrate on Torrents. Others are more about uploading rather than downloading. Plus, every existing download manager fights with other programs for bandwidth.

So how would SuperPipe solve the bandwidth conflict issue?

Imagine for a moment that programs like Firefox could let a download manager, like SuperPipe, handle all their downloads. Now the download manager knows about those other downloads and can give them priority. It can also keep the caller up to date.

The plan is provide an open API that those programs could use and other download managers (like Orbit) implement for themselves. Actually, there would be two APIs, each interchangeable. One would support .NET clients and download managers (SuperPipe) would use. The other would provide a C interface. A system would be implemented to allow programs to not deal with which API the other side is using. Another bridge might later allow for Java interfaces.

We would also provide a Windows control panel applet a way for users to specify which downloader to use. The C interface would be portable, so non-Windows users would need a counterpart.

How did SuperPipe come about?

Well, I used to use Reget Pro, a paid download manager. But they had bugs that they never fixed. In fact, they stopped coming out with new releases several years ago. Plus, I had troubles filing new problem reports.

So I replaced Reget with Orbit. But I don't like it either. Here is why:

  1. Unlike Reget, Orbit doesn't provide a quick way to control how much bandwidth it uses. Reget provides handy Red, Yellow, Green buttons for that. (Green is unlimited bandwidth. Red is really stingy.)
  2. Orbit doesn't have a true queue system. In Reget, moving items up the list moves them up in priority. However, Orbit insists on sorting the entries somehow.
  3. Orbit insists on checking tons of programs for updates. Basically, if you have it installed, Orbit might claim you need to update it. However, I checked on a lot of its claims. It was telling me I needed to update programs that were up to date.

    To me, this is a feature a downloader doesn't really need. I have no plans to shove this onto users. As for Orbit, I don't think you can turn its upgrade notifications off. There is a way to disable checking for upgrades to Orbit itself, but not other programs.

  4. Reget provides a handy way to delete completed downloads. Not Orbit. Now Orbit does allow you to provide an instant mirror to other Internet users for anything you download. But keeping those records in the list of completed downloads doesn't make sense.
  5. Orbit seems to ignore the directory I set at times. I am certain I set the folder, but the files once in a while end up elsewhere. I have also seen the default folder isn't always the correct default.
  6. Reget can show the progress for each download inside the row. Orbit makes you select the download.

How did the UI for SuperPipe come about?

So far, I have been mostly copying the UI for Reget. I don't know how much more of that I will copy. That remains to be seen.

Will there be any projects created to support SuperPipe?

Well, there is the API system. After that, I don't know. I have already coded some specialist controls for SuperPipe that ask for the size of something and the unit of measure for that value. (The UOM would be things like bytes versus gigabytes.)

I also started coding a control that looks a lot like a combobox. However, the drop list would show history. It would also have a browse button with just an ellipse (…) for text. That would bring up a file or folder browser.

Some of those controls could end up in their own SourceForge project.

Why are you using the SourceForge beta website?

Well, I wanted to try it out. However, as of now, I am already regretting it. They haven't implemented enough yet. Sorry. The good news is that they have fixed the problem that was preventing our forum pages from loading.

The project listing doesn't state which version of the GPL license is in use. Which version did you pick?

I went with GPL v3.0. Please note it is different from older versions of the GPL. The rights involved have changed and the new version isn't compatible with older versions. As for why the version isn't listed, please vote for it on SourceForge's IdeaTorrent. In my book, the designers of the beta website were a little shortsighted.

What back end are you using?

For now, all data is being stored in XML files. If SuperPipe later provides mirrors for downloaded files (like the above mentioned Orbit feature), that might be stored in SQLite or something similar.

What is the logo supposed to be?

Well, I am no artist. I was attempting to draw an cable to the Internet with data coming out of it. I am open to replacements, especially in the smaller sizes where it doesn't do that well.

What is required to existing builds of SuperPipe?

Why did you use .NET as the platform?

I was expecting to do most of the coding myself. .NET happens to be the only modern platform I know how to code for. That rules out GTK (think Inkscape and GIMP), JAVA, XUL (Mozilla), and more.

Why did you code in C# rather than VB?

Well in part, see the previous question. Until I learned C#, most of my coding experience was with MFC/C++. C# was closer to C++. As for why not C++ .NET, VC++ 2010 Express is missing too many features.

Why is XML back end for the project?

I learned long ago to be careful of binary formats. If you change the format, you trash all existing data that your users have. As for why not a RDBMS, we may need that later, but for the queues and preferences, it is simplier to store them in XML.

What do I need to compile the project?

How about some screenshots?

Sure. Go to this part of the Project gallery.

Where can I download the official logo?

Go to this part of the Project gallery. All sizes of the logo are available in PNG and SVG. All are available licensed CC-BY-ND-3.0 © 2011 Will Pittenger.

If I link to your site, which page should the link go to?

Either this page, which is our homepage, or the project listing. We certainly could use the links. If you do provide a link, please let us know in the Guestbook.

How can I help?

How can I join the project?

Go to our Join the project forum and post there. Please propose how you would fit in the project and provide eitehr a skill set or a link to a public skill set.