This is a great plug-in for international users, I was hoping for the main program to add this years ago for titles like Once Upon a Time in the West. However, the plug-in would be much more useful if there was a filter option to search for a title across all fields. If I enter Once Upon a Time in the West as the international english title, I can filter for it, but this filter will not show discs that actually do use this title, e.g. a US DVD. I need a way to make it work so that searching for "Once Upon" shows discs that actually use this title AND discs where I entered it as the international title. Is this possible? Without me entering the international title for all thousands of discs on my wishlist

Any chance of an update which includes the feature I mentioned? I also noticed that the actual original title of the disc does not get exported when exporting to csv/excel. Could this column please be added? It is part of the XML export.

Done

Another feature request Please add the Production Year as a column to the (Excel) export, it's quite useful to distinguish films.

Awesome. You quoted the wrong post, so I didn't even realize at first that you added the search feature I requested! Thanks, it works as suggested

As you say though, it is indeed quite slow. Here are some suggestions to make it faster. I'm not sure if and how these are possible in terms of profiler plug-ins, they come from my perspective as a developer.

1) Don't start searching for the first two entered characters, it's unlikely that someone actually wants to filter that way. You can still actually run that search if, after a wait of, let's say, 2 seconds, no further character is entered

2) Only search within the current filtered dataset. This is especially true if I just add a character to the existing search term, but it also applies to other filters already applied.

3) Only search within the current collection category. From usage tests, it feels like there is no speed difference depending on my selected category, so it seems you always load and search all profiles. In my case, with thousands of wishlisted titles, this means wasting a lot of time.

4) This is actually a workaround, but would probably solve all performance problems and be easier to develop too?! Find a way to duplicate/store the profiler title fields in your own plug-in data structure. That way, you search within that and it's lightning fast again

Quoting hydr0x:

Quote:
Awesome. You quoted the wrong post, so I didn't even realize at first that you added the search feature I requested! Thanks, it works as suggested

As you say though, it is indeed quite slow. Here are some suggestions to make it faster. I'm not sure if and how these are possible in terms of profiler plug-ins, they come from my perspective as a developer.

1) Don't start searching for the first two entered characters, it's unlikely that someone actually wants to filter that way. You can still actually run that search if, after a wait of, let's say, 2 seconds, no further character is entered

The minimum search term length is possible.

Quote:

2) Only search within the current filtered dataset. This is especially true if I just add a character to the existing search term, but it also applies to other filters already applied.

3) Only search within the current collection category. From usage tests, it feels like there is no speed difference depending on my selected category, so it seems you always load and search all profiles. In my case, with thousands of wishlisted titles, this means wasting a lot of time.

Unfortunately the API gives you the profile you are to inspect, I cannot pre-select the number of profiles which I will inspect.

Quote:

4) This is actually a workaround, but would probably solve all performance problems and be easier to develop too?! Find a way to duplicate/store the profiler title fields in your own plug-in data structure. That way, you search within that and it's lightning fast again

That seems like a bit of an overkill to enhance the performance of an additional search.

Quoting hydr0x:

Quote:


That is unfortunate. I wonder if the API has some kind of other function that might help. Is the documentation available somewhere outside the plug-in developer forum?

Why not just join the developer forum?  don't recall anybody ever being refused. Of course, given the current state of affairs, I'm not sure if anybody is entertaining those requests. There are internal filters available, and I am sure that he is using those already. They are limited. Only other ways I know of to speed things up are (and again, DJ knows all this stuff), are to exclude Cast/crew and personal info from the filter, or run a filter file internally  (pre-generated or build the XML dynamically), then grab the resulting displayed collection. In that case you still suffer the delay caused by the GUI rendering. Anything not supported by the API internal filters, or the XML filter file search, requires inspecting the individual profiles. Again, with an exception: if you happen to have the XML collection handy, then you can use an XPath to grab a (relatively) quick result.

Hmm ... DJ maybe you didn't have to sign anything, but when I became a developer, I had to actually sign a contract agreeing not to reveal the API.