[ADD] estate: started the server framework, completed the coding guidelines, setup guide, and chapter 1#1348
Draft
abkus-odoo wants to merge 22 commits into
Draft
[ADD] estate: started the server framework, completed the coding guidelines, setup guide, and chapter 1#1348abkus-odoo wants to merge 22 commits into
abkus-odoo wants to merge 22 commits into
Conversation
Added the basic structure for the new module by creating the and files.
- Added real_estate module - Completed Chapter 2 exercises - Understood ORM basics and how it works - Began working with Odoo ORM structure
- Created estate.property model - Added all required basic fields - Configured required field attributes - Verified PostgreSQL schema updates using Odoo ORM
- Created ir.model.access.csv for estate.property model - Added read, write, create and delete permissions - Learned how Odoo security works using access rights - Added security file in __manifest__.py - Fixed access warning for estate.property model
- Added estate_property_views.xml with basic act_window action - Connected estate.property model with UI through action - Understood how menu > action >view >model flow works in Odoo - Created views folder and add the estate_property_views.xml file - After adding this file Odoo loads it successfully during module update - Action gets created in the database but nothing shows in UI bcz menu is not added
- Added estate_menu.xml and connected menu with action - Added estate_property_views.xml with list and form views - Learned basic structure of Odoo views and actions - Completed Chapter 5 and understood form/list view concepts - Practiced menu >action >view connection flow
- Added custom search view for estate properties - Implemented search fields for property filtering - Added predefined filters and group by functionality - Practiced and understood search views, filters, domains, and group by concepts from Chapter 6 exercise
- Started Chapter 7 on relational fields - Revised earlier Odoo tutorial chapters - Reviewed models, views, ORM, and field concepts
- Fixed code formatting issues and removed unnecessary whitespace - Cleaned up XML and Python structure for better readability - Started learning relational fields (Many2one) - Began exercises from the chapter on Many2one fields
- Studied Many2one field behavior and relationships - Explored res.partner and res.users models - Started implementing Many2one field exercises in estate module - Improved understanding of relational fields in Odoo
Completed Many2many field exercise for property tags - Added estate.property.tag model estate_property_tag.py - Created views for property tags list and form views - Added menu and action for Property Tags in Estate module
- Completed One2many field exercise, added estate_property_offer model, and implemented its views - Added offer_ids field in estate_property_offer.py
- Started learning computed fields and completed the first exercise - Added total_area field in estate_property.py - Computed total_area from living_area and garden_area using a compute method
- Added best_offer field on estate.property - Implemented compute method using mapped() to determine highest offer price - Updated dependencies on offer_ids.price for automatic recomputation
- Added validity and date_deadline fields to estate.property.offer - Implemented computed date_deadline field with @api.depends - Added inverse method to recalculate validity from deadline date - Added garden onchange in estate.property to auto-set garden area and orientation - Configured default values and field synchronization for offer deadlines
- Added Cancel and Sold actions on estate.property with state transition validation - Prevented cancelled properties from being sold and sold properties from being cancelled using UserError - Added Accept and Refuse actions on estate.property.offer - Implemented offer status updates and corresponding form view buttons with icons
- Added SQL constraints in estate models: - property: expected_price > 0, selling_price >= 0 - offer: price > 0 - tag: UNIQUE(name) - property type: UNIQUE(name
…dget - Added property_ids One2many field in estate.property.type - Implemented inline list view for properties in property type form - Added statusbar widget in estate.property state field - Updated form view to display related properties with limited fields
- Added model ordering for properties, offers, tags, and property types Added sequence field with manual ordering support for property types Configured property type field to disable create/edit from property form Added color field to tags and enabled color picker widget
- Added invisible rules for garden fields and offer buttons - Restricted offer creation based on property state (readonly) - Made list views editable for property, offer and tags - Updated list view fields (optional date_availability, hidden by default) - Added decorations for property and offer states - Set default 'Available' filter and updated living area search domain
|
|
- Added stat button on estate.property.type to open estate.property.offer action using type='action' - Displayed all related offers using offer_ids and offer_count in the view - Implemented navigation from property type to offers list view via smart/stat button - Added domain filter on estate.property.offer action to show only offers linked with active property type (property_type_id = active_id)
Author
|
#1265 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added the initial setup for the estate tutorial module, including the server framework, coding guidelines, setup instructions, and completion of chapter 1. This sets up the base structure for the rest of the Server framework 101 Chapters.