search

ststeiger / PdfSharpCore

Port of the PdfSharp library to .NET Core - largely removed GDI+ (only missing GetFontData - which can be replaced with freetype2)
Other
1.06k stars 239 forks source link

Why Solution Named "Stammbaum" #16

Closed jogibear9988 closed 5 years ago

jogibear9988 commented 6 years ago

Why is the Solution Name Stambaum.sln and not "PdfSharp" or smth. similar?

ststeiger commented 6 years ago

Because I originally incorporated this as part of a genealogy program. (I got the data from my grandfather's hobby program, and tried to integrate it with some existing genealogy program, and realized they're all crap, including but not limited to gramps, so I tried writing my own ). I was experimenting with how best to print out a pedigree (or Stammbaum in German), for which I thought PDF wouldn't be bad, and I was working on Linux with .NET, so I searched for .NET Core PDF libraries and there were none in a functional state.

I had since abandoned the project, because I realized graphing an arbitrary pedigree (with arbitrary holes and '2^n ancestors' - with ancestor shrinkage ) is a lot more difficult than I thought, and the best course of action was doing it with d3js and using wkhtml2pdf to create the pdf.

Some people on stackoverflow where then complaining about being unable to create pdf reports in .NET Core, upon which I pointed them to this repository - which is how it became 'popular'.

That's why it's called pedigree - because I hacked this together for a pedigree test application. It was not originally intended to share PdfSharp.

Project CoreDb is also in the repositories here. It was just used to read the data from the SQL database. I think if I remember right I experimented with git submodules, so if you'd do a git submodule init, git would fetch it - i think.

ststeiger commented 5 years ago

As I moved the original genealogical-tree-project to a new home, renamed the solution. Thus, renamed the solution.