c2c-oerpscenario team mailing list archive

["Nhomar \(Vauxoo\) - http://openerp.com.ve" <nhomar@xxxxxxxxx>]

2011/9/1 xrg <xrg@xxxxxxxxx>

> 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:
nhomar@xxxxxxxxxxxxxx <nhomar.hernandez@xxxxxxxxxxxxx>
nhomar@xxxxxxxxxxxxxxx
twitter: @nhomar

-- 
You received this bug notification because you are a member of C2C
OERPScenario, which is 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