This is a PR following the Discord discussion where people wanted to use dg2d as a dub dependency.
Before putting it on the dub registry it would need a bit of reorg, if you are okay with it.
demo code is now under ./demo and has its own dub.json
You can generate the demo VisualD project with:
cd demodub generate --compiler ldc2 [--combined] visuald
I've not updated the existing VisualD project.
source code of the library has moved to source/dg2d/ for import paths
font.d now part of the library code instead of the example code.
What I would really recommend now is to have a package.d and only put there stuff that will be in the public API (in other words, boundaries).
It can help long-term to separate stuff that is private from stuff that is in the public API (ideally: few things are public).
eg: dg2d.blitex would not be imported by package.d
This is a PR following the Discord discussion where people wanted to use dg2d as a dub dependency. Before putting it on the dub registry it would need a bit of reorg, if you are okay with it.
demo code is now under ./demo and has its own
dub.jsonYou can generate the demo VisualD project with:
cd demodub generate --compiler ldc2 [--combined] visualdI've not updated the existing VisualD project.
source code of the library has moved to
source/dg2d/for import pathsfont.dnow part of the library code instead of the example code.What I would really recommend now is to have a package.d and only put there stuff that will be in the public API (in other words, boundaries). It can help long-term to separate stuff that is private from stuff that is in the public API (ideally: few things are public).
eg:
dg2d.blitexwould not be imported bypackage.d