Deeper Quasar Component Support

[jtrip]

Just wondering if anyone has thoughts about implementing more of the features of Quasar's components.

For example I noticed the tooltip component works but doesn't support all the options available in Quasar, like the offset prop, which would be nice for making tooltips appear to the side instead of below.

I could look at opening an issue and working on it, but I am not very familiar with NiceGUI's layer that implements the components.

I would guess it would involve extending the class here:
nicegui/elements/tooltip.py

Maybe a method to look for a offset parameter and implement rendering the parameter in the component attribute. And that could be called from the init method.

[thevinchi]

This is what the .props() method is for.

ui.tooltip('Hello World').props('anchor="center left"')

Check out the docs on this here:
https://nicegui.io/documentation/section_styling_appearance

[falkoschindler]

Thanks for the suggestion, @jtrip! As @thevinchi pointed out, NiceGUI's .props() method is the general escape hatch for setting any Quasar prop on any element. For your tooltip offset example:

with ui.label('Hover me'):
    ui.tooltip('Hello World').props(':offset="[0,10]"')

(Note the leading colon : indicating a string value that needs to be converted into a JavaScript array by the client.)

This works for all Quasar props across all components — see the Styling & Appearance docs.

The reason we don't expose every Quasar prop as an explicit Python parameter is that Quasar components can have dozens of props each, and surfacing all of them would make the API overwhelming and hard to maintain. Instead we focus the __init__ signatures on the most commonly used props and rely on .props() for the rest. This keeps the API clean and discoverable while still giving full access to every Quasar feature.

That said, we're always interested in expanding built-in parameter support for props that users frequently reach for. If you find yourself regularly using a particular prop like offset on tooltips, feel free to open a feature request or PR — that kind of real-world usage signal is exactly what helps us decide which props deserve first-class support.

[jtrip]

Ah yes, sorry I missed that! Using .props() should be good enough for now, but thanks for letting us know you are open for changes, we'll speak up if it comes to that. 😄