Skip to content

[ADD] estate and awesome dashboard: add estate module for property selling and build awesome_dashboard using owl #813

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

Draft
wants to merge 10 commits into
base: 18.0
Choose a base branch
from

Conversation

hich-odoo
Copy link

  • created Estate module for selling properties, add offers to properties, created invoice when property get sold, added many small features & contrainsts to the app, write test cases for module

  • learnt about owl framework, created simple todo app to get idea of owl structure, components and props and more,
    -created awaesome dashboard using owl js, learnt about services, hook, registery, reactivity etc, implemenmted pie chart using chart JS, get known to LazyLoading component, created dashboard setting for viewing only ticked cards( save inlocalstorage )

hich-odoo added 9 commits May 20, 2025 14:47
fixed issues like 'New line at end of code', trailing whitespace after comma etc
Added few fields in estate property model , apply various attribute to fields.
Add access rights for property model , created 3 tier menu for estate module and
created action for property and also worked on views for Form view , Search view
and List View of model.
…odels

Implemented computed fields & onchange methods for auto completed fields
implemented buttons in property form to perform direct action defined in
models defenation.
…ance

Implemented sql & python constraint in estate app ,
Enhance the view (ui) of app
Override and interfier the base method of CRUD to put more business logic
Established estate account module for connection between invoice and
estate property . Implement  functionality to generate invoice when property
is getting sold. Fix some idantation issue in code.
…p according

As a security perspective , created user(agent) group and manager(admin) group with
different  access to app's modules and feature , created security.xml and
defined rules in it.
Using data folder & xml fields , defined modules data for some pre-installed
data. Add some functionality in that auto accept the pre-installed offers.
Also learned to attach  offers to property using Command.create
… test case

learn and implement about qweb templates , sub-templates , reports
and generates  pdf reports from templates.
Write 2-3 test cases
… using owl

implemented counter component , that passed as slot in parent component card.
build a todo list working app with CRUD oprations.
@robodoo
Copy link

robodoo commented Jun 9, 2025

Pull request status dashboard

@hich-odoo hich-odoo force-pushed the 18.0-training-hich branch from ec968fb to f404231 Compare June 9, 2025 11:16
Copy link

@bit-odoo bit-odoo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@@ -0,0 +1,63 @@
import { registry } from "@web/core/registry";
import { rpc } from "@web/core/network/rpc";
// import { memoize } from "@web/core/utils/functions";

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should not push commented code on PR.

@@ -1,10 +1,28 @@
<?xml version="1.0" encoding="UTF-8" ?>
<?xml version="1.0" encoding="UTF-8"?>

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unnecessary changes.

Comment on lines +73 to +77
@api.depends("garden_area", "living_area")
def _compute_total_area(self):
for prp in self:
prp.total_area = prp.garden_area + prp.living_area

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is good pratice to define function after declaration of all fields.


@api.depends("validity")
def _compute_deadline(self):
for ofr in self:

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

naming convention should be good.

get data from API using rpc and set in reactive varibale.
created generic components and render loop via reactive array .
implemented pie chart to categorized data.
created setting for dashboard to view only selected cards.
@hich-odoo hich-odoo force-pushed the 18.0-training-hich branch from f404231 to 7e9a1a4 Compare June 12, 2025 10:31
@hich-odoo hich-odoo changed the title 18.0 training hich Estate module and Awesome Dashboard using Owl [ADD] estate module and awesome dashboard using owl Jun 13, 2025
@hich-odoo hich-odoo changed the title [ADD] estate module and awesome dashboard using owl [ADD] estate and awesome dashboard: add estate module for property selling and add awesome_dashboard using owl Jun 13, 2025
@hich-odoo hich-odoo changed the title [ADD] estate and awesome dashboard: add estate module for property selling and add awesome_dashboard using owl [ADD] estate and awesome dashboard: add estate module for property selling and build awesome_dashboard using owl Jun 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants