• from sennago (france):

proposal for improvement: it is not possible to improve the quality of image compression on the invoice pdf? This one is very highly compressed relative to version 0.2 and it affects the quality of final bill.

With the version 0.2, my background image are 1280px of large (72dpi). Now, in 0.3, for enter in A4, I can change in 850px large and the quality is to low for see correctly the logo or text.

• from gael (france):

the inside label is really not comfortable to use as when you clic on a form field you have first to remove the inside label (in Chrome at least) and after you have removed the label you must clic on the field to know what field it is. I really invite you check the jquery plugin I sent you a few weeks ago.

It would be great to have a duplicate button on invoice and recurring invoice

The default template does not include any issue date. It would be great to use the "invoice.issue_date" to show how to display the date as there is for now no documentation of available tags

When checking more than one invoice and the print as PDF button it generates one file with all invoices what is not really usefull when you send invoice by email. It would be greate to propose to generate on pdf for each invoices instead.

Giving the possibilities to make some discount it's great but it would be better to have the choice between pourcentage discount or fix amount discount.

• from carlos ferreira (portugal):

Quanto a la SAFT-PT es obligatoria en Portugal en cualquier programa de facturación.

Sería muy importante para Siwapp ser bien aceptada en Portugal esta capacidad.

Aquí se encuentran alguns enlaces.

•  http://www.saftpt.net/osaft.htm
•  http://www.saftpt.com/validador.aspx
•  http://www.saft-pt.info/cms/o_que_e_o_saft-pt.php?lang=es

Te envio también um exemplo de un archivo saft de test.

• from piotr (poland):

BTW: Siwapp is not fully suitable to the requirements of Polish law. Eg in invoice view is missing amounts of VAT at each item. I can help in adjusting Siwapp to the Polish market.

• multiple accounts (for companies) and multiple users (for employees)
• data interchange such as: webAPI, RESTful, XML-RPC, SOAP...

1. be comply with the i18n and l10n (We need thier own, international, english dictionary of legal and business phrases and terms related to the accounting, tax and bill);
2. be simple ("CRUD") invoices manager;
3. be easy to use ("WYSIWYG") invoices editor;
4. handle multiple users - both employees / salesman and corporate clients / consumers (both B2C and B2B);
5. serve many companies - both issuer and recipient of invoices;
6. have a webAPI / webservice to integrate with other websites and desktop applications;
7. have a authenticity of invoice origin (e-sign eg GPG) and content integrity (hash, eg SHA-1) mechanisms;
8. have a full integration with the e-mail mechanisms - built-in webmailer or indirect integration (see section 6);
9. be able to import invoices to be archived in any format such as JPEG,PDF, and export / download / print to PDF;
10. have a functions to mass import / export data in a typical format,eg XML.

• from adrian moya (venezuela):

Me gustaría mucho que la versión 0.4 incluyera un API Restful. Se que ademas esto ayudaría en tratar varios puntos deseables en siwapp, como integración con plataformas de pago (que en mi opinión debería de ser posible a traves de integración via API y no como una parte de siwapp que me encanta que este enfocado en una sola cosa: facturas). Ademas de la creación automática de facturas y el tema de "multi-usuario" que me parece que a través del API como base se podrian crear portales para clientes que quieran consultar sus facturas en linea y tal...

Bueno la idea para mi es plantear los requerimientos del API y convertirlos en tickets, de manera de atacarlos de forma segmentada. Aun no me sente a estudiar el código, pero mi idea es reutilizar las clases existentes actualmente en la app de manera de no "romper" nada, solo hacer llamadas a clases internas que realicen las mismas operaciones que las que se hacen a través del frontend. Ahora, para el tema del multiusuario y permisología, para permitir a futuro a un cliente consultar sus facturas a través del API, si es importante una buena planificación a nivel de arquitectura de la app.

• from luke (uk):

In the twig template language, there is a filter "python style" for datetime objects or timestamps: it works like this: {{ object.issued_at|date("dd/mm/y")}}. It only works with timestamps or datetime objects , so a good improvement would be to let the templates access to timestamps instead of "date" strings, so they can be customized. Date formatting is very locale-sensitive.

Just an idea but perhaps having the client name stated as the Company Name and having a field for the telephone number for the customer would be a good addition?

• from the group:

Assign a specific print template to each invoice separately

Make it possible for siwapp to use different mailing mechanisms, since the swift mailer supports it. The point is whether to do it on the installation process or on the settings.

• from sturt:

By the way, Great application. Just one tip, would be GREAT to have  http://www.datatables.net/that one on the Bills list, autosearch, pagination and order by header. NOTE: it's a jquery plugin great for organizing lists.

• from kwiaty (blog):

For me best way with template will by not choose template for PDF or print, but some permanent join template on beggining. I need template when I send email, print, view, do a PDF. I will use different templates to give invoices from one company, but few another sections. I need another logos, language, etc … Try to think about this

• from daniel horton (group):

I didn't realize at first just how many files were in the app, so I actually uploaded the whole uncompressed directory through filezilla. One thing I've learned from working with other web apps (particularly things in a framework that have a large number of files) is that FTP tends to lose things when you get up into the thousands of files. At any rate, I reuploaded and just overwrote those with size differences, and things are running fine.