2023-02-11 21:16:48 +00:00
|
|
|
{{ define "title" -}}
|
|
|
|
{{( pgettext "Invoices" "title" )}}
|
|
|
|
{{- end }}
|
|
|
|
|
2023-03-20 12:09:52 +00:00
|
|
|
{{ define "breadcrumbs" -}}
|
|
|
|
{{- /*gotype: dev.tandem.ws/tandem/numerus/pkg.InvoicesIndexPage*/ -}}
|
2023-02-11 21:16:48 +00:00
|
|
|
<nav>
|
2023-04-02 14:10:13 +00:00
|
|
|
<p data-hx-target="main" data-hx-boost="true">
|
2023-02-11 21:16:48 +00:00
|
|
|
<a href="{{ companyURI "/" }}">{{( pgettext "Home" "title" )}}</a> /
|
|
|
|
<a>{{( pgettext "Invoices" "title" )}}</a>
|
|
|
|
</p>
|
2023-03-09 11:11:53 +00:00
|
|
|
|
|
|
|
<form id="batch-form" action="{{ companyURI "/invoices/batch" }}" method="post">
|
|
|
|
{{ csrfToken }}
|
|
|
|
<p>
|
|
|
|
<button type="submit"
|
|
|
|
name="action" value="download"
|
|
|
|
>{{( pgettext "Download invoices" "action" )}}</button>
|
|
|
|
<a class="primary button"
|
2023-03-31 11:01:26 +00:00
|
|
|
data-hx-push-url="false" data-hx-swap="beforeend" data-hx-boost="true"
|
2023-03-09 11:11:53 +00:00
|
|
|
href="{{ companyURI "/invoices/new" }}">{{( pgettext "New invoice" "action" )}}</a>
|
|
|
|
</p>
|
|
|
|
</form>
|
2023-02-11 21:16:48 +00:00
|
|
|
</nav>
|
2023-03-20 12:09:52 +00:00
|
|
|
{{- end }}
|
2023-02-11 21:16:48 +00:00
|
|
|
|
2023-03-20 12:09:52 +00:00
|
|
|
{{ define "content" }}
|
2023-02-11 21:16:48 +00:00
|
|
|
{{- /*gotype: dev.tandem.ws/tandem/numerus/pkg.InvoicesIndexPage*/ -}}
|
Add filters form for invoices
Instead of using links in the invoice tags, that we will replace with a
“click-to-edit field”, with Oriol agreed to add a form with filters that
includes not only the tags but also dates, customer, status, and the
invoice number.
This means i now need dynamic SQL, and i do not think this belongs to
the database (i.e., no PL/pgSQL function for that). I have looked at
query builder libraries for Golang, and did not find anything that
suited me: either they wanted to manage not only the SQL query but also
all structs, or they managed to confuse Goland’s SQL analyzer.
For now, at least, i am using a very simple approach with arrays, that
still confuses Goland’s analyzer, but just in a very specific part,
which i find tolerable—not that their analyzer is that great to begin
with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
|
|
|
<div aria-label="{{( pgettext "Filters" "title" )}}">
|
Trigger filter form on change and search, as well as submit as before
Changed the invoice number field’s type to search to add the delete icon
on Chromium. Firefox does not add that icon, but i do not care; it is
still better that type="text".
Had to emit the change event to the numerus-tag field, otherwise the
form would not detect the change.
I also can not use keyup as a trigger because the changed modifier can
not be used in the <form>, as nothing ever changes, i do not know how to
trigger the form from children (i.e., data-hx-trigger on the <input>
does nothing), and i can not trigger for just any keyup, or i would
make the request even if they only moved the cursor with the arrow keys,
which is very confusing as Firefox resets the position (this may be due
the fact that i reload the whole <main>, but still).
2023-04-03 10:45:15 +00:00
|
|
|
<form method="GET" action="{{ companyURI "/invoices"}}" data-hx-target="main" data-hx-boost="true" data-hx-trigger="change,search,submit">
|
Add filters form for invoices
Instead of using links in the invoice tags, that we will replace with a
“click-to-edit field”, with Oriol agreed to add a form with filters that
includes not only the tags but also dates, customer, status, and the
invoice number.
This means i now need dynamic SQL, and i do not think this belongs to
the database (i.e., no PL/pgSQL function for that). I have looked at
query builder libraries for Golang, and did not find anything that
suited me: either they wanted to manage not only the SQL query but also
all structs, or they managed to confuse Goland’s SQL analyzer.
For now, at least, i am using a very simple approach with arrays, that
still confuses Goland’s analyzer, but just in a very specific part,
which i find tolerable—not that their analyzer is that great to begin
with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
|
|
|
{{ with .Filters }}
|
|
|
|
{{ template "select-field" .Customer }}
|
|
|
|
{{ template "select-field" .InvoiceStatus }}
|
|
|
|
{{ template "input-field" .FromDate }}
|
|
|
|
{{ template "input-field" .ToDate }}
|
|
|
|
{{ template "input-field" .InvoiceNumber }}
|
|
|
|
{{ template "tags-field" .Tags }}
|
|
|
|
{{ end }}
|
|
|
|
<button type="submit">{{( pgettext "Filter" "action" )}}</button>
|
|
|
|
</form>
|
|
|
|
</div>
|
2023-03-07 10:52:09 +00:00
|
|
|
<table class="no-padding">
|
2023-02-11 21:16:48 +00:00
|
|
|
<thead>
|
|
|
|
<tr>
|
|
|
|
<th>{{( pgettext "All" "invoice" )}}</th>
|
|
|
|
<th>{{( pgettext "Date" "title" )}}</th>
|
|
|
|
<th>{{( pgettext "Invoice Num." "title" )}}</th>
|
|
|
|
<th>{{( pgettext "Customer" "title" )}}</th>
|
|
|
|
<th>{{( pgettext "Status" "title" )}}</th>
|
2023-03-10 13:02:55 +00:00
|
|
|
<th>{{( pgettext "Tags" "title" )}}</th>
|
2023-02-22 13:39:38 +00:00
|
|
|
<th>{{( pgettext "Amount" "title" )}}</th>
|
2023-02-11 21:16:48 +00:00
|
|
|
<th>{{( pgettext "Download" "title" )}}</th>
|
2023-03-08 10:54:06 +00:00
|
|
|
<th>{{( pgettext "Actions" "title" )}}</th>
|
2023-02-11 21:16:48 +00:00
|
|
|
</tr>
|
|
|
|
</thead>
|
|
|
|
<tbody>
|
2023-02-12 20:06:48 +00:00
|
|
|
{{ with .Invoices }}
|
|
|
|
{{- range $invoice := . }}
|
|
|
|
<tr>
|
2023-03-09 11:11:53 +00:00
|
|
|
{{ $title := .Number | printf (pgettext "Select invoice %v" "action") }}
|
|
|
|
<td><input type="checkbox" form="batch-form"
|
|
|
|
name="invoice" value="{{ .Slug }}"
|
|
|
|
aria-label="{{ $title }}"
|
|
|
|
title="{{ $title }}"/></td>
|
2023-02-12 20:06:48 +00:00
|
|
|
<td>{{ .Date|formatDate }}</td>
|
Add filters form for invoices
Instead of using links in the invoice tags, that we will replace with a
“click-to-edit field”, with Oriol agreed to add a form with filters that
includes not only the tags but also dates, customer, status, and the
invoice number.
This means i now need dynamic SQL, and i do not think this belongs to
the database (i.e., no PL/pgSQL function for that). I have looked at
query builder libraries for Golang, and did not find anything that
suited me: either they wanted to manage not only the SQL query but also
all structs, or they managed to confuse Goland’s SQL analyzer.
For now, at least, i am using a very simple approach with arrays, that
still confuses Goland’s analyzer, but just in a very specific part,
which i find tolerable—not that their analyzer is that great to begin
with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
|
|
|
<td><a href="{{ companyURI "/invoices/"}}{{ .Slug }}" data-hx-target="main"
|
|
|
|
data-hx-boost="true">{{ .Number }}</a></td>
|
2023-03-28 07:50:19 +00:00
|
|
|
<td>{{ .CustomerName }}</td>
|
2023-03-07 10:52:09 +00:00
|
|
|
<td>
|
|
|
|
<details class="invoice-status menu">
|
|
|
|
<summary class="invoice-status-{{ .Status }}">{{ .StatusLabel }}</summary>
|
2023-03-31 11:01:26 +00:00
|
|
|
<form action="{{companyURI "/invoices/"}}{{ .Slug }}" method="POST" data-hx-boost="true">
|
2023-03-07 10:52:09 +00:00
|
|
|
{{ csrfToken }}
|
|
|
|
{{ putMethod }}
|
2023-03-13 14:00:35 +00:00
|
|
|
<input type="hidden" name="quick" value="status">
|
2023-03-07 10:52:09 +00:00
|
|
|
<ul role="menu">
|
|
|
|
{{- range $status, $name := $.InvoiceStatuses }}
|
|
|
|
{{- if ne $status $invoice.Status }}
|
2023-03-08 10:54:06 +00:00
|
|
|
<li role="presentation">
|
|
|
|
<button role="menuitem" type="submit"
|
2023-03-13 14:00:35 +00:00
|
|
|
name="invoice_status" value="{{ $status }}"
|
2023-03-08 10:54:06 +00:00
|
|
|
class="invoice-status-{{ $status }}"
|
|
|
|
>{{ $name }}</button>
|
2023-03-07 10:52:09 +00:00
|
|
|
</li>
|
|
|
|
{{- end }}
|
|
|
|
{{- end }}
|
|
|
|
</ul>
|
|
|
|
</form>
|
|
|
|
</details>
|
|
|
|
</td>
|
2023-03-10 13:02:55 +00:00
|
|
|
<td>
|
|
|
|
{{- range $index, $tag := .Tags }}
|
|
|
|
{{- if gt $index 0 }}, {{ end -}}
|
Add filters form for invoices
Instead of using links in the invoice tags, that we will replace with a
“click-to-edit field”, with Oriol agreed to add a form with filters that
includes not only the tags but also dates, customer, status, and the
invoice number.
This means i now need dynamic SQL, and i do not think this belongs to
the database (i.e., no PL/pgSQL function for that). I have looked at
query builder libraries for Golang, and did not find anything that
suited me: either they wanted to manage not only the SQL query but also
all structs, or they managed to confuse Goland’s SQL analyzer.
For now, at least, i am using a very simple approach with arrays, that
still confuses Goland’s analyzer, but just in a very specific part,
which i find tolerable—not that their analyzer is that great to begin
with, but that’s a story for another day.
2023-03-29 14:16:31 +00:00
|
|
|
{{ . }}
|
2023-03-10 13:02:55 +00:00
|
|
|
{{- end }}
|
|
|
|
</td>
|
2023-02-22 13:39:38 +00:00
|
|
|
<td class="numeric">{{ .Total|formatPrice }}</td>
|
2023-03-07 10:52:09 +00:00
|
|
|
<td class="invoice-download"><a href="{{ companyURI "/invoices/"}}{{ .Slug }}.pdf"
|
|
|
|
download="{{ .Number}}.pdf"
|
|
|
|
title="{{( pgettext "Download invoice" "action" )}}"
|
|
|
|
aria-label="{{( pgettext "Download invoice %s" "action" )}}"><i
|
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
|
|
|
class="ri-download-line"></i></a></td>
|
2023-03-08 10:54:06 +00:00
|
|
|
<td class="actions">
|
|
|
|
<details class="menu">
|
|
|
|
<summary><i class="ri-more-line"></i></summary>
|
|
|
|
<ul role="menu" class="action-menu">
|
2023-03-13 14:00:35 +00:00
|
|
|
<li role="presentation">
|
2023-03-31 11:01:26 +00:00
|
|
|
<a role="menuitem" href="{{ companyURI "/invoices"}}/{{ .Slug }}/edit"
|
|
|
|
data-hx-push-url="false" data-hx-swap="beforeend" data-hx-boost="true"
|
|
|
|
>
|
2023-03-13 14:00:35 +00:00
|
|
|
<i class="ri-edit-line"></i>
|
|
|
|
{{( pgettext "Edit" "action" )}}
|
|
|
|
</a>
|
|
|
|
</li>
|
2023-03-08 10:54:06 +00:00
|
|
|
<li role="presentation">
|
|
|
|
<a role="menuitem" href="{{ companyURI "/invoices/new"}}?duplicate={{ .Slug }}">
|
|
|
|
<i class="ri-file-copy-line"></i>
|
|
|
|
{{( pgettext "Duplicate" "action" )}}
|
|
|
|
</a>
|
|
|
|
</li>
|
|
|
|
</ul>
|
|
|
|
</details>
|
|
|
|
</td>
|
2023-02-12 20:06:48 +00:00
|
|
|
</tr>
|
|
|
|
{{- end }}
|
|
|
|
{{ else }}
|
|
|
|
<tr>
|
|
|
|
<td colspan="7">{{( gettext "No invoices added yet." )}}</td>
|
|
|
|
</tr>
|
|
|
|
{{ end }}
|
2023-02-11 21:16:48 +00:00
|
|
|
</tbody>
|
|
|
|
</table>
|
|
|
|
{{- end }}
|