Right now, the list task activity is using very naive implementation to populate the tasks in a double loop (but with a few improvements) which can get slow with time.
This problem can be avoided by making some changes in the database and soon one of us will have to do that. (Probably after mid sem demo)
Right now, the list task activity is using very naive implementation to populate the tasks in a double loop (but with a few improvements) which can get slow with time.
This problem can be avoided by making some changes in the database and soon one of us will have to do that. (Probably after mid sem demo)