<<Originally posted by: blinehan>>
I'm a vbscript and ASP developer (not .NET yet though) and I was wondering if we could a tag added to the HTML output fields for the actual name of the movie (AVI or MPG or whatever). Then you could create a link in HTML that would play the movie itself. This would be HUGELY beneficial in allowing someone to build their own library and player while using Media Companion to manage it all. I know we have the <container> field and the <fullpathandfilename> field, so I could cobble those together after the HTML has been outputted(spelling?) but I thought it might be a nicer solution to try to have it done within the program already. That could actually lead to a nice/easy way of making a website accessible to any device (barring device limitations like Flash support) that could play the movies directly from the website. Ideas?


<<Posted by: HueyHQ>>
Yeah, your proposition sounds feasible. It's a shame <<fullpathandfilename>> includes the .nfo extension, otherwise it would be easy to concatenate <<format:container>> to it (I think <<container>> has been deprecated - I can't see it in the code).

Can I get some input on some options for this? I am thinking the base tag could be <<filename>> with path:file:ext as extenders?

For example, M\Movies\MyMovie.mkv:


<<filename>> -> M\Movies\MyMovie.mkv (default)
<<filename:file>> -> MyMovie
<<filename:file:ext>> -> MyMovie.mkv
<<filename:path:file:ext>> -> M\Movies\MyMovie.mkv
etc

That would go some way towards flexibility of accessing different files, say, a relative path on a website (eg <a href="\media\<<filename:file:ext>>"><<title>></a>), or the fanart (eg <img src="<<filename:path:file>>">-fanart.jpg>, altho' may not work if structured as movie per folder and files renamed 'movie', but will cross that bridge when we get to it.)

I would be particularly interested in any alternatives for the <<filename>> base tag (<<file>> is out as it is used elsewhere).