<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - New wizard for filling bank checks" href="https://bugs.documentfoundation.org/show_bug.cgi?id=123599#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - New wizard for filling bank checks" href="https://bugs.documentfoundation.org/show_bug.cgi?id=123599">bug 123599</a> from <a class="email" href="mailto:cwendling@hypra.fr" title="cwendling@hypra.fr">cwendling@hypra.fr</a> <pre>(In reply to Heiko Tietze from <a href="show_bug.cgi?id=123599#c4">comment #4</a>) > The maintenance issue is the same when the code goes into the core. With the slight but significant difference that API change would be picked up earlier and automatically I guess. > […] However, those templates would spam the > list/start center and should go at least into a separate folder. Yes. > Is your focus on a11y or on support? In the first case you may want to go > step-by-step through the form by asking for every single value, the second > could involve filling the data from a large list similar to mail merge. We'd focus on the a11y aspect first, but ideally we'd support both. Being able to emit a series of checks would be very handy, and likely one of the key feature appealing to most users. However, I'd think first start with a single output, that should be reasonably easy to expand to auto-fill from a linked data source.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>