Dave Mielke wrote:
> Are you suggesting launching TRPlayer from TRPreset?
Yes.
> The -u option, in other words, would output the correct URL.
What about presets that should start playback in the middle of a clip or
in some clip other than the first one? Perhaps TRPreset could have a -q
(query) option that would print the URL, clip number, and offset in
seconds, separated by whitespace. That wouldn't be so hard to parse from
TRPlayer. In that case, the clip number and offset could be supported as
additional parameters at the end of the TRPlayer command line.
> People will probably find
> modifying interpreted source easier than modifying compiled source anyway.
I agree on that point.
> With p[rocessors becoming so fast these days, I wouldn't worry about it.
I've heard that reasoning before, and I'm not comfortable accepting it.
We should consider not only speed but RAM usage, and not everyone has
recent hardware. I have a friend who uses a machine with a Pentium
processor (don't know how fast) and 8 MB of RAM. I have another friend
who used to use a 486 with 8 MB of RAM, and later 16 MB of RAM, until she
got another computer in October or November of this year. Maybe I never
explicitly stated this, but one of my goals in developing TRPlayer is to
make it run well on older hardware, because the standard RealPlayer
doesn't.
> If in C, you'd have to install the correct XML library. Either way, something
> will have to be installed if it's not there. A good interpreter, rather than
> just a library, might be the better choice.
For a programmer, a good interpreter would be more beneficial. However, I
don't want to waste disk space on users' systems.
I may still write the first version of TRPreset in Python instead of C, so
I can develop it more quickly.
--
Matt Campbell
Web site: http://www.pobox.com/~mattcampbell/
ICQ #: 33005941
