Hi Mark, On Mon, Oct 27, 2008 at 5:31 PM, Mark Fortner <[EMAIL PROTECTED]> wrote: > 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.
Great features! > 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. These ones seems amazing, specially those related to Word/OO.o. > 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. Check in go into trunk. We freeze trunk in the alpha (only bugfixes) and beta (only high-priority fixes) periods. IICR, these policies are explained in detail in the cookbook. > Do I need to create a bugzilla issue to commit the change set under? I'd suggest new issues and single commits for each feature, but as long as you seem to be the only current developer working on it, LGTM committing without an issue related. In the future, I suggest the create_issue-commit-mark_as_fixed approach. For those features that you're working in but not finished yet, I suggest to create the issues so if for any reason you stop interested in them (I hope that this won't happen), we have the ideas and thoughts about them in the tracker. > Regards, > > -- > Mark Fortner > > > > -- Cheers, Christian López Espínola <penyaskito>
