Part of what I love about the new widget structure is being able to reuse code in multiple places. But I’ve run into an issue when attempting to do this for the voting plugin . I use widgets heavily on the page for an individual topic. It makes the build process much smoother. But I want to take the…

Unfortunately there just is no way to do this right now. Widgets are fairly incompatible with raw handlebars. You can put a widget outside of the raw handlebars fairly easily if you can get away with that.

Makes sense, Robin. It gets tricky using a combination of widget decoration and plugin outlets. Since there’s no intent to port the topic list away from the raw templates (and I don’t disagree with this decision), it makes it difficult to work with the existing plugin outlets within the topic-list-i…

Scratch that. It doesn’t work to add a plugin outlet there. The tr tag is created within the component extension . You’d have to prepend the raw template by reopening the component and somehow injecting html, which I’m pretty sure can’t be done. So for now, I have no solution to this. I may need to …

Can you explain what you’re trying to do? It’s not clear to me why you’d want to change that tr tag or decorate around it?

The voting plugin makes heavy use of widgets to do pretty much everything. All of the actions to increment and decrement votes for a topic and the user as well as the UI displayed to make it all work are widgets. And I still think that’s the best way to build it as it’s extremely flexible and clear …

@eviltrout It follows from this that you can’t render a component (any component) in a raw template right? I’m trying to render the share-popup component in a topic list item. I could just re-create the functionality, but I’d prefer not to. @david Any ideas?

[imagen] angus: It follow from this that you can’t render a component (any component) in a raw template right? I think you are correct there, based on all of the raw templates in core. [imagen] angus: @david Any ideas? I’m not sure of the exact history/reasons/implementation for raw t…

[imagen] A tour of how the Widget (Virtual DOM) code in Discourse works You can’t embed a widget in a raw template. But don’t worry, we aren’t going to convert the topic list over. The gains over raw rendering for that part are negligible. Not a team member, but through my conversations with R…

Yes, any non-ember rendering paths were purely done for performance reasons. The code is almost always harder to follow or has major limitations (values not updating) but performs much better. It was mainly done because of android performance .

Mounting widget in raw template?

Desarrollador

joebuhlig (Joe Buhlig) 15 Noviembre, 2018 14:32 9

Not a team member, but through my conversations with Robin on this I had the understanding that those raw templates render significantly quicker overall. It has to do with the sheer number of times the template is reused.

Tema		Respuestas	Vistas
Making custom changes to a raw template Development	6	665	26 Agosto 2023
A tour of how the Widget (Virtual DOM) code in Discourse works Development	75	29150	10 Julio 2023
Render a component within a Widget. (Using select-kit components within plugin code) Development	31	3528	6 Marzo 2024
Unable to replace topic-list-item.raw.hbs / topic-list-item.hbr on mobile Development	10	1481	13 Febrero 2020
Render Component in Widget Development	1	392	27 Junio 2023

Mounting widget in raw template?

Temas relacionados