I want to customize webchat send input field, by adding label tag above the input field and remove the placeholder and add send text instead of icon using react.
Currently, I have tweaked using javascript(Es6)
Unfortunately, at this time, there is no built in feature of Web Chat that allows the developer to alter the send box (beyond hiding / not hiding it). If you feel strongly about this as a feature others could benefit from, I would suggest you present it as a feature request on the BotFramework-WebChat repo. You can do so here.
The method you are using (i.e. altering the DOM directly) is the correct method.
Hope of help!
Related
I'm wondering if it's possible to configure field edtiable state (and other associated view layout information) via code, rather than via the Strapi Web UI?
e.g. In Strapi you can customise a view, and these settings are written to the core_store database table into a json object keyed as plugin_content_manager_configuration_content_types::application::video.video
When making this change via the web UI, no code is changed on the filesystem. So it's all in the database.
We're hoping to configure some of these settings via code, especially controlling if a field is editable or not.
Is this possible?
When the app starts the browser makes a request to http://localhost:1337/content-manager/content-types/application::video.video (for the video content type) and this returns some metadatas such as:
I've poked around in the node_modules/strapi-plugin-content-manager/ to try see if there's a way to modify this data but I'm in over my head.
Any pointers appreciated, thanks!
Iām not sure what you need, but here are some links to strapi documentation, which gives examples to change default behavior.
Content editor:
https://strapi.io/documentation/3.0.0-beta.x/guides/slug.html#configure-the-layout-for-the-content-editor
https://strapi.io/documentation/3.0.0-beta.x/guides/custom-admin.html#introduction
Custom data response:
https://strapi.io/documentation/3.0.0-beta.x/guides/custom-data-response.html
I believe you can customize strapi a lot, it just might take some time to understand the system.
I am using bot framework web chat and I have an adaptive card with just one input field.Is it possible to handle auto complete as user's type in the card's input field ?
Example : Input field is for city.As user type the first 3 character of city i want to provide the suggestions and users can pick from it.
I found the below link in github but its about auto complete for chat typing area not for cards.
https://github.com/Microsoft/BotFramework-WebChat/issues/476
To the best of my knowledge this is not possible today in v1.0 of the Adaptive Card specification. The cards are rendered without any control over their behavior except for the built-in actions: Submit, OpenURL, ShowCard.
Adaptive Cards are very much like HTML 2.0... if you were [un]fortunate to have lived through those days. š The spec defines all the possible behaviors and the agent/host is considered compliant with a version of the spec when they implement those behaviors and no additional behaviors are supported via any kind of extensibility.
It may require a little work and some react knowledge, but you should be able to create a custom AdaptiveCard Renderer using WebChat's attachmentMiddleware. In your custom renderer, you should be able to add an input field with your autocomplete logic. For more details on how to create a custom AdaptiveCard Renderer, take a look at this WebChat Example that creates a custom GitHub Card.
Hope this helps!
Is it possible to add some code or something else to make it possible that whenever I type a hashtag followed by a number that this will be replaced by a url?
My requirement is whenever some developer mention a ticket number like #1234 in his chat post into a channel I want to make this clickable and directly opens a url like myticketsystem.com?id=1234.
If I understand correctly, you're looking to implement an auto-linking similar to how GitHub handles things like Fixes issue #xxxx? It isn't possible to implement this in Teams today, it isn't possible to inject your own logic into the composition rendering pipeline.
What you could do however is build a Compose Extension. This wouldn't replicate the GitHub experience but it would certainty make it easier to insert links to tickets into the compose editor. It could also be a more powerful tool, allowing users to search the ticketing system rather than having to know the number before writing the post.
Since facebook is deprecating fbml, could someone point me in the direction of what would be the replacement for the multi-friend-selector? We use this to allow facebook users to send invitations to their friends to let them know about our site.
You might want to have a look at Facebook's Send Dialog and Request Dialog.
There also exist two JQuery Plugins you might be interested in. The first is an autocomplete plugin which includes a Facebook theme and the second is a full friend selector plugin. I already used both on production:
http://loopj.com/jquery-tokeninput/demo.html (see the facebook theme)
http://labs.thesedays.com/blog/2011/06/20/the-missing-facebook-interface-component-for-friend-selection/
So I dont know what it is called but I am looking for a way to box in the user entered email addresses like they do in hotmail, where any valid email is boxed into that rectangle locked email once it is validated in real time? Also in hotmail they allow you to remove it by clicking the X and edit it by clicking the edit icon. I want to add more features also appart from edit and delete, so I guess I use AJAX for this? I dont know the term for this so not sure how to search for sample code and design patters for this. Any idea on what this is called or sample links with different design patterns?
You mean a facebook-like autocompletion? It uses AJAX (Javascript libraries: Prototype / Scriptacoulous).
Maybe this library is not perfectly suited to your use case, but you definitely need Javascript to do it as soon as the user enters it, but not necessarily AJAX - via javascript you can create input-hidden fields that will get submitted with the rest of the form.