[WISHLIST] Remove save button in binary widget

Bug #838432 reported by Moisés López - http://www.vauxoo.com
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Odoo GTK Client (MOVED TO GITHUB)
Confirmed
Wishlist
OpenERP sa GTK client R&D
Odoo Web Client
New
Undecided
Unassigned

Bug Description

For determination of law requires that the file is represented in a widget-> fields.binary not have the save button.
We need to have an attribute to control this type of case.
As: attr ['with_save_button'] = False

I put the patch With These wishlist

Greetings!

moylop260
vauxoo

Revision history for this message
Moisés López - http://www.vauxoo.com (moylop260) wrote :
Revision history for this message
Moisés López - http://www.vauxoo.com (moylop260) wrote :

In Latin America, we need to send data directly to printers tax, and must match what you say openerp
Therefore we have developed a module, which sends commands to the printer, and must be sent directly to the ejecuación.
Without allowing storage.
This solved it by removing the save button on the widget binary field.

And install an additional program running the file type (by extension), with the fiscal printer script

Revision history for this message
Nhomar - Vauxoo (nhomar) wrote :

Hello.

We in vauxoo are developing the Venezuela localization, the main leak of the syste right now is to be able to execute python code on client side, IMHO with this little improvement it can be partially solved.

I want to confirm this as a wishlit, an please try patch, we have alreade some related scritps to run in client side Moises is working with us on Venezuela and this concept is already tested, some videos soon.

Changed in openobject-client:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
xrg (xrg) wrote : Re: [Bug 838432] Re: [WISHLIST] Remove save button in binary widget

On Thursday 01 September 2011, you wrote:
> In Latin America, we need to send data directly to printers tax, and must
> match what you say openerp ...

It may be the same with what "account_greek_fiscal" has been doing. Sending the
invoice report directly to printer, w/o permission of the client to interfere
with the data..

Revision history for this message
Moisés López - http://www.vauxoo.com (moylop260) wrote :

These fiscal printer not is a normal printer.
Its need a communication via serial port & commands to write.
1. OpenPort
2. OpenTicket
3. SaleItems
4. CloseTicket
5. ClosePort

Its need:
1. Driver in client
2. App what execute sentences to serial port.
3. File with parser sentece, generate with server and execute directly

> Date: Thu, 1 Sep 2011 10:58:03 +0000
> From: <email address hidden>
> To: <email address hidden>
> Subject: Re: [Bug 838432] Re: [WISHLIST] Remove save button in binary widget
>
> On Thursday 01 September 2011, you wrote:
> > In Latin America, we need to send data directly to printers tax, and must
> > match what you say openerp ...
>
> It may be the same with what "account_greek_fiscal" has been doing. Sending the
> invoice report directly to printer, w/o permission of the client to interfere
> with the data..
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/838432
>
> Title:
> [WISHLIST] Remove save button in binary widget
>
> Status in OpenERP GTK Client:
> Confirmed
>
> Bug description:
> For determination of law requires that the file is represented in a widget-> fields.binary not have the save button.
> We need to have an attribute to control this type of case.
> As: attr ['with_save_button'] = False
>
> I put the patch With These wishlist
>
> Greetings!
>
> moylop260
> vauxoo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-client/+bug/838432/+subscriptions

Revision history for this message
Nhomar - Vauxoo (nhomar) wrote :

Hello Xrg.

Can you give us the branch to see if it is the same?

Thanks

2011/9/1 xrg <email address hidden>

> On Thursday 01 September 2011, you wrote:
> > In Latin America, we need to send data directly to printers tax, and must
> > match what you say openerp ...
>
> It may be the same with what "account_greek_fiscal" has been doing. Sending
> the
> invoice report directly to printer, w/o permission of the client to
> interfere
> with the data..
>
> --
> You received this bug notification because you are subscribed to the
> OpenERP Project Group.
> https://bugs.launchpad.net/bugs/838432
>
> Title:
> [WISHLIST] Remove save button in binary widget
>
> Status in OpenERP GTK Client:
> Confirmed
>
> Bug description:
> For determination of law requires that the file is represented in a
> widget-> fields.binary not have the save button.
> We need to have an attribute to control this type of case.
> As: attr ['with_save_button'] = False
>
> I put the patch With These wishlist
>
> Greetings!
>
> moylop260
> vauxoo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-client/+bug/838432/+subscriptions
>

