Quoting Brian Rose <[EMAIL PROTECTED]>:
Well, for one it would be really awesome if the
invoice template was similar to iBiz,
http://www.iggsoftware.com/ibiz/index.html .
1. We don't want to have specific external targets from within
gnucash like that - the reference you quote is a moving target and
if we try to "fix" against it, it will always be a case of catch-up.
I wasn't suggesting mimicking iBiz.
Another option we've discussed previously is e-guile.. This would make
invoice templates effectively hand-written HTML with embedded guile..
So if you wanted to change the look at feel of your invoice you would
just edit the HTML until it looked how you wanted it to look.. And then
the embedded guile interpreter would run the template you created
and display it with the relevant information.
Then we could also distribute a bunch of templates (similar to iBiz)
and you could choose one or create your own.
Unfortunately as I was looking for an e-guile link I noticed that the
author restructured his website and the old page is no longer there.
I just emailed him about it. As I recall e-guile was effectively a single
source file, so we could just copy-and-paste it into GnuCash and then
someone would just need to figure out how to integrate it into the
report subsystem and set up a runtime environment for a report template.
2. Tips and advice on how to manage the gnucash codebase. The tools
to use and links to their documentation. Conventions and when to use
branches.
3. A concerted effort to bring the existing disparate docs into one
cohesive whole that is relevant, friendly, welcoming, genuinely
helpful and bridges the gap between the gnucash-docs package and the
gnucash-devel archives.
4. Regular and consistent updates to all documentation components.
Realistically, this can only be achieved by using a tool that
provides write access to all developers with CVS/SVN commit rights
plus a few others with documentation skills - i.e. some form of CMS.
I'd recommend Drupal.
Sounds good, but what do you think, Derek, about 2,3, and 4--directly above?
I think they sound like a great idea. I would love for someone to dedicate
time to coalescing all the various docs, finding out what docs are missing,
what docs are duplicated, and honing down our docs into:
user-docs (gnucash-docs package)
dev-docs (in doxygen)
build docs (README, HACKING, ...)
arch docs (everything else, which bridges the gaps)
I don't believe we'd need something like Drupal for this; I think this
could all be done in CVS/SVN.
Sincerely,
Brian
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
Member, MIT Student Information Processing Board (SIPB)
URL: http://web.mit.edu/warlord/ PP-ASEL-IA N1NWH
[EMAIL PROTECTED] PGP key available
_______________________________________________
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
