Add date picker

[dword-design-honestly]

Add date picker

[xvaara]

imho. We already have type="datetime-local" so we don't need a picker anymore in the main libary.

I have bootstrap style date/time -pickers in one client project, I could maybe clean that up for us.
@VividLemon thoughts?

[dword-design-honestly]

@xvaara afaik the dropdowns system date inputs aren't styleable because they depend on the OS.

[xvaara]

@dword-design-honestly yes, that's why they work universally, and on mobile I prefer the native widget over any other picker.

[VividLemon]

Also the bootstrap vue versions appearance is quite dated looking. The native variants simplify things

[VividLemon]

imho. We already have type="datetime-local" so we don't need a picker anymore in the main libary.

I have bootstrap style date/time -pickers in one client project, I could maybe clean that up for us. @VividLemon thoughts?

I have no opinion. It's your call.

[dword-design-honestly]

@VividLemon Would not reuse the styling from BootstrapVue probably, doesn't look that good. Having the option to have a custom widget makes sense to me since, although having the universal one is a pro because it just works, if you have a specific design, it sometimes doesn't integrate well (color of selected date, border radius, padding and stuff).

[xvaara]

@VividLemon imho, I'm two minds about this. I'd like to keep the core components simple. Maybe have another repo for more complex components that aren't "bootstrap"... but we already have BTable that's quite complex and "violates that divide"

I'd like us not to have to "create css" only use what bootstrap has provided.

I'd probably just take https://www.radix-vue.com/components/date-picker.html and style that to match my site.

on the other hand, multiselect and date/time picker, better number input, range selector, range on datetime, pin input, color picker, tree, wysiwyg editor (tiptap) ... I've done all of those for client sites that use bootstrap-vue-next and they are nice to have :)

[VividLemon]

but we already have BTable that's quite complex and "violates that divide"

There are places where it does seem appropriate to take over. Tables can have a lot of nested html making it difficult to create many tables. This isn't something that is related to bootstrap, nor is it something that they could fix given their limited knowledge of the app.

However, other components like spinbutton, date picker, etc are all really bootstrap components. These things could be implemented in bootstrap (within reason, a single "spinbutton" is really just a collection of multiple buttons... So a bootstrap component seems odd for this)

It's a complicated issue. Realistically the only downside is that there is more maintenance on our end. Which is why strategies of abstraction are the best imo (since these things have already been created, and we're just reinventing the wheel), such as embedding radix Vue. Although we have talked about this before. If we were able to abstract things like pin input, date-picker, to an external source, I would be significantly more comfortable with adding many more "standard" components. I'd be fine with rewriting existing components, but I recall you having issues with that idea @xvaara

[dword-design-honestly]

Throwing in the argument that most UI frameworks have a themeable date picker component (in contrast to more special components e.g. like a WYSIWYG editor). Ofc. the difficulty is to set the boundary where the framework ends and contributed packages with special components consuming Bootstrap variables start.

I also think that reusing a Vue 3 date picker component and then styling it with Bootstrap makes more sense than reimplementing it.

[VividLemon]

If the implementation is a wrapper around https://www.radix-vue.com/components/date-picker , then I'm going to "okay" it