|
|
95.
|
|
|
use an application client (the GTK client) installed on each computer.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst:12
|
|
|
96.
|
|
|
The two methods of access give very similar facilities, and you can use both on the same server at the same time. It is best to use the web browser if the OpenERP server is some distance away (such as on another continent) because it is more tolerant of time delays between the two than the GTK client is. The web client is also easier to maintain, because it is generally already installed on users' computers.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst:14
|
|
|
97.
|
|
|
Conversely you would be better off with the application client (called the GTK client because of the technology it is built with) if you are using a local server (such as in the same building). In this case the GTK client will be more responsive, so more satisfying to use.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst:21
|
|
|
98.
|
|
|
Web Client and GTK Client
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst:30
|
|
|
99.
|
|
|
There is little functional difference between the two OpenERP clients - the web client and the GTK client at present. The web client offers more functionality, for instance, the Corporate Intelligence feature, and the Gantt view.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst:32
|
|
|
100.
|
|
|
When you are changing the structure of your OpenERP installation (adding and removing modules, perhaps changing labels), you might find the web client to be irritating because of its use of **caching**.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst:36
|
|
|
101.
|
|
|
Caching speeds it all up by keeping a copy of data somewhere between the server and your client, which is usually good. But you may have made changes to your installation that you cannot immediately see in your browser. Many apparent faults are caused by this! The workaround is to use the GTK client during development and implementation where possible.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst:40
|
|
|
102.
|
|
|
The OpenERP company will continue to support two clients for the foreseeable future, so you can use whichever client you prefer.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst:36
|
|
|
103.
|
|
|
An OpenERP system is formed from three main components:
|
|
|
|
|
Un sistema de OpenERP esta formado por tres componentes principales
|
|
Translated by
Alexandro Colorado
|
|
Reviewed by
Alexandro Colorado
|
|
|
|
Located in
../../source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst:20
|
|
|
104.
|
|
|
the PostgreSQL database server, which contains all of the databases, each of which contains all data and most elements of the OpenERP system configuration,
|
|
|
|
|
el servidor de base de datos PostgreSQL, el cual contiene todas las bases de datos, cada una contiene todos los datos y la mayoría de los elementos de configuración relacionados con el sistema OpenERP,
|
|
Translated by
Alexandro Colorado
|
|
Reviewed by
Alexandro Colorado
|
|
|
|
Located in
../../source/book/1/1_1_Inst_Config/1_1_Inst_Config_architecture.rst:22
|