--
Saludos Cordiales

Nhomar G. Hernandez M.
+58-414-4110269
Skype: nhomar00
Web-Blog: http://geronimo.com.ve
Servicios IT: http://openerp.com.ve
Linux-Counter: 467724
Correos:
<email address hidden> <email address hidden>
<email address hidden>
twitter: @nhomar

Revision history for this message
xrg (xrg) wrote :

On Thursday 01 September 2011, you wrote:
> These fiscal printer not is a normal printer.
> Its need a communication via serial port & commands to write.
>...
> Its need:
> 1. Driver in client
> 2. App what execute sentences to serial port.
> 3. File with parser sentece, generate with server and execute directly

Same here. (see "fiscal_prints.py") But I preferred to install the printer
against the /server/, not the client. Because, I thought, it is better to have
the fine-settings in the server machine, and then equally let any client
connect and issue invoices through OpenERP.
Else, you see, somebody could connect to the db through a "normal" openerp
client and bypass the fiscal printing setup.
Note that the serial printer /can/ be installed (physically) at the client
machine. Only that it must be controlled by the server application, not the
gtk client or so. (what if you wanted to use the web-client also? )

Revision history for this message
Nhomar - Vauxoo (nhomar) wrote :

2011/9/1 xrg <email address hidden>

> On Thursday 01 September 2011, you wrote:
> > These fiscal printer not is a normal printer.
> > Its need a communication via serial port & commands to write.
> >...
> > Its need:
> > 1. Driver in client
> > 2. App what execute sentences to serial port.
> > 3. File with parser sentece, generate with server and execute directly
>
> Same here. (see "fiscal_prints.py") But I preferred to install the printer
> against the /server/, not the client. Because, I thought, it is better to
> have
> the fine-settings in the server machine, and then equally let any client
> connect and issue invoices through OpenERP.
>

I'm agreed with you, but, for features on this printer, we just need to lock
what widget does, if i can send python code to client (web and gtk), and
this code be excecuted with an exec() instruction it should be the way.

We install just a loval driver on client side and it will be already solved,
for now, just "open with an special program" is the solution we can faund,
and for this this property on widget is necesary.

Correct me if i'm wrong! ;-)

> Else, you see, somebody could connect to the db through a "normal" openerp
> client and bypass the fiscal printing setup.
>
It is no possible.
The Fiscal printer _must_ be installed on client side, because, it is used
just by a cash box.
With this feature, you just need to declare a little program on client that
open our file and send directly to printer,

> Note that the serial printer /can/ be installed (physically) at the client
> machine. Only that it must be controlled by the server application, not the
> gtk client or so. (what if you wanted to use the web-client also? )
>

With web is the same, but i just install GTK for leaks on Web-Client, it
will be used for a really limited user, this user just sale.

We got internally this discussion already, and is not possible to administer
"as printers" this special fiscal devices.

We need to communicate with local serial ports.

>
> --
> You received this bug notification because you are subscribed to the
> OpenERP Project Group.
> https://bugs.launchpad.net/bugs/838432
>
> Title:
> [WISHLIST] Remove save button in binary widget
>
> Status in OpenERP GTK Client:
> Confirmed
>
> Bug description:
> For determination of law requires that the file is represented in a
> widget-> fields.binary not have the save button.
> We need to have an attribute to control this type of case.
> As: attr ['with_save_button'] = False
>
> I put the patch With These wishlist
>
> Greetings!
>
> moylop260
> vauxoo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-client/+bug/838432/+subscriptions
>

--
Saludos Cordiales

Nhomar G. Hernandez M.
+58-414-4110269
Skype: nhomar00
Web-Blog: http://geronimo.com.ve
Servicios IT: http://openerp.com.ve
Linux-Counter: 467724
Correos:
<email address hidden> <email address hidden>
<email address hidden>
twitter: @nhomar

Revision history for this message
xrg (xrg) wrote :

On Thursday 01 September 2011, you wrote:
> Hello Xrg.
>
> Can you give us the branch to see if it is the same?
>

It's the 'trunk-xrg' branch on Sourceforge or Igloo:

http://git.hellug.gr/?p=xrg/openobject-addons
http://openerp-addons.git.sourceforge.net/git/gitweb.cgi?p=openerp-
addons/openerp-addons;a=summary

About the discussion: let's both agree that we give 2 possible solutions to
the same issue. For the Greek market, it is true that the fiscal printer is
connected to the cash box too (it must provide the "key" to print on the
invoice, although the fiscal device may be separate from the printer that we
use for the customer's "receipt").

My consideration is that I define a "protected area" of software and hardware
installation. The fiscal printer, the driver and the business logic must be
_audited by authorities_, to ensure that no receipt can be printed w/o getting
through the complete flow. So, I wanted this "protected area" to be outside of
OpenERP's software management (versions, installations, hacks). Since the
client and the server might change at any point, I made a clear separation of
the OpenERP's invoicing logic and the "fiscal printing". And put most of that
protected stuff in the server, because the server is more closely administered
than the client machines.

It is still doable to work through CUPS. I wrote a special wrapper for that,
talking to the serial port, too. I could provide you with full design plans
etc. And the benefit of the CUPS logic is that it can easily be networked, so
that it is physically placed where the fiscal printer needs to be installed.

(to be continued.. - I hope :] )

Revision history for this message
Moisés López - http://www.vauxoo.com (moylop260) wrote :
Revision history for this message
Moisés López - http://www.vauxoo.com (moylop260) wrote :

We need execute a file, since a app.
Because these app execute a library C

Revision history for this message
xrg (xrg) wrote :

On Friday 02 September 2011, you wrote:
> ** Attachment added: "Architecture of fiscal printer"
>
> https://bugs.launchpad.net/openobject-client/+bug/838432/+attachment/23417
> 36/+files/Impresora%20Fiscal%20-%20Arquitectura%20de%20Desarrollo.pdf

There you are: that's my architecture

The fiscal "machine" and the "app" could either be at the server machine or the
client, I don't care (CUPS bridges them). But their installation
(administration rights) is what I was concerned. I wouldn't allow a windows
user to fiddle with them.

Changed in openobject-client:
assignee: nobody → OpenERP sa GTK client R&D (openerp-dev-gtk)
importance: High → Wishlist
Revision history for this message
Jorge Saldaña (jorgesaldanan) wrote :

Hi Here in Panama i need to do the same in order to follow the new fiscal law using fiscal printers, so any one can help me with these. I don't know if any one has a working solution ??

Revision history for this message
Nhomar - Vauxoo (nhomar) wrote :

HEllo.

Please follow the Venezuela Localization team, this particularry is not the place to make wuetion, open a new one and we open a answer serie.

Revision history for this message
Israel Fermin Montilla (iferminm) wrote :

Hi Jose,

This is a little offtopic here, this isn't the right place to make questions
because this is a bug report.

We, the Venezuela Localization Team, are developing a module to integrate
the Fiscal Printing functionality into OpenERP, I encourage you to visit our
project page, download and test our module and make as many questions as you
want.

El 4 de octubre de 2011 23:32, Jorge Saldaña
<email address hidden>escribió:

> Hi Here in Panama i need to do the same in order to follow the new
> fiscal law using fiscal printers, so any one can help me with these. I
> don't know if any one has a working solution ??
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/838432
>
> Title:
> [WISHLIST] Remove save button in binary widget
>
> Status in OpenERP GTK Client:
> Confirmed
>
> Bug description:
> For determination of law requires that the file is represented in a
> widget-> fields.binary not have the save button.
> We need to have an attribute to control this type of case.
> As: attr ['with_save_button'] = False
>
> I put the patch With These wishlist
>
> Greetings!
>
> moylop260
> vauxoo
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/openobject-client/+bug/838432/+subscriptions
>

--
Israel Fermín Montilla
Twitter: @iferminm
Cel: +58426 806 7890
Skype: iffm5150
PIN: 242E20D6
Blog: http://iferminmontilla.net
Servicios IT: http://vauxoo.com

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.