English > Feature Suggestions
Vote: Features for 0.9.9
phalox:
I was wondering if there are some kind of plans to make movie importation more automatical ??
I mean if I have some kind of rip from a know ripper... Let's say Axxo. Then the name becomes [name] "axxo". Isn't there a way to remove "axxo" automatically ? Another usefull thing could be a readout from the .nfo files. There's allways a link to the imdb page of the movie.
What else: read the folder name. I think there are many people who name the folders as they should, but leave the file as it was.
Next to that a server-client version would be great... but I see that you won't be using any existing hosting based databases ?
An example: use Mysql to store all the data. This would be a great feature, since I have a NAS with integrated webserver...
Is it possible to add subtitle support ? Something like the checkbox for the 'watched' status. And this for multiple languages.
And the last thing that comes in mind: a possibiliy to make PVD data-files per movie. Wich contains one or more links and the name (and maybe some other data) for 1 movie. When you double click on it, it PVD opens, and asks if you want to add the file to your database.
This is something that would make partial transfers between databases really easy!
I must say that this is software with great potential. And now already a great set of features!
nostra:
--- Quote ---I mean if I have some kind of rip from a know ripper... Let's say Axxo. Then the name becomes [name] "axxo". Isn't there a way to remove "axxo" automatically ?
--- End quote ---
No problem with RegExp in 0.9.9.4 beta
--- Quote ---Another useful thing could be a readout from the .nfo files. There's allways a link to the imdb page of the movie.
What else: read the folder name. I think there are many people who name the folders as they should, but leave the file as it was.
--- End quote ---
You can change the Textfile script to read any kind of text files. See Creating own scripts.
--- Quote ---Next to that a server-client version would be great... but I see that you won't be using any existing hosting based databases ?
An example: use Mysql to store all the data. This would be a great feature, since I have a NAS with integrated webserver...
--- End quote ---
Supporting different kinds of DB eingines would make the program too complicated for me to program and for users to use. If you need such functionality take a look at Kroozbox - PVD to media theatre solution and PK's MovieDB dynamic website template
--- Quote ---Is it possible to add subtitle support ? Something like the checkbox for the 'watched' status. And this for multiple languages.
--- End quote ---
There is already support for subtitles, multiple languages, wish and many more things ;) Just play with the program a little bit more.
--- Quote ---And the last thing that comes in mind: a possibiliy to make PVD data-files per movie. Wich contains one or more links and the name (and maybe some other data) for 1 movie. When you double click on it, it PVD opens, and asks if you want to add the file to your database.
This is something that would make partial transfers between databases really easy!
--- End quote ---
It seems like this is the same as "Tag export/import (like ID3 for mp3)" requested by patch.
rick.ca:
--- Quote ---It seems like this is the same as "Tag export/import (like ID3 for mp3)" requested by patch.
--- End quote ---
The desired functionality might also be provided by the split and append/join features we've discussed before. If it's about sharing movie entries between databases (especially those of different users), this method is particularly appropriate. The tag import/export idea is about getting the movie reference right. The other user/database can then download whatever information they want. That doesn't help much if the point is to share the information that has been collected. The easiest and most effective way to do this would be to split (save in a new database) selected movies, and then be able to append this new database to another.
Nostra, you've indicated this is on your TODO list, but is it going to make it into 0.9.9? It seems my database has become too unwieldy for my tired old computer, but I don't even want to think about splitting it until I have the means to exchange records between databases. I'm thinking I could split my "Wish list" movies (about half) to a separate database, then move them into my main database as I acquire or plan to acquire them.
BTW, it occurs to me one of the complications you have to consider is the handling of custom fields. If a custom field does not exist in the target, would it be added, or would the data be omitted? I suppose another option would be to dump data from unmatched custom fields into the comments field.
patch:
--- Quote from: rick.ca on January 27, 2009, 10:01:54 pm ---The tag import/export idea is about getting the movie reference right. The other user/database can then download whatever information they want. That doesn't help much if the point is to share the information that has been collected.
--- End quote ---
Depends what is in the exported tag and how the functionality is implemented.
If it was user editable custom fields could in theory be added.
--- Quote from: rick.ca on January 27, 2009, 10:01:54 pm ---The easiest and most effective way to do this would be to split (save in a new database) selected movies, and then be able to append this new database to another.
--- End quote ---
I agree if the task is for a one off transfer of data, especially if the movie files are not being also shared.
If the data transfer occurs many times (with small incremental changes as additional movie files are shared over a network or remote site), then tagging the movie files would probably be easier for the user.
rick.ca:
--- Quote ---Depends what is in the exported tag and how the functionality is implemented.
--- End quote ---
The functionality I'm referring to is the sharing of all the information for a movie, exactly as it appears in the source data base, and quite intentionally not depending on anything else. The simplest case—copying entire records from one database to another—I would expect to be a straightforward Firebird utility function. But that's a technical matter beyond my understanding. If it had to be done as an export/import tag information operation, I'd be surprised, but I wouldn't care—I'm only interested in the end result.
--- Quote ---The tag import/export idea is about getting the movie reference right...
--- End quote ---
...so once download sources for information and images have been determined, other databases sharing the same media files don't have to search for and determine this information again.
These are different features for different purposes. I suppose we could conjure up situations where they overlap, but I don't see any benefit in doing so. I think both would be useful.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version