MISSING TSHIRT DESIGN
7 |Counter:
MISSING TSHIRT DESIGN
7 ||
8 | Customers with active orders
9 |
10 |
11 |
14 |
15 | |
17 |
| 22 | 23 | | 24 |
| 27 | |
%s
78 |%s
79 | """ % (title, content) 80 | 81 | @api.model 82 | def get_statistics(self): 83 | """ 84 | Returns a dict of statistics about the orders: 85 | 'average_quantity': the average number of t-shirts by order 86 | 'average_time': the average time (in hours) elapsed between the 87 | moment an order is created, and the moment is it sent 88 | 'nb_cancelled_orders': the number of cancelled orders, this month 89 | 'nb_new_orders': the number of new orders, this month 90 | 'total_amount': the total amount of orders, this month 91 | """ 92 | first_day = date.today().replace(day=1).strftime(DEFAULT_SERVER_DATETIME_FORMAT) 93 | last_day = datetime.today().strftime(DEFAULT_SERVER_DATETIME_FORMAT) 94 | this_month_domain = [('create_date', '>=', first_day), ('create_date', '<=', last_day)] 95 | new_this_month_domain = expression.AND([this_month_domain, [('state', '=', 'new')]]) 96 | nb_new_orders = self.search_count(new_this_month_domain) 97 | cancelled_this_month_domain = expression.AND([this_month_domain, [('state', '=', 'cancelled')]]) 98 | nb_cancelled_orders = self.search_count(cancelled_this_month_domain) 99 | total_amount = self.read_group(new_this_month_domain, ['amount'], [])[0]['amount'] 100 | total_quantity = self.read_group(this_month_domain, ['quantity'], [])[0]['quantity'] 101 | nb_orders = self.search_count(this_month_domain) 102 | orders_by_size = self.read_group([['state', '!=', 'cancelled']], [], ['size']) 103 | 104 | return { 105 | 'average_quantity': 0 if not nb_orders else round(total_quantity / nb_orders, 2), 106 | 'average_time': (random.random() * 44) + 4, # simulate a delay between 4 and 48 hours 107 | 'nb_cancelled_orders': nb_cancelled_orders, 108 | 'nb_new_orders': nb_new_orders, 109 | 'orders_by_size': {g['size']: g['quantity'] for g in orders_by_size}, 110 | 'total_amount': total_amount or 0, 111 | } 112 | -------------------------------------------------------------------------------- /exercises_5_custom_kanban_view.md: -------------------------------------------------------------------------------- 1 | # Part 5: Custom Kanban View (hard) 2 | 3 | This is a more complicated project that will showcase some non trivial aspects 4 | of the framework. The goal is to practice composing views, coordinating various 5 | aspects of the UI and doing it in a maintainable way. 6 | 7 | Bafien had the greatest idea ever (after the freeze!): a mix of a Kanban View 8 | and a list view would be perfect for your needs! In a nutshell, he wants a list 9 | of customers on the left of the task kanban view. When you click on a customer 10 | on the left sidebar, the kanban view on the right is filtered to only display orders 11 | linked to that customer. 12 | 13 |  14 | 15 | ## 5.1 Create a new kanban view 16 | 17 | Since we are customizing the kanban view, let us start by extending it and using 18 | our extension in the kanban view for the tshirt orders 19 | 20 | - extend the kanban view 21 | - register it under the `awesome_tshirt.kanbanview_with_customers` 22 | - use it in the `js_class` 23 | 24 | ## 5.2 Create a CustomerList component 25 | 26 | We will need to display a list of customers, so we might as well create the 27 | component. 28 | 29 | - create a `CustomerList` component (which just display a div with some text for now) 30 | - it should have a `selectCustomer` prop 31 | - create a new template extending (xpath) the kanban controller template to add 32 | the `CustomerList` next to the kanban renderer, give it an empty function as `selectCustomer` for now 33 | - subclass the kanban controller to add `CustomerList` in its sub components 34 | - make sure you see your component in the kanban view 35 | 36 |231 | Some quick example text to build on the card title and make up the bulk 232 | of the card's content. 233 |
234 | Go somewhere 235 |Some quick example text...
246 | Go somewhere 247 |