Introduces date selector to xilem

[giannissc]

I pushed a first draft so that people can have a look but I am not happy with it. I think I misunderstand how map_state and adapt work. I was under the impression that you can take any arbitrary state, create a subset and then pass it to a child view. In this case, I was hoping to be able to do

struct DateLocal {
    month: Month,
    year: i32,
}

}
struct Calendar {
    selected_date: Date,
    date_local_1: DateLocal,
    date_local_2: DateLocal,
}

Using this I though I could share selected_date between two date() view and adapt the state using (selected_date, date_local_1) and (selected_date, date_local_2)

Is there something I am missing here?

[giannissc]

I believe this is ready for review! I still haven't evaluated the state_accessoralternative we talked about in Zulip but since I don't hate this I am happy to merge and create a new PR for any future changes! @Philipp-M

[DJMcNab]

Don't have time for a full review, but some initial thoughts.

Could you also include a screenshot in this thread?

[DJMcNab]

I wonder if this should live in a components folder? From a developer of Xilem perspective, there is a meaningful difference between "raw" views and composed components. But from an end-user perspective, they are the same.

I don't know what the right answer is here.

[giannissc]

I am going to actually create an RFC to discuss this among ither things that i have in mind. For now I would suggest to do both. In the internal folder organisation there should be a primitives folder and a components folder but at the tip the should all be re-exported together. Does this sound reasonable?

[DJMcNab]

We should have some docs here.