19.0 estate cebul#1371
Open
cezarbulancea wants to merge 19 commits into
Open
Conversation
This the foundation of the module. This part implements the instructions of chapter 2 from server framework 101.
Creating estate_property model as part of chapter 3 - ORM from server framework 101.
Following chapter 3 - model fields from Server Framework 101
Following chapter 3 - common attributes from SF101.
Following chapetr 4 - security from SF101. The access rights define which user/users/group of users can access some data.
First action implemented as on chapter 5 - action from SF101.
Tree is no longer recognized as a valid action view mode keyword so I replaced it with list. Also created a three level menu view as per chapter 5 -menus from SF101.
|
|
Failed linting because of missing new lines at the end of files. Also needed two lines between top level declarations and the actual code. THis changes now.
cezarbulancea
force-pushed
the
19.0-estate-cebul
branch
from
July 22, 2026 14:19
51555ed to
bc296dd
Compare
Finished chapter 5 from the SF101 tutorial.
Finished chapter 6 - basic views from SF101. In the list view we can see some attributes of each property. There is also a form for each property. Also now the user can filter some field, group by postcode and see the available properties.
Implemented the Many2one part from chapter 7 of sf101. Now we have property types and views for them. Any property has another tab as well where we can see the salesman and the buyer of the property.
Implemented Many2many from Chapter 7 of SF101. Now we can assign tags to each property.
Offers under each property as part of the One2Many part from chapter 7 of SF101. And with this chapter 7 ends.
Got to chapter 8 from sf101 and implemented the dependencies and inverse function parts under the computed fields section. Now we total area is computed using garden area and living area, best price of the offers is computed as well and we also compute the available date and the validity of an offer (they affect each other through an inverse function).
Finished Chapter 8 of SF101. Implemented onchange so that whenever garden is ticked, then garden area and orientation are filled by default with some values.
Finished Chapter 9 of the SF101. Now we can mark a property as sold and cancelled and we have errors in place incase a user wants to cancel an already sold property or vice versa. WE can also accept and refuse offers. Once an offer has been accepted then the others are refused, the selling price is set as well as the buyer.
Finished chapter 10 of sf 101. Implemented SQL constraints on the names of the tags and types, offer price, selling price and expected price. Also implemented a Python constraint so that the selling price is at least 90% of the expected price. Also saw a previous mistake where I called self.state even though I was looping over records. Now it's record.state.
Started chapter 11 from sf101. IMplemented a view where under eaxh property type you can see the properties with that type.
continue chapter 11 of sf 101, implemented everuthing in the tutorial till the exercise that says 'use invisible'
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.
My first odoo pr!