@ktadd
Quote:
ClipDown was initially designed to just be a download assistant for OWB until it received it's own download capabilities built-in. Initially it only relied on wget being in the C: directory. I never really expected it to devepe into what is has now.
Yes I know that
Quote:
I chose to use ToolTypes and command line options for setup so it's easy to run multiple copies of ClipDown taylored for the specific program you want to use it with. (ie. different screens and options.)
In this case I think it would be more of a pain to have to start the program then change the options from a preferences program each time you wanted to use it with a different programs.
Yes but aniway if one develop a simple GUI, tooltypes can remain as is and can be usefull if someone need more control over it, one choice doesn't exclude another
Quote:
Well, if I didn't use existing programs it would take me a very very long time to code up the capability they provide built in and ClipDown would never exist. I did think about building in the getvideo functionallity but that would also cause significant delay and with gnash on the horizon to play flash videos I'm not sure it's worth the effort. wget, getvideo and MPlayer are all significant efforts and without them ClipDown would not exist.
Agree
Quote:
Sorry, I don't think I'm going to spend the time doing that right now. Maybe if there is a lot of demand but it wouldn't eliminate the need to install the dependency programs.
If you put the dependency programs in the C: directory there should be not setup required unless you want to set different options.
Do people find Shift-Clicking on a ToolType entry to activate or deactivate it or modifying Tooltypes that difficult? I'd like to receive more input on this.
Ok you are right, is correct to see more feedback on that from other users, maybe I'm the only one ...
Imagine that my situation using ClipDown is the same of your avatar