I got the idea for this tool when I read about mediadogg creating the HTTPJolie plugin. I had sometimes found that there were profiles that had been updated online that I had, for some reason, missed. I wanted to be able to compare my local profiles to their online counterparts in order to find those differences. So I created DpUpdateCheck to compare the unlocked sections of my profiles to the online. I figured that if I locked a section, then I wouldn't want to update it anyway. But ...

While testing I realized that most of the differences that I found were actually corrections that I had made to my local profiles, but that I had never contributed. So that changed the focus a bit, and I made the program more customizable.

Anyway, what it does is to compare the profiles that is in a DVD Profiler export file to the same profiles online, and create a flag file of the profiles that differ. This flag file is then saved in Profilers flag file directory, and you can load it in DVD Profiler. Then you can examine the differences (Online / Refresh DVD from Invelos / Preview Changes), or Alt-orc.

Since the checking can take some time you may want to work on something else while it is running, and therefore I have kept the main window very small:


The General Settings look like this:


And the Section Settings look like this:

The default is actually If not locked for all sections.

Download DpUpdateCheck version 1.0. Please read the help file, it contains important information!

And remember, you must have HTTPJolie installed in order to use DpUpdateCheck!

Please note that you don't have to run DVD Profiler/HTTPJolie elevated (as administrator) in order to use this integration!

Quoting Rander:

Quote:
My collection is just over 1000 titles, yet it runs thorugh the entire file in less than a second, saying there are no updates? In the sections, I have set everything to "Always", except Discinformation.

When you load the xml file, does DpUpdateCheck say that it has 1000 something profiles loaded?

Your xml file looks OK, at least at a quick check. And it sure runs through quick, so I really have to do some debugging to see what's going on. Sure looks like it's a bug. But I'll get back to you.

Quoting GSyren:

Quote:
Sure was a bug! I bypassed the check if the entire DVD was locked - which all yours were. 

ROTFLMAO! Honestly, for some reason, this made me laugh out loud, even though I'm home alone. In the past, I have done some programming myself, and this is the sort of thing that makes sense, until you remember the odd ways of users... :-)

Quote:

DpUpdateCheck 1.1 will fix that! Many thanks for reporting this problem so I could fix it!

Thank you very much, kind Sir! 

Hey Gunnar. Seems like much fun being had here.

I think you tested this, but have you found it faster or somehow better to do the Invelos XML export and reload from your tool, rather than getting the XML collection directly via HTTPJolie?

DpUpdateCheck 2.0

I couldn't resist taking on mediadogg's "challenge", getting local data from HTTPJolie instead of from an export file. Not surprisingly it's a bit slower. Reading from a file is faster that getting the same data via HTTPJolie. But you don't really have to wait for it, just let it run while you do something else.

On the plus side it offers greater flexibility in selecting which profiles to test.

You can check any standard or custom collection, or Flagged.


Or you can select Open flag set and use any saved flag set in DVD Profiler as input.

If you abort a run, you now get this message:


As stated in that message, when you save the result to an already existing file you get the option of either appending to that file or overwriting it.

And, as always, at least glance through the help file!

PS You can, if you wish, install version 1.1 and 2.0 side by side by unzipping in different folders. In case you want to compare them.

Quoting mediadogg:

Quote:
Holy smokes. I plant a small seed and this genius grows a tree overnight!!!

He he, not quite overnight. Changing the processing from reading an xml file to getting the data from HTTPJolie was easy. Selecting the input and handling the output took a little more thinking. But the ”boringest” part was updating the help file. Does any developer think documentation is fun?

The real genius is the guy who invented HTTPJolie. Without it the tree would have remained a seed.