@gdpelican I just pushed a new Babble branch full-page-chat-discovery to demonstrate how I’m thinking on how the frontend should work.
I think that, rather than having a completely separate view, the chat stream should exist as a sub-route of Discovery, taking advantage of the Discovery navigation, rather than using ‘channels’ per se.
Screencast of functionality: http://quick.as/R0YoIav2e
I’ve also added some updates to Admin Chats to allow the selection of categories to create new chat topics in.
As you can see, this has required a few changes, which is why I’ve pushed this to a branch so we can discuss.
Here are some of the salient differences:
-
Client side chat routes are mapped to discovery, and follow the pattern of the build-category-route component to pull the appropriate Babble topic and render the appropriate templates in the Discovery outlets. The individual routes are built in this initializer (copied from the tagging plugin).
-
Chat admin gets a custom category dropdown to allow new babble topics to be created in different categories
-
I’ve added in the ‘chat’ topic archetype, because I think this makes it easier for us to link chat topics to categories, using the archetype to differentiate them, rather than the Babble category.
Concerning your remaining todos, ‘6’ and ‘7’ should be covered if we go with my suggested approach. I’ll start tackling ‘5’ (as it will be the same regardless of what approach we take) on the weekend.
Let’s finish off this structural question and your to dos first, then we can see if anything needs to be done with rate limiting and other limits. We can probably just copy these from Quick Messages.