tandem
/
numerus
2
0
Fork 0
Code Issues 39 Pull Requests Packages Projects 1 Releases 1 Wiki Activity
numerus/web/template/invoices/view.gohtml

119 lines
5.2 KiB
Plaintext
Raw Normal View History

Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
{{ define "title" -}}
{{ .Number | printf ( pgettext "Invoice %s" "title" )}}
{{- end }}
{{ define "content" }}
{{- /*gotype: dev.tandem.ws/tandem/numerus/pkg.invoice*/ -}}
<nav>
<p>
<a href="{{ companyURI "/" }}">{{( pgettext "Home" "title" )}}</a> /
<a href="{{ companyURI "/invoices"}}">{{( pgettext "Invoices" "title" )}}</a> /
<a>{{ .Number }}</a>
</p>
Convert invoices to PDF with WeasyPrint Although it is possible to just print the invoice from the browser, many people will not even try an assume that they can not create a PDF for the invoice. I thought of using Groff or TeX to create the PDF, but it would mean maintaining two templates in two different systems (HTML and whatever i would use), and would probably look very different, because i do not know Groff or TeX that well. I wish there was a way to tell the browser to print to PDF, and it can be done, but only with the Chrome Protocol to a server-side running Chrome instance. This works, but i would need a Chrome running as a daemon. I also wrote a Qt application that uses QWebEngine to print the PDF, much like wkhtmltopdf, but with support for more recent HTML and CSS standards. Unfortunately, Qt 6.4’s embedded Chromium does not follow break-page-inside as well as WeasyPrint does. To use WeasyPrint, at first i wanted to reach the same URL as the user, passing the cookie to WeasyPrint so that i can access the same invoice as the user, something that can be done with wkhtmltopdf, but WeasyPrint does not have such option. I did it with a custom Python script, but then i need to package and install that script, that is not that much work, but using the Debian-provided script is even less work, and less likely to drift when WeasyPrint changes API. Also, it is unnecessary to do a network round-trip from Go to Python back to Go, because i can already write the invoice HTML as is to WeasyPrint’s stdin.
2023-02-26 16:26:09 +00:00
<p>
Add option to duplicate an invoice With Oriol we agreed that a duplicate is just the new invoice form prefilled with the data from another invoices, but without the number or the date.
2023-03-08 10:26:02 +00:00
<a class="primary button" href="{{ companyURI "/invoices/new"}}?duplicate={{ .Slug }}">{{( pgettext "Duplicate" "action" )}}</a>
Convert invoices to PDF with WeasyPrint Although it is possible to just print the invoice from the browser, many people will not even try an assume that they can not create a PDF for the invoice. I thought of using Groff or TeX to create the PDF, but it would mean maintaining two templates in two different systems (HTML and whatever i would use), and would probably look very different, because i do not know Groff or TeX that well. I wish there was a way to tell the browser to print to PDF, and it can be done, but only with the Chrome Protocol to a server-side running Chrome instance. This works, but i would need a Chrome running as a daemon. I also wrote a Qt application that uses QWebEngine to print the PDF, much like wkhtmltopdf, but with support for more recent HTML and CSS standards. Unfortunately, Qt 6.4’s embedded Chromium does not follow break-page-inside as well as WeasyPrint does. To use WeasyPrint, at first i wanted to reach the same URL as the user, passing the cookie to WeasyPrint so that i can access the same invoice as the user, something that can be done with wkhtmltopdf, but WeasyPrint does not have such option. I did it with a custom Python script, but then i need to package and install that script, that is not that much work, but using the Debian-provided script is even less work, and less likely to drift when WeasyPrint changes API. Also, it is unnecessary to do a network round-trip from Go to Python back to Go, because i can already write the invoice HTML as is to WeasyPrint’s stdin.
2023-02-26 16:26:09 +00:00
<a class="primary button"
href="{{ companyURI "/invoices/" }}{{ .Slug }}.pdf"
download="{{ .Number}}.pdf">{{( pgettext "Download invoice" "action" )}}</a>
</p>
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
</nav>
Convert invoices to PDF with WeasyPrint Although it is possible to just print the invoice from the browser, many people will not even try an assume that they can not create a PDF for the invoice. I thought of using Groff or TeX to create the PDF, but it would mean maintaining two templates in two different systems (HTML and whatever i would use), and would probably look very different, because i do not know Groff or TeX that well. I wish there was a way to tell the browser to print to PDF, and it can be done, but only with the Chrome Protocol to a server-side running Chrome instance. This works, but i would need a Chrome running as a daemon. I also wrote a Qt application that uses QWebEngine to print the PDF, much like wkhtmltopdf, but with support for more recent HTML and CSS standards. Unfortunately, Qt 6.4’s embedded Chromium does not follow break-page-inside as well as WeasyPrint does. To use WeasyPrint, at first i wanted to reach the same URL as the user, passing the cookie to WeasyPrint so that i can access the same invoice as the user, something that can be done with wkhtmltopdf, but WeasyPrint does not have such option. I did it with a custom Python script, but then i need to package and install that script, that is not that much work, but using the Debian-provided script is even less work, and less likely to drift when WeasyPrint changes API. Also, it is unnecessary to do a network round-trip from Go to Python back to Go, because i can already write the invoice HTML as is to WeasyPrint’s stdin.
2023-02-26 16:26:09 +00:00
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
<link rel="stylesheet" type="text/css" href="/static/invoice.css">
<article class="invoice">
<header>
Adapt the invoice design to Oriol’s
2023-02-25 12:48:57 +00:00
<div>
<h1>{{ .Number | printf ( pgettext "Invoice %s" "title" )}}</h1>
<p class="date">{{( pgettext "Date" "title" )}} {{ .Date | formatDate }}</p>
</div>
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
<address class="invoicer">
{{ .Invoicer.Name }}<br>
{{ .Invoicer.VATIN }}<br>
{{ .Invoicer.Address }}<br>
{{ .Invoicer.City }} ({{ .Invoicer.PostalCode}}), {{ .Invoicer.Province }}<br>
{{ .Invoicer.Email }}<br>
{{ .Invoicer.Phone }}<br>
</address>
Adjust invoice.css to work with WeasyPrint too I am planning to use WeasyPrint to “generate PDF” from the same HTML that the user view, but it seems that it does not support flex’s gap and some other properties that i had to change to work in both user agents. I also moved the invoice’s “footer” inside the last product’s body because i do not want the footer to be a “widow”.
2023-02-25 02:16:20 +00:00
Replace static legal disclaimer with a database field
2023-03-02 09:24:44 +00:00
<p class="legal">{{ .LegalDisclaimer }}</p>
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
</header>
<div>
<address class="invoicee">
{{ .Invoicee.Name }}<br>
{{ .Invoicee.VATIN }}<br>
{{ .Invoicee.Address }}<br>
{{ .Invoicee.City }} ({{ .Invoicee.PostalCode}}), {{ .Invoicee.Province }}<br>
</address>
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
{{- $columns := 5 | add (len .TaxClasses) | add (boolToInt .HasDiscounts) -}}
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
<table>
<thead>
<tr>
<th>{{( pgettext "Concept" "title" )}}</th>
<th class="numeric">{{( pgettext "Price" "title" )}}</th>
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
{{ if .HasDiscounts -}}
<th class="numeric">{{( pgettext "Discount" "title" )}}</th>
{{ end -}}
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
<th class="numeric">{{( pgettext "Units" "title" )}}</th>
<th class="numeric">{{( pgettext "Subtotal" "title" )}}</th>
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
{{ range $class := .TaxClasses -}}
<th class="numeric">{{ . }}</th>
{{ end -}}
<th class="numeric">{{( pgettext "Total" "title" )}}</th>
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
</tr>
</thead>
Adjust invoice.css to work with WeasyPrint too I am planning to use WeasyPrint to “generate PDF” from the same HTML that the user view, but it seems that it does not support flex’s gap and some other properties that i had to change to work in both user agents. I also moved the invoice’s “footer” inside the last product’s body because i do not want the footer to be a “widow”.
2023-02-25 02:16:20 +00:00
{{ $lastIndex := len .Products | sub 1 }}
{{ range $index, $product := .Products -}}
<tbody>
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
{{- if .Description }}
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
<tr class="name">
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
<td colspan="{{ $columns }}">{{ .Name }}</td>
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
</tr>
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
{{ end -}}
<tr>
{{- if .Description }}
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
<td>{{ .Description }}</td>
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
{{- else }}
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
<td>{{ .Name }}</td>
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
{{- end -}}
<td class="numeric">{{ .Price | formatPrice }}</td>
{{ if $.HasDiscounts -}}
<td class="numeric">{{ $product.Discount | formatPercent }}</td>
{{ end -}}
<td class="numeric">{{ .Quantity }}</td>
<td class="numeric">{{ .Subtotal | formatPrice }}</td>
{{ range $class := $.TaxClasses -}}
<td class="numeric">{{ index $product.Taxes $class | formatPercent }}</td>
{{ end -}}
<td class="numeric">{{ .Total | formatPrice }}</td>
</tr>
Adjust invoice.css to work with WeasyPrint too I am planning to use WeasyPrint to “generate PDF” from the same HTML that the user view, but it seems that it does not support flex’s gap and some other properties that i had to change to work in both user agents. I also moved the invoice’s “footer” inside the last product’s body because i do not want the footer to be a “widow”.
2023-02-25 02:16:20 +00:00
{{ if (eq $index $lastIndex) }}
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
<tr class="tfoot separator">
<th scope="row" colspan="{{ $columns | sub 1 }}">{{( pgettext "Tax Base" "title" )}}</th>
Adjust invoice.css to work with WeasyPrint too I am planning to use WeasyPrint to “generate PDF” from the same HTML that the user view, but it seems that it does not support flex’s gap and some other properties that i had to change to work in both user agents. I also moved the invoice’s “footer” inside the last product’s body because i do not want the footer to be a “widow”.
2023-02-25 02:16:20 +00:00
<td class="numeric">{{ $.Subtotal | formatPrice }}</td>
</tr>
{{ range $tax := $.Taxes -}}
<tr class="tfoot">
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
<th scope="row" colspan="{{ $columns | sub 1 }}">{{ index . 0 }}</th>
Adjust invoice.css to work with WeasyPrint too I am planning to use WeasyPrint to “generate PDF” from the same HTML that the user view, but it seems that it does not support flex’s gap and some other properties that i had to change to work in both user agents. I also moved the invoice’s “footer” inside the last product’s body because i do not want the footer to be a “widow”.
2023-02-25 02:16:20 +00:00
<td class="numeric">{{ index . 1 | formatPrice }}</td>
</tr>
{{- end }}
<tr class="tfoot">
Add discount and tax classes columns to invoice This was actually the (first) reason we added the tax classes: to show them in columns on the invoice—without the class we would need a column for each tax rate, even though they are the same tax. The invoice design has the product total with taxes at the last column, above the tax base, that i am not so sure about, but it seems that it has not brought any problem whatsoever so far, so it remains as is. Had to reduce the invoice’s font size to give more space to the table or the columns would be right next to each other. Oriol also told me to add more vertical spacing to the table’s footer.
2023-03-01 13:08:12 +00:00
<th scope="row" colspan="{{ $columns | sub 1 }}">{{( pgettext "Total" "title" )}}</th>
Adjust invoice.css to work with WeasyPrint too I am planning to use WeasyPrint to “generate PDF” from the same HTML that the user view, but it seems that it does not support flex’s gap and some other properties that i had to change to work in both user agents. I also moved the invoice’s “footer” inside the last product’s body because i do not want the footer to be a “widow”.
2023-02-25 02:16:20 +00:00
<td class="numeric">{{ $.Total | formatPrice }}</td>
</tr>
{{ end }}
</tbody>
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
{{- end }}
</table>
Adjust invoice.css to work with WeasyPrint too I am planning to use WeasyPrint to “generate PDF” from the same HTML that the user view, but it seems that it does not support flex’s gap and some other properties that i had to change to work in both user agents. I also moved the invoice’s “footer” inside the last product’s body because i do not want the footer to be a “widow”.
2023-02-25 02:16:20 +00:00
{{ if .Notes -}}
<p class="notes">{{ .Notes }}</p>
{{- end }}
Add the payment method to invoices
2023-03-05 17:50:57 +00:00
<p class="payment-instructions">{{ .PaymentInstructions }}</p>
Add invoice view, with print CSS Had to group name and description rows in tbody because i do not want to break them on pagination. I also could not use tfoot for subtotal, taxes, and total because then they appear on every page. The disclaimer should appear only at the very bottom of the last page, but i do not know how to do that; using position fixed shows it on every page.
2023-02-24 11:22:15 +00:00
</div>
</article>
{{- end}}