@mantielero I have looked a bit into the Poppler API, and I think you have started a really difficult task. Poppler has a lot low-level stuff, like the GLists of poppler.Rectangle or poppler.ImageMapping. Gintro would create proxy objects for these, but I noticed that these are not opaque types in poppler, so we have to access the fields. That makes it a bit difficult. Memory management for non-proxy objects in GLists is difficult. I will do some small tests today, maybe gintro can handle it. I think we should continue with proxy objects, as gintro converts them from GLists to Nim seqs automatically. But then we have to create getter and setter procs for the fields manually.
I still wonder why you are not using ordinary tools like the poppler-utils for extracting the pictures. Have you contineously to extract hundreds of pictures on a daily basis? Then coding a tool would make sense? There seems to be not much poppler tutorials available, so we may have to look at the source of poppler-utils to write our code? And I have heard of no one using poppler in the last 10 years, so I guess asking for details on a forum or mailing list will not have much success. Until yesterday, I had no idea how picture extractions may work with poppler, and I had to do much googling. Personally, if I would need such a tool, I would use poppler from plain C or maybe C++, as that seems to be simpler. For extracting pictures from documents: Personally I would be not that happy when someone would extract pictures from my PhD thesis without asking for permission. For forking repositories: I would never do that myself without asking the original author for permission, but I guess that GitHub allows it, and it is no real problem for me.
