Falko Schindler

Awesome, thanks @Diegiwg! I started to refactor the code (my preferred way of getting to know new code). Now I'm at the point where we should decide what the final...

Thanks, @Diegiwg and @morningstarsabrina, for your feedback and ideas! We brainstormed different options once again: 1. Builder pattern with namespace per section and methods per Tailwind property: ```py ui.label().typography.text_color('orange-900').text_weight('bold').layout.width('full') ```...

Ok, I experimented with option 5/6 and it feels quite nice. I am, however, not sure if auto-suggestions for the 17,000 lines of generated code are fast enough. Sometimes it...

Thanks for the suggestion, @ofenbach! We would rather not introduce a new UI element for this purpose, since it only solves a subset of Tailwind styling and there's no reason...

I think this PR is basically ready to merge. Documentation and tests are done. The last thing I did was to split the 20,000 lines into separate files which improves...

Good question! As far as I can tell, there are multiple layers to the problem: 1. The argument `f"options={date_options}"` results in the string "options=['2023-01-01', '2023-01-12', '2023-01-17']" which is incorrectly parsed...

Oh hey, I found a solution! It turns out the dates have to be in YYYY/MM/DD format: ```py d = ui.date(value='2023-01-01') d._props['options'] = ['2023/01/01', '2023/01/12', '2023/01/17'] ``` You can even...

Thanks for bringing this up, @rbeeli! That's an interesting point. Originally, NiceGUI was built on top of JustPy, which in turn has a pretty strong AG Grid integration. Once we...

@Diegiwg We probably need to handle selection events and send the modified list of selected rows back to the client. That's how we do it for QTree. Have a look...

@Diegiwg, @dclause I'm a bit behind with reviewing/thinking about your PR's #434, #500 and related issues like #501. But I'm planning to look into it next week.