| | 1 | [[BackLinksMenu]] |
| | 2 | |
| | 3 | [[TicketQuery(summary=TASK_NAME_HERE, format=table, col=summary|owner|status|type|component|priority|effort|importance, rows=description|analysis_owners|analysis_reviewers|analysis_score|design_owners|design_reviewers|design_score|implementation_owners|implementation_reviewers|implementation_score|test_owners|test_reviewers|test_score|)]] |
| | 4 | |
| | 5 | = Analysis = |
| | 6 | == Overview == |
| | 7 | The goal of this group of tasks is to improve the performance of the ProLib. [[BR]] |
| | 8 | This revision of the task is responsible for improving the performance of ProLists. |
| | 9 | |
| | 10 | == Task requirements == |
| | 11 | There are too many notifications for updates when using a ProList. [[BR]] |
| | 12 | |
| | 13 | Currently, when an AutoProperty depends on a ProList, it gets recomputed every time anything about the ProList changes - its size, its elements, etc. In certain cases, though, an AutoProperty might depend only on the size of a given ProList and thus in doesn't need to get recomputed when some elements in the ProList change their value, because this operation doesn't change the size of the list. [[BR]] |
| | 14 | |
| | 15 | Another case is when you deal with skins. Skins are basically maps between keys and values. At a certain time an AutoProperty might be interested to monitor only the list of all pairs of keys and values which have the key "meddle". So if this list remains the same while the whole ProList which contains it changes, this AutoProperty shouldn't get recomputed. [[BR]] |
| | 16 | |
| | 17 | Devise and implement a concept how to deal with such problems. |
| | 18 | |
| | 19 | == Task result == |
| | 20 | ^(List the end product of the task (for example "Source code", "Wiki page", etc.))^ |
| | 21 | |
| | 22 | == Implementation idea == |
| | 23 | ^(Provide some rough implementation idea(s).)^ |
| | 24 | |
| | 25 | == Related == |
| | 26 | ^(Add links to related tasks that could be useful or helpful.)^ |
| | 27 | |
| | 28 | == How to demo == |
| | 29 | ^(Provide instructions for demonstration of the task.)^ |
| | 30 | |
| | 31 | = Design = |
| | 32 | |
| | 33 | = Implementation = |
| | 34 | ^(Describe and link the implementation results here (from the wiki or the repository).)^ |
| | 35 | |
| | 36 | = Testing = |
| | 37 | ^(Place the testing results here.)^ |
| | 38 | |
| | 39 | = Comments = |
| | 40 | ^(Write comments for this or later revisions here.) |
