is it possible to always use nicegui's widgets in slot directly?

[retsyo]

This is a following thought of this discussion

@falkoschindler shows a general way to add slot, i.e, using quasar code

tabRange.add_slot('body-cell-percent', r'''
    <q-td :props="props">
        <q-linear-progress size="1rem" :value="props.value" color="red" track-color="green">
            <div class="absolute-center text-black text-sm">
                {{ (props.value * 100).toFixed(0) }}%
            </div>
        </q-linear-progress>
    </q-td>
''')

which is some difficult to write for user, like me, knows little about VUE/Quasar.

Since nicegui has supplied ui.linear_progress(well, based on q-linear-progress), what comes into my mind naturally is

with tabRange.add_slot('body-cell-percent'):
    ui.linear_progress().props('value=0.1').classes('w-full')

but as we may find that, we can't sets every cell's value to every ui.linear_progress.

So any way to move more quasar code out of projects based on nicegui by using pre-defined widgets? Thanks

[falkoschindler]

Let me refer to a comment in a previous discussion #1138 (comment) which still holds today:

These scoped slots are certainly one of the most complicated things NiceGUI has to offer. I'm thinking about ways to simplify it for some time now, but so far I don't see how. Since these elements q-tr, q-td, ... don't live in Python (they are no NiceGUI elements), we would need something new to define template objects. It would have to allow for all possible HTML tags and attributes. And we need the ability access row props and to handle and forward events. It all needs to be nice and simple enough to justify the implementation and learning this new API instead of learning to write Vue templates. Pretty complicated, but maybe not impossible. 🙂

So I'm still pretty clueless how we could improve the slot API. But I'm open for any suggestions.