This is fun, particularly for actors playing many secondary roles in TV Series, e.g.


I imagine cast headshots are not saved in the xml exported file. That's too bad, it would add to the fun to have a face along with the name.

At any rate, thanks for this new toy! 

Quoting Wigram:

Quote:
I imagine cast headshots are not saved in the xml exported file.

You're imagining right. And unlike cover scans (and thumbnails) they are not saved as separate images, but - as far as I can tell - embedded in the database files, so not accessible.

I had identified two problems in DpLink:
- The same title could be listed twice
- Clicking a director could produce a result with no title links

I believe I have fixed both those bugs in DpLink 1.0.1.

Quoting Rander:

Quote:
May I ask what language you are programming in?

Before Windows 95 came along, I was not bad at Borland Turbo Pascal, though I never really got around to doing anything graphical in it. Later, I did a lot of php, and lately I have been looking a bit at Python. But I would like to find something that's not too difficult to do Windows-programs (and if the same source can be compiled to Linux also, that would be a bonus)... 

That's really two questions; what do I use and what should you use. Let's start with some background.

The two most obvious choices for programming language are C# and Visual Basic. "Classic VB" was introduced by Microsoft in 1990, and became really popular with VB 3.0 in 1993. When Microsoft introduced .Net Framework in 2002 they scrapped Classic VB - much to the chagrin of many VB developers - and introduced VB.Net and C#. Those have very similar capabilities, but new features have usually been introduced in C# before VB.Net. Still, there are very few thing that you can do in C# that you can't do in VB.Net. Unless you have a C or C++ background, VB.Net is most likely easier to learn than C#, but not by all that much.

Then there is the matter of graphical subsystem. You have the older WinForms and the newer - but not really new - WPF (Windows Presentation Foundation). WPF offers far superior capabilities over WinForms, but also has a higher learning curve. Some say that in WPF the complex is made easy and the simple is made difficult. That's not true, but there is a grain of truth in it.

Me, I started programming VB over 25 years ago, and I am a stubborn SOB, so I am not changing to C# unless I am absolutely forced to. Which hopefully will not happen before they carry me out feet first. As regards WinForms vs. WPF, I switched to WPF exclusively in 2004, and I haven't looked back since.

I know very little about Linux, but I doubt that either C# or VB.Net can be easily ported to Linux. If portability is high on your list, then I guess that Java might be a good choice. Since you have a background with Turbo Pascal, you could check out Free Pascal, which I understand is cross-platform. But I doubt it is as convenient as developing C# / VB.Net with Visual Studio, which has a free Community Edition.

That makes everything crystal clear, right? 

Edit: I should add that there is a lot more sample code available in C# than in VB.Net, so you might take that into consideration as well. Although, most of it is easily translated into VB.Net. https://codeconverter.icsharpcode.net/ is a good help.