Yet another MovieJukebox...

[maikone]

Hi, I'm trying this very nice program on a USB NTFS formatted Hard drive with a *.bat with the following:

Moviejukebox.bat f:\_Transfer -nr "file:///opt/sybhttpd/localhost.drives/USB_DRIVE_A/_Transfer/"

If I plug the USB Drive later on my PCH I can start the index file, but if I try to start one of this movies, nothing is happen!
What is wrong with the phat/directory?

Thanks.

PS: Is it possible to ad also *.MOV extension or why not ad all extensions supported by PCH?
If I can see, like in a log file how many movies detected, how many found in IMDB and how many not analyzed, this could be very useful for me with a lot of movies.

[gandalf]

maikone Wrote:Hi, I'm trying this very nice program on a USB NTFS formatted Hard drive with a *.bat with the following:

Moviejukebox.bat f:\_Transfer -nr "file:///opt/sybhttpd/localhost.drives/USB_DRIVE_A/_Transfer/"

If I plug the USB Drive later on my PCH I can start the index file, but if I try to start one of this movies, nothing is happen!
What is wrong with the phat/directory?

Thanks.

PS: Is it possible to ad also *.MOV extension or why not ad all extensions supported by PCH?
If I can see, like in a log file how many movies detected, how many found in IMDB and how many not analyzed, this could be very useful for me with a lot of movies.

try USB_DRIVE_A-1

[jjulien]

jriihi Wrote:Hi jjulien,

I looked your code and added multiple directories and nmtpaths to it as exercise. It seems to need configuration file implementation because easily goes over command line limit (255 chars?).
I didnt implement any configuration file yet. Do you think properties or xml file would be better? I think xml file would be more readable..?

After configuration file is implemented it could be added to svn (current implementation works only for like max 3 dirs).

Great!! Thanxx!

imho properties files are easier to read, edit and document... so my vote goes to a property file.

[jjulien]

jjulien Wrote:

jriihi Wrote:Hi jjulien,

I looked your code and added multiple directories and nmtpaths to it as exercise. It seems to need configuration file implementation because easily goes over command line limit (255 chars?).
I didnt implement any configuration file yet. Do you think properties or xml file would be better? I think xml file would be more readable..?

After configuration file is implemented it could be added to svn (current implementation works only for like max 3 dirs).

Great!! Thanxx!

imho properties files are easier to read, edit and document... so my vote goes to a property file.

In fact the tool definitely needs a property file, I'll make one.
But you're right, to specify a list of couple values { { path1, nmtPath1}, {..,..}}, XML is more apropriate!

[jriihi]

jjulien Wrote:In fact the tool definitely needs a property file, I'll make one.
But you're right, to specify a list of couple values { { path1, nmtPath1}, {..,..}}, XML is more apropriate!

Actually my current version has exclusion filters and file extensions specified in xml also. Anyways look at my old code in bug tracker maybe

Just looked at MovieFilenameScanner and there seems to be lot of stuff that could be read from configuration xml.

[shay1972]

What a great application.
Works great.
However, i do have some trouble trying to config the display of the index.html page.
I am trying to increse the font size and reduce the number of images per line.
I have edited 'exportindex_item_pch.css' in the 'C:\MovieJukebox_v1.0.6_beta\resources' directory to increase the font size, however i see that my 'jukebox' directory has those files already.
I have deleted them from the 'jukebox' directory, and let them be copied automaticlly again, but they are not identical to the files that i have modified - they returned to defualt setting.
What am i doing wrong?

[Grael]

Bad luck, css and xsl are embedded in the moviejukebox.jar...

If you have a zip tools (like 7 zip), open moviejukebox.jar and remove those files from the jar.

[sTyLeS]

Yes, would be better if the app did not use files embedded in the jar for any purpose. Would make customizing that much easier.

[shay1972]

thank you, it works great.
It will be wise to export does file out of the .jar for further configuration, and also, becuae it says so in the README.....

[shay1972]

another thing - i managed to display only 5 images in the index page. In order to make them bigger, i tried the -th and -tw options in the command line, but the executable did not get these options and returned error.
I see in the README that the command line cannot take these options but they are mentioned as 'OPTIONAL', so which is correct, and will it be added later?
Thanx

[sTyLeS]

I have another suggestion if I may. Just an ease of use sort of thing.
There is also a proprietary attribute called TVID which when placed within an <a href> tag will allow the associated remote control button to access said link.

For example, on the detail page, the final link that plays the movie, you could add TVID="Play" inside the <a href> tag to allow the movie to be played simply by pressing the Play button on the remote, instead of having to navigate to the link and press enter. Of course, navigating to the link will still work, but the Play button is just a simplification.

[Grael]

shay1972 Wrote:i tried the -th and -tw options in the command line, but the executable did not get these options and returned error.

May be because the MovieJukebox.bat doesn't pass through enough parameters
replace

Code:

java -classpath ./moviejukebox.jar;./resources com.moviejukebox.MovieJukebox %1 %2 %3 %4 %5 %6

by

Code:

java -classpath ./moviejukebox.jar;./resources com.moviejukebox.MovieJukebox %1 %2 %3 %4 %5 %6 %7 %8 %9 %10 %11 %12 %13

[gfb107]

Fix both issues are once: put ./resources before ./moviejukebox.jar in the classpath, and use %* to get all the command line parameters:

Code:

java -classpath ./resources;./moviejukebox.jar com.moviejukebox.MovieJukebox %*

[Grael]

Nice!

[gfb107]

sTyLeS Wrote:I have another suggestion if I may. Just an ease of use sort of thing.
There is also a proprietary attribute called TVID which when placed within an <a href> tag will allow the associated remote control button to access said link.

For example, on the detail page, the final link that plays the movie, you could add TVID="Play" inside the <a href> tag to allow the movie to be played simply by pressing the Play button on the remote, instead of having to navigate to the link and press enter. Of course, navigating to the link will still work, but the Play button is just a simplification.

There's lots of those kinds of things that can be done.
Like setting TVID="PGUP" for the "Previous" link, and TVID="PGDN" for the Next link. Also give the "Play" link the name "Play" and adding ONLOADSET="Play" to the body tag. This will put the initial focus on that link.

Too bad we can't do simple javascript navigation menus with forms and selects. Would be nice to have the Genres be a drop-down menu.

Code:

<form action="genres.html" method="GET">
<select onChange="window.location.href=this.value;return false;">
<option value="index_Action.html">Action</option>
<option value="index_Adventure.html">Adventure</option>
<option value="index_Animation.html">Animation</option>
<option value="index_Crime.html">Crime</option>
<option value="index_Drama.html">Drama</option>
</SELECT>
</form>

There are lots of different ways to code this, but I haven't found any that work with the PH, although I have found documents that claim the PH brower supports some ECMA-script.