Move the CPDF library into its own GIT subproject
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 11.2k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
Original author: eclecticgeek (September 03, 2010 00:48:03)
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: http://code.google.com/p/dompdf/issues/detail?id=178
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the repository structure and the CPDF development path, then assess the proposed SVN trunk, tagged versions, and externals arrangement; done would mean CPDF is maintained as a separate subproject while remaining usable by DOMPDF.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100