search

rvpatel / dompdf

Automatically exported from code.google.com/p/dompdf
0 stars 0 forks source link

Move the CPDF library into its own SVN subproject #178

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Since DOMPDF is *supposed* to be library independent I think it would make 
sense to have the development of the CPDF renderer be semi-independent of the 
DOMPDF library. Naturally the two have to be developed somewhat hand in hand, 
especially since CPDF is the default library of DOMPDF. However, I don't see 
any reason we can't develop the library in it's own SVN path and use SVN 
externals to pull it back in. Following standard SVN development practices we 
can develop in the CPDF trunk and link to tagged versions.

I like this idea, but it certainly deserves scrutiny from everyone else. 
Worthwhile or not?

Original issue reported on code.google.com by eclecticgeek on 3 Sep 2010 at 12:48

GoogleCodeExporter commented 9 years ago

Original comment by eclecticgeek on 24 May 2013 at 3:00