I've been working on updating ArgoPrint for the past week. Here are some of
the changes that I've made:
- Implemented a pluggable templating framework. The XSLT templating
mechanism was preserved, and I added support for the Velocity templating
language. Template engines are selectable based on the file extension of
the template selected by the user.
- Created a DiagramUtil class with a number of utility methods to make
accessing model information easier for template writers.
- Created a sample design document template. I created a design document
template in HTML.
What's still in the works:
- ability to generate diagrams as SVG and embed them in HTML.
- ability to export diagrams as PNGs - this would allow the user to
convert a diagram name into a file name, and automatically generate a PNG
version of the diagram.
- ability to export and embed diagrams as Base64 encoded images in HTML:
this allows the user to embed images directly into HTML to create a single
document without any external references.
- design document template in docx format for easy import into Word.
- handling of TODO items as tasks within the design document template -
this would create a simple project plan with links to a user-definable issue
tracker (i.e. Bugzilla, JIRA, Trac, etc).
- creating a profile to make the generation of design documentation
easier.
Questions:
- I read through the developer documentation and I didn't see any
information on the philosophy behind checkins. In argoprint/argouml, do you
typically check into a branch and merge for a release, or check into the
head and branch for a release? Different open source projects have
different philosophies, so I thought I would ask. Since argoprint has yet
to be released, it may not make a difference at this stage.
- Do I need to create a bugzilla issue to commit the change set under?
Regards,
--
Mark Fortner
