David Candy said:
There's lots of ways of doing it.
These convert mov (apple, an MS subsidary) files to Windows
files. My digital camera only records in mov.
I wasn't really interested in converting these files, they are for
personal and family use, and we all have quicktime. I like that you
can do minor editing right from the player.
As to scripting how's it supposed to work. Where are the shortcuts
going, where are the silly unusuable mov files (or of you convert,
the usuable avi files - if you want me to see them they better be
AVI)?
I see you are an *.avi fan. They are much more versatile but would
take much more room than the *.movs. For me, it was a simple
matter. The videos were *.mov to start with so I'm not putting time
into converting and such.
The general plan was to have a file hierarchy that resembles a table
of contents, so that a user who wanted to deal direct with the vids
could find there way around with no html or other guides.
Main_topic1
| | => etc
cat1 cat2
where vids concerning cat1 would be found on the file system at:
main_topic1/cat1/vid1 vid2 vid3 .... vidN
/cat2/vid1 vid2 vid3 ....
main_topic2/cat1/vid1 vid2 vid3 ... vidN
/cat2/vid1 vid2 vid3
The videos arent't really numbered, they wear names that reflect the
content. All several hundred are unique.
Then for most users I wanted to use an html guide and a pool of all
the vids (shortcuts really) at:
BIGMain/all_vids
that are really just shortcuts to those in the file
structure.
The big pool is to provide simple addressing for the lengthy html page
that will present the topics and provide links to start the associated
vids.
All vids can use a simple
<a href="BIGMain/all_vids/name.mov"></a>
And `BIGMain/all_vids' will remain the same for all of them.
With name.mov being a shortcut to those in the file hierarchy.
Creating the needed hierarchy and the 350 shortcut links (*.lnk) could
be scripted in any of the unix shell languages in 15 to 20 line of
code with for loops and iteration. Only there they would be symlinks
which is not understood by win XP filesystem.
So, I was looking for a way to do that on windows XP. More than likely
it will come up a number of times over the next mnths.
For now I've done it by hand by dragging and dropping with right mouse
but believe there is a better way... possibly involving scripting.