Thank you for sharing. I enjoyed watching this. I understand for the most part. However, I would have liked to see a follow up to this to demonstrate what the first module does and how (and where) to in fact code the part in terms of what it does.
Thank you for your feedback! I’m glad you enjoyed the video and found it helpful. You’re absolutely right; the next logical step after creating a custom module is demonstrating its functionality and showcasing where and how to code the features that make it work. I’m planning a follow-up video that will dive deeper into: Understanding the structure: Explaining how the files like models.py, views.xml, and security/ir.model.access.csv work together. Adding functionality: Writing actual Python code in the models.py file to define the module's behavior and logic. Defining views: Showing how to create form, tree, and kanban views in XML. Testing the module: Demonstrating how to use the new module in Odoo once it’s installed and configured. Stay tuned, and I’ll be sure to make the follow-up video informative and practical so you can see exactly how a custom module comes to life in Odoo 18. If you have any specific features you’d like to see in the demo, let me know, and I’ll try to include them! 😊
Module Naming Conventions Lowercase with underscores: Use lowercase letters and separate words with underscores (_). Example: custom_sales_module, project_task_extension. Descriptive and concise: Choose names that clearly describe the module's purpose without being overly long. Example: Use employee_management instead of custom_module_for_employee_records. Avoid generic names: Avoid names like module1, test, or custom as they don't indicate the module's purpose. File Naming Conventions Structured organization: Place models in models/. XML views in views/. Static files (like CSS, JS, and images) in static/. Descriptive filenames: Python files: Use names that represent the model or logic, e.g., employee.py, sale_order_extension.py. XML files: Name files based on the feature, e.g., employee_views.xml, sale_order_views.xml. Lowercase with underscores: Similar to module names, use lowercase letters and underscores for filenames. Example: product_template_extension.py, res_partner_views.xml.
this is so difficult for me to understand and to follow along... can you recommend another apps with minimal customization? Thank you so much to your responds.😁
Hi, I'm here because I am interested in creating custom modules in Odoo, I have watched your installation guide for Odoo 18 on Windows, and it worked. Do you recommend developing it on windows or should I change to Linux?
Hi, thank you for watching my video! I'm glad the installation guide for Odoo 18 on Windows worked for you. 😊 When it comes to developing custom modules in Odoo, both Windows and Linux have their pros and cons. Here’s a quick breakdown: Developing on Windows: Pros: If you're already comfortable with Windows, there's no steep learning curve. Windows has plenty of tools like Visual Studio Code, which works seamlessly with Odoo development. You can use tools like WSL (Windows Subsystem for Linux) to get a Linux-like experience while staying on Windows. Cons: Some Odoo dependencies and commands (e.g., pip, wkhtmltopdf) may require extra configuration or may not work as smoothly as on Linux. Community support for Odoo development on Windows is relatively smaller, as most developers use Linux. Developing on Linux: Pros: Odoo was originally built for Linux, so it runs more natively and efficiently. Easier to install dependencies and resolve issues, as most tutorials and guides are written for Linux. A smoother experience with tools like PostgreSQL, Python, and Odoo services. More flexibility in setting up Docker containers for Odoo. Cons: If you're new to Linux, there’s a learning curve (though it's worth it in the long run!). If you rely on specific Windows-only tools, you may need to adapt to Linux alternatives.
hi, if you want to use multiple odoo versions then you need to have your launch.json like this where project 1 first and then project 2 { "name": "PythFon:project_1", "type": "debugpy", "request": "launch", "stopOnEntry": false, "python": "/home/farooq/workspace/odoo17/odoo17-venv/bin/python3.12", "console": "integratedTerminal", "program": "${workspaceRoot}/odoo17/odoo-bin", "args": [ "--config=/home/farooq/workspace/odoo17/project_1.conf", "--limit-time-real", "1000",
you need to install multiple odoo versions which you want to use and conf file will be like this [options] db_user = farooq addons_path = /home/farooq/workspace/odoo16/addons, /home/farooq/workspace/odoo16/enterprise, /home/farooq/workspace_project/odoo16/project_1 xmlrpc_port = 8015 dbfilter = admin_passwd = ????????????????????????
@@odooistic thank you very much, I will definitely try this with some modifications to meet own environment , path etc. where the file launch.json will be ? and can u please add the sample conf file? this will help too. This is a humble request to please make a tutorial Video which guide us Step-by-step to setup multiple versions of Odoo and configure VSCode etc. will all its requirements and configurations, this will help a lot. thank you again.
Hello, thank you for the interesting video! I have a question: I want to create a module for Odoo, and I need to set up Odoo on my computer or a virtual environment to test the modules. Can I do this by simply installing the program, or do I need to download the repository from GitHub for a full setup and module testing?
yes you can install odoo in your personal computer and then in launch.json file you can give your custom addons folder path and straight away start working with custom modules and do any kind of customization you like. you can watch my video to how to install and work in vscode one and then you can create custom addons. let me know if you need more help thanks
Thank you for sharing.
I enjoyed watching this. I understand for the most part. However, I would have liked to see a follow up to this to demonstrate what the first module does and how (and where)
to in fact code the part in terms of what it does.
Thank you for your feedback! I’m glad you enjoyed the video and found it helpful.
You’re absolutely right; the next logical step after creating a custom module is demonstrating its functionality and showcasing where and how to code the features that make it work.
I’m planning a follow-up video that will dive deeper into:
Understanding the structure: Explaining how the files like models.py, views.xml, and security/ir.model.access.csv work together.
Adding functionality: Writing actual Python code in the models.py file to define the module's behavior and logic.
Defining views: Showing how to create form, tree, and kanban views in XML.
Testing the module: Demonstrating how to use the new module in Odoo once it’s installed and configured.
Stay tuned, and I’ll be sure to make the follow-up video informative and practical so you can see exactly how a custom module comes to life in Odoo 18. If you have any specific features you’d like to see in the demo, let me know, and I’ll try to include them! 😊
Thanks for the instruction. Should we have a name convention for naming a module and its files?
Module Naming Conventions
Lowercase with underscores: Use lowercase letters and separate words with underscores (_).
Example: custom_sales_module, project_task_extension.
Descriptive and concise: Choose names that clearly describe the module's purpose without being overly long.
Example: Use employee_management instead of custom_module_for_employee_records.
Avoid generic names: Avoid names like module1, test, or custom as they don't indicate the module's purpose. File Naming Conventions
Structured organization:
Place models in models/.
XML views in views/.
Static files (like CSS, JS, and images) in static/.
Descriptive filenames:
Python files: Use names that represent the model or logic, e.g., employee.py, sale_order_extension.py.
XML files: Name files based on the feature, e.g., employee_views.xml, sale_order_views.xml.
Lowercase with underscores: Similar to module names, use lowercase letters and underscores for filenames.
Example: product_template_extension.py, res_partner_views.xml.
this is so difficult for me to understand and to follow along... can you recommend another apps with minimal customization? Thank you so much to your responds.😁
Sure I will upload some more detailed videos and try to explain in more easier way
Please make some more modules with detailed models and more complex form views in future videos.
sure i will add soon , in the meantime watch this video th-cam.com/video/akpdQy9LvZA/w-d-xo.html
Hi, I'm here because I am interested in creating custom modules in Odoo, I have watched your installation guide for Odoo 18 on Windows, and it worked. Do you recommend developing it on windows or should I change to Linux?
Hi, thank you for watching my video! I'm glad the installation guide for Odoo 18 on Windows worked for you. 😊
When it comes to developing custom modules in Odoo, both Windows and Linux have their pros and cons. Here’s a quick breakdown:
Developing on Windows:
Pros:
If you're already comfortable with Windows, there's no steep learning curve.
Windows has plenty of tools like Visual Studio Code, which works seamlessly with Odoo development.
You can use tools like WSL (Windows Subsystem for Linux) to get a Linux-like experience while staying on Windows.
Cons:
Some Odoo dependencies and commands (e.g., pip, wkhtmltopdf) may require extra configuration or may not work as smoothly as on Linux.
Community support for Odoo development on Windows is relatively smaller, as most developers use Linux.
Developing on Linux:
Pros:
Odoo was originally built for Linux, so it runs more natively and efficiently.
Easier to install dependencies and resolve issues, as most tutorials and guides are written for Linux.
A smoother experience with tools like PostgreSQL, Python, and Odoo services.
More flexibility in setting up Docker containers for Odoo.
Cons:
If you're new to Linux, there’s a learning curve (though it's worth it in the long run!).
If you rely on specific Windows-only tools, you may need to adapt to Linux alternatives.
how i can configure vscode for this and if i am using multiple odoo versions how all can be configure vscode for all? regards
hi, if you want to use multiple odoo versions then you need to have your launch.json like this where project 1 first and then project 2 {
"name": "PythFon:project_1",
"type": "debugpy",
"request": "launch",
"stopOnEntry": false,
"python": "/home/farooq/workspace/odoo17/odoo17-venv/bin/python3.12",
"console": "integratedTerminal",
"program": "${workspaceRoot}/odoo17/odoo-bin",
"args": [
"--config=/home/farooq/workspace/odoo17/project_1.conf",
"--limit-time-real",
"1000",
],
"cwd": "${workspaceRoot}",
"env": {},
"envFile": "${workspaceRoot}/.env",
},
{
"name": "PythFon:project_2",
"type": "debugpy",
"request": "launch",
"stopOnEntry": false,
"python": "/home/farooq/workspace/odoo16/odoo16-venv/bin/python3",
"console": "integratedTerminal",
"program": "${workspaceRoot}/odoo16/odoo-bin",
"args": [
"--config=/home/farooq/workspace/odoo17/project_2.conf",
"--limit-time-real",
"1000",
],
"cwd": "${workspaceRoot}",
"env": {},
"envFile": "${workspaceRoot}/.env",
}, and then 2 conf files related to these 2 project1 and project2.
you need to install multiple odoo versions which you want to use and conf file will be like this [options]
db_user = farooq
addons_path = /home/farooq/workspace/odoo16/addons, /home/farooq/workspace/odoo16/enterprise, /home/farooq/workspace_project/odoo16/project_1
xmlrpc_port = 8015
dbfilter =
admin_passwd = ????????????????????????
@@odooistic thanks a bunch for help, i will try these and confirm.
@@odooistic thank you very much, I will definitely try this with some modifications to meet own environment , path etc. where the file launch.json will be ? and can u please add the sample conf file? this will help too. This is a humble request to please make a tutorial Video which guide us Step-by-step to setup multiple versions of Odoo and configure VSCode etc. will all its requirements and configurations, this will help a lot. thank you again.
Hello, thank you for the interesting video!
I have a question: I want to create a module for Odoo, and I need to set up Odoo on my computer or a virtual environment to test the modules.
Can I do this by simply installing the program, or do I need to download the repository from GitHub for a full setup and module testing?
yes you can install odoo in your personal computer and then in launch.json file you can give your custom addons folder path and straight away start working with custom modules and do any kind of customization you like. you can watch my video to how to install and work in vscode one and then you can create custom addons. let me know if you need more help thanks
By the way, I couldn't understand security and views file.........but copy-paste worked fine.
ok watch this video and let me know th-cam.com/video/akpdQy9LvZA/w-d-xo.html