On Thursday 30 December 2004 11:02, s. keeling wrote: > The first time I tried it, I was in my home dir, which didn't have > enough space to hold it. I C-c'd out, cd'd to where I did have space, > copied what it had got so far, then re-ran the command. It checked > the existing file, then continued on from where I'd C-c'd > > No idea what btdownloadheadless means, and btdownloadgui complained > about python for me too. If you read the Wired article, it mentions > good reasons (health related) for his missing small details like > usability and documentation.
Thanks. I'll give it another go later tonight. This is the part that's starting to bug me about open source. Here's a sample of a good tool that for one reason or another the developer(s) haven't been able to provide decent documentation for (with regards to an end user, not a techie). This much can be expected - us techs generally aren't the best at thinking about documenting what we do. But the tool IS open source, and has been in use for some time. I would expect that SOMEONE would have put together some decent docs by now. BitTorrent doesn't deserve undo credit for this failing - it applies to almost all open source packages I've used, with some noticeable exceptions (i.e. Apache, PostgreSQL, Gentoo, etc.). Maybe it's just me but I would think a popular open source project would have good instructions on how to USE the tool, not just install it (task based instructions, versus tech based instructions). (Another great example - Checkout the Drupal Handbook at http://www.drupal.org, and try to figure out how to create simple navigation menus based on the stored content and categories/taxonomy. It's all either for the wrong version, or requires a plug-in, or custom coding. For something that should be clearly defined as being a core part of the project IMO. Don't get me wrong though - Drupal is a great tool and I'm still cutting my teeth on it...) Shawn _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
