-
Notifications
You must be signed in to change notification settings - Fork 2.8k
19.0 tutorials pkhu #1106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: 19.0
Are you sure you want to change the base?
19.0 tutorials pkhu #1106
Conversation
- Architecture Overview - A New application - Models And Basic Fields - Security - A Brief Introduction - Finally, Some UI To Play With
- Covered Odoo architecture concepts - Initialized a new application - Implemented core models and fields - Added basic security configuration - Created simple UI views to interact with data
- Created custom XML views (list and form) for estate.property model - Defined logical field arrangement instead of defaults - Enabled searching across multiple fields - Added postcode-based filter - Added group by for record status: New and Offer Received
- Added new models for property type, tags, and offers - Added many2one fields for property type, buyer and salesperson - Added many2many relation for property tags with appropriate widget - Implemented one2many relation for property offers - Updated views and menus accordingly
mash-odoo
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @pkhu-odoo,
Good work so far for the new module..
Please check out my comments and apply the suggestions.
| @@ -0,0 +1,114 @@ | |||
| <?xml version='1.0' encoding='UTF-8' ?> | |||
| <odoo> | |||
| <data> | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think the <data> tag changes anything functionally here, or would it behave the same without it?
- Implemented computed fields (total area, best offer, Deadline date) - Added inverse methods for validity - Created onchange to auto-update garden area and orientation
- Added action buttons (Cancel, Sell, Accept, Refuse) linked to model methods - Implemented state transitions for properties and offers via actions - Automatically set selling price and buyer on offer acceptance - Added restrictions (e.g., prevent selling canceled properties) - Added SQL constraints for positive prices, unique property names, etc. - Implemented Python constraints for selling price
- Removed trailing white space - Fixed indentation to follow 4-space rule - Corrected extra spaces after keywords and parentheses - Resolved over-indentation warnings
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello,
Great work on the PR and implementations.
Here are some few questions and suggestions..
- Added inline property lists in property type view. - Applied widgets (statusbar, color tags) for better UI. - Set default list ordering with _order attributes. - Added conditional visibility and readonly attributes in views. - Enhanced search defaults and filter behavior. - Added a smart button in the property type form view to access related property offers.
0a308c1 to
fc117a5
Compare
- Created maintenance request model linked to properties - Added workflow states: new, approved, done - Added validation for approved maintenance cost - Computed total maintenance cost per property - Restricted selling properties with unfinished maintenance
fc117a5 to
d8e37e7
Compare

No description provided.