adding new chatbubbles based on user-interaction

[schwrrring]

adding new chatbubbles based on user-interaction

[alastaircoote]

Hello!

My apologies for taking so long to reply to this. And my apologies for the state of the code!

You're definitely on the right path. You will want to insert a new ChatBubbleProperties into the items array of the Script. The best way to do that will probably be a function in Frame, as it contains the script in its state. If you want to avoid having to add the function to the entire chain of components, you might want to look into React context:

https://reactjs.org/docs/context.html

That would allow you to send the function into a context in <Frame/>, then extract it back out again inside <ChatBubble/>.

Is that any help?

[schwrrring]

Hey Alastair! Thank you very much for your response! Yes, your mail is immensely helpful. Nice to hear, that I was on the right path :) For now I worked around the task by making the Chatbubble itself transform after the user made a choice (clicking a button). But if we stick to the idea to play around with podmod - and I hope we will, at least for a bit, the topic will come up again. Maybe it is nice to hear for you that your work had quite some influence here, after a workshop week during which we explored new storytelling formats for mobile, I came across the guardian lab and ended up reading all your great posts and talks now we try to implement your learnings here. Very very helpful and inspiring, thank You! Playing around with podmod is lots of fun and triggered some ideas, we really would love to keep working on, to test the concepts we would love to stick to podmod and tweak it here and there, but right now I guess I reached a point where I am no more sure, if it makes sense to stick to the code. The issue I faced, first seemed to be a small thing, adding a textarea into a chat bubble to gather userFeedback. Now I think it could quite a big challenge - it would be great if you could prove me wrong! What is the problem? The Dummy-Scroller covers the text-area and makes it impossible to enter Text. I read your text about the performance-scroll-view and get one thing: It is beyond my skills to change the performance-scroll-view. :) Do you think there is an easy way to solve the textarea issue - even it is quite a really dirty hack, it is only to get the prototype working and test the concept. If it is the only way out, I thought about implementing something like the image behaviour, which opens div outside of the scrollview. Do you think that would be the best way? Or is there an easy alternative I didn't see? In case you don't find the time to think about it, that is of cause completely understandable! Thank you very much and all the best from Hamburg! Malte

…

On Tue, 24 Jul 2018 at 00:14, Alastair Coote ***@***.***> wrote: Hello! My apologies for taking so long to reply to this. And my apologies for the state of the code! You're definitely on the right path. You will want to insert a new ChatBubbleProperties into the items array <https://github.com/gdnmobilelab/podmod/blob/master/src/interfaces/script.tsx#L34> of the Script. The best way to do that will probably be a function in Frame, as it contains the script in its state. If you want to avoid having to add the function to the entire chain of components, you might want to look into React context: https://reactjs.org/docs/context.html That would allow you to send the function into a context in <Frame/>, then extract it back out again inside <ChatBubble/>. Is that any help? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKsaSEECBEJetH_e-KXzY4UzsfqsIZVrks5uJkrZgaJpZM4VQ96E> .

-- Mobil: [phone] Mail: malte.hildebrand@g <[email protected]>mail.com Malte Hildebrand Bilserstr. 53 22335 Hamburg

[alastaircoote]

I am not surprised the performance-scroll-view is causing problems there, unfortunately! It does all sorts of tricks that make it a lot less flexible. My best suggestion for an alternative is what you've already mentioned - including a button in the chat bubble that opens the textarea in a separate div, on top of all the other elements. It wouldn't be anywhere near as nice a UI presentation, but it would get around all of the scrolling issues.

Depending in what direction you go with your ideas it might make sense to abandon the podmod code eventually. Although I tried to make it as flexible as I could, we were also approaching the end of the mobile lab, so parts of it were more rushed than I would have liked. If it served as a good place to test out some ideas before starting something new then I will consider that a win!

It's really great to hear that the mobile lab's work has continued to make an impact, a lot of the time we were working on these things without knowing if anyone was paying attention! I can't promise I will be able to give in-depth answers, but if there are any other things you'd like to know about then let me know!

[schwrrring]

Hey Alastair! it is super kind of you to answer! Thank You!! For now, I did some really really bad thing to your code :) But however, for testing it might be sufficient. Somehow if I change the z-index of the div that is rendered by the scroll-item-component it works. And here comes that dirty, very rulebook reactish move ;) [image: image.png] magic. Thanks again for your very kind offer! Have a great day! Malte

…

On Wed, 25 Jul 2018 at 17:09, Alastair Coote ***@***.***> wrote: I am not surprised the performance-scroll-view is causing problems there, unfortunately! It does all sorts of tricks that make it a lot less flexible. My best suggestion for an alternative is what you've already mentioned - including a button in the chat bubble that opens the textarea in a separate div, on top of all the other elements. It wouldn't be anywhere near as nice a UI presentation, but it would get around all of the scrolling issues. Depending in what direction you go with your ideas it might make sense to abandon the podmod code eventually. Although I tried to make it as flexible as I could, we were also approaching the end of the mobile lab, so parts of it were more rushed than I would have liked. If it served as a good place to test out some ideas before starting something new then I will consider that a win! It's really great to hear that the mobile lab's work has continued to make an impact, a lot of the time we were working on these things without knowing if anyone was paying attention! I can't promise I will be able to give in-depth answers, but if there are any other things you'd like to know about then let me know! — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AKsaSC0k0kQzQzF04aWW_ABcjxUHdrS9ks5uKIo4gaJpZM4VQ96E> .

-- Mobil: [phone] Mail: malte.hildebrand@g <[email protected]>mail.com Malte Hildebrand Bilserstr. 53 22335 Hamburg

[schwrrring]

Hey Alastair! I am making progress here, and even though you are not so happy with the code, it seems, for me it is an awesome way to learn something by looking at your stuff :) Right now I would like to get another stone out of the way and would like to ask you for a word of advise: depending on user input the size of a chat bubble changes - but however the next bubble doesn't realise the change and hence it covers the bubble that has changed in size. Is there a "of cause..."-thought poppin into your head right now? So far I am not sure, which function to call in order to update the positions of the bubbles. I hope this mail finds you well. All the best Malte On Wed, 25 Jul 2018 at 18:15, Malte Hildebrand <[email protected]> wrote:

…

Hey Alastair! it is super kind of you to answer! Thank You!! For now, I did some really really bad thing to your code :) But however, for testing it might be sufficient. Somehow if I change the z-index of the div that is rendered by the scroll-item-component it works. And here comes that dirty, very rulebook reactish move ;) [image: image.png] magic. Thanks again for your very kind offer! Have a great day! Malte On Wed, 25 Jul 2018 at 17:09, Alastair Coote ***@***.***> wrote: > I am not surprised the performance-scroll-view is causing problems there, > unfortunately! It does all sorts of tricks that make it a lot less > flexible. My best suggestion for an alternative is what you've already > mentioned - including a button in the chat bubble that opens the textarea > in a separate div, on top of all the other elements. It wouldn't be > anywhere near as nice a UI presentation, but it would get around all of the > scrolling issues. > > Depending in what direction you go with your ideas it might make sense to > abandon the podmod code eventually. Although I tried to make it as flexible > as I could, we were also approaching the end of the mobile lab, so parts of > it were more rushed than I would have liked. If it served as a good place > to test out some ideas before starting something new then I will consider > that a win! > > It's really great to hear that the mobile lab's work has continued to > make an impact, a lot of the time we were working on these things without > knowing if anyone was paying attention! I can't promise I will be able to > give in-depth answers, but if there are any other things you'd like to know > about then let me know! > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#1 (comment)>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AKsaSC0k0kQzQzF04aWW_ABcjxUHdrS9ks5uKIo4gaJpZM4VQ96E> > . > -- Mobil: [phone] Mail: ***@***.*** ***@***.***>mail.com Malte Hildebrand Bilserstr. 53 22335 Hamburg

-- Mobil: [phone] Mail: malte.hildebrand@g <[email protected]>mail.com Malte Hildebrand Bilserstr. 53 22335 Hamburg