← Back to team overview

openerp-community team mailing list archive

Re: Development Module Flow

 

Any changes you make to python won't be 'seen' by the server until it restarts.

 

You can use a command-line argument: -u <your_module> so that your module is updated (XML re-loaded, database structure
changed, etc) happens automatically.


Follow this procedure:

1. Run the server

2. Install your module

3. Test your module

4. Make your changes to the PY and XML files

5. Stop the server

6. Start the server with the -u option

 

Repeat the Test, Change, Stop, Start process


Ray.

 

From: Openerp-community [mailto:openerp-community-bounces+rcarnes=ursainfosystems.com@xxxxxxxxxxxxxxxxxxx] On Behalf Of
David
Sent: Thursday, October 31, 2013 12:34 PM
To: openerp-community@xxxxxxxxxxxxxxxxxxx
Subject: [Openerp-community] Development Module Flow

 

I'm starting to spend more time working on building a simple module to get the change of things. I'm keeping it very
simple now.
OpenERP(7) is running on a linux box. I'm on a Windows machine, and SSHing into the Linux box to make my changes to the
files with
a text editor in the shell.

I have the directory where I have my module mapped to in "openerp-server.conf", I can see my module listed in "Installed
Modules" list.  So that's not
a problem.
Now the issue I have is making changes to my *.py and *.xml. I see that they aren't updated in the new menu I created, I
have found that I need to
always go back to the Settings and UPDATE my model. But issues I have is that sometimes that doesn't update my changes
and it's also time consuming going back and
forth to force the update. And sometimes the changes don't even appear.

Now the question is, is this the correct procedure? Is there a proper way to make changes to the module and see them in
OE in a quicker manner? Do I have to flush a cache
to see my changes even though I have forced a UPDATE they don't appear in my new menu.


Follow ups

References