Introduce topic list management system [DO NOT MERGE] #106
Conversation
…logs to depend on it.
…it of test code, incomplete documentation, and no tests. However, it does introduce a new way to handle recycler view binding, and demonstrates end-to-end integration with Oppia's backend. This PR will actually be split up into several to demonstrate how we should approach end-to-end projects like this in pieces.
|
/cc @veena14cs and @nikitamarysolomanpvt since this may affect how the recycler view is being set up for content card list. I'd like to extract the adapter out of this and move it to its own PR to get that in earlier. /cc @vinitamurthi for how this hooks up the backend controller to a custom data provider with the proto-based cache in the middle for caching. I started off trying to create a generic solution, but decided that we don't need it yet since there are few data stores we actually need (see #103 for a more exhaustive braindump). |
|
I am not clear on how I can bind multiple views to the adapter. In Content
card list we have feedback and learner's interaction which needs to display
like a chat.
So I have created 2 different views to show interactions on left and right
of the view.
Could you please suggest me how I can do it using this recycler view.
…On Mon, Sep 16, 2019 at 12:18 PM Ben Henning ***@***.***> wrote:
/cc @veena14cs <https://github.com/veena14cs> and @nikitamarysolomanpvt
<https://github.com/nikitamarysolomanpvt> since this may affect how the
recycler view is being set up for content card list. I'd like to extract
the adapter out of this and move it to its own PR to get that in earlier.
/cc @vinitamurthi <https://github.com/vinitamurthi> for how this hooks up
the backend controller to a custom data provider with the proto-based cache
in the middle for caching. I started off trying to create a generic
solution, but decided that we don't need it yet since there are few data
stores we actually need (see #103
<#103> for a more exhaustive
braindump).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#106?email_source=notifications&email_token=AD4LXZG3PBPKW7732XADGBLQJ4T5LA5CNFSM4IW6MFEKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6YHXPA#issuecomment-531659708>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AD4LXZD4R6HUDSPU6MCSHMDQJ4T5LANCNFSM4IW6MFEA>
.
|
|
@veena14cs I'll answer your question in #172. |
|
@BenHenning Is this PR still relevant? |
|
Hi @BenHenning. Due to recent changes in the "develop" branch, this PR now has a merge conflict. Please follow this link if you need help resolving the conflict, so that the PR can be merged. Thanks! |
|
I don't think so--it seems this was split up and finished in multiple pieces (including #176). |
BenHenning
deleted the
introduce-topic-list-management-system-fully-integrated-demo
branch
Initial commit of the topic list management system. This includes a bit of test code, incomplete documentation, and no tests. However, it does introduce a new way to handle recycler view binding, and demonstrates end-to-end integration with Oppia's backend.
This PR will actually be split up into several to demonstrate how we should approach end-to-end projects like this in pieces.