Hi, @wp!!!
Thanks a lot for your as always very helpful and much constructive insights!
I am surely in favour of using as much external interface libraries as possible, to avoid the risk of depending upon unmaintained code.
As of THistoryFiles, I have long wondered why LCL did not include a MRU component! But it seems that my relatively old version (2.0.12) of Lazarus does not include any such component, therefore I had to resort to an external package. Now, I see a good reason for updating my Lazarus installation!
As of THTMLViewer, I have used that fine component since the first Delphi versions, almost three decades ago! I was delighted when I found out that it has been ported to Lazarus, and then I could keep using it. It is, as you pointed out, much better than the HTML viewer component which comes with Lazarus. But if it can, in some cases, replace the external component,
without compromising the functionality of the application, so I surely do not object. Just as an aside, I had not any issue with the DocumentSource property, either under Windows or Linux (I have another, much larger application, which also uses this component but compiles and runs fine either under both operating systems). Perhaps I am also using an older version of the package.
But the Vectors Library is a different case. In fact, this program only exists because of this library, since it provides much of the functionality which constitute the
raison d'être of the program. Probably, there are container classes in modern Lazarus which can replace the function provided by the Vector Library, but I can't say. In my opinion, the ideal solution would be to adapt the Vector Library to work in Lazarus uder Linux (because these problems do not appear under Windows).
I will take a look at your code and, in due time, may include one or more of the modifications in a new release of the Libro application.
Again, thank you very much for your help!
With warmest regards,