← Back to branch summary

~openerp-spain-team/openerp-spain/6.0-git

« back to all changes in this revision

Viewing changes to l10n_es_toponyms/l10n_es_toponyms_wizard.xml

  • Committer: Borja L.S.
  • Date: 2010-10-18 10:04:25 UTC
  • Revision ID: git-v1:271c47a993616dbba60585d48b8b98d603199d93
[REF] *: Refactorización para portar a 6.0 - Paso 1.

- Se han renombrado los módulos para usar la nomenclatura propuesta
  por OpenERP: l10n_es para el módulo base de localización (plan de 
  cuentas), l10n_es_* para el resto de módulos.

- Se eliminan los módulos extra_addons/* que deberían moverse a 
  los extra-addons genéricos (no son específicos de España).

- Se renombran los __terp__.py por __openerp__.py

Show diffs side-by-side

added added

removed removed

Lines of Context:
l10n_es_toponyms/l10n_es_toponyms_wizard.xml
 
1
<?xml version="1.0" encoding="utf-8"?>
 
2
<openerp>
 
3
    <data>
 
4
 
 
5
       <record id="view_confirm_toponyms_es_form" model="ir.ui.view">
 
6
            <field name="name">config.ES.toponyms</field>
 
7
            <field name="model">config.ES.toponyms</field>
 
8
            <field name="type">form</field>
 
9
            <field name="arch" type="xml">
 
10
                <form string="State configuration">
 
11
                    <separator col="4" colspan="4" string="Select the toponym version of the Spanish states"/>
 
12
                    <field name="state"/>
 
13
                    <label colspan="2" string="For example: Official (Girona), Spanish (Gerona), Both (Gerona / Girona)" align="0.0"/>
 
14
                    <newline/>
 
15
                    <separator col="4" colspan="4" string="Add city and state information associated to the zip codes for all the Spanish cities"/>
 
16
                    <field name="city_info" on_change="onchange_city_info(city_info, city_module)"/>
 
17
                    <label colspan="2" string="This allows to fill automatically the city and states fields of partner and contact forms from the zip code." align="0.0"/>
 
18
                    <field name="city_info_recover" attrs="{'readonly':[('city_info','=','no'),('city_module','=','uninstalled')]}"/>
 
19
                    <label colspan="2" string="If the city module has been installed, recover the location data there was in the partner addresses before installing it." align="0.0"/>
 
20
                    <field name="city_module" invisible="1"/>
 
21
                    <newline/>
 
22
                    <label colspan="4" string="Warning! Adding more than 15000 zip codes can take several minutes and it will be done in a background process."/>
 
23
                    <separator string="" colspan="4"/>
 
24
                    <label string="" colspan="2"/>
 
25
                    <group col="2" colspan="2">
 
26
                        <button icon="gtk-cancel" name="action_cancel" string="Skip" type="object" special="cancel"/>
 
27
                        <button icon="gtk-ok" name="action_set" string="Create" type="object"/>
 
28
                    </group>
 
29
                </form>
 
30
            </field>
 
31
        </record>
 
32
 
 
33
        <record id="action_config_toponyms_es_form" model="ir.actions.act_window">
 
34
            <field name="name">Spanish toponyms configuration</field>
 
35
            <field name="type">ir.actions.act_window</field>
 
36
            <field name="res_model">config.ES.toponyms</field>
 
37
            <field name="view_type">form</field>
 
38
            <field name="view_mode">form</field>
 
39
            <field name="target">new</field>
 
40
        </record>
 
41
 
 
42
        <!-- register on configuration -->
 
43
        <record id="config_wizard_toponyms_es" model="ir.actions.todo">
 
44
            <field name="name">Spanish toponyms configuration</field>
 
45
            <field name="note">You can select the toponym version of the Spanish states and add the Spanish cities associated to the zip codes.</field>
 
46
            <field name="action_id" ref="action_config_toponyms_es_form"/>
 
47
            <field name="sequence">20</field>
 
48
        </record>
 
49
 
 
50
</data>
 
51
</openerp>