Richard Topchii

Hi, thanks a lot for your pull request! Highly appreciate! I've checked out your request and found few issues that make it hard to fit to the existing CalendarKit architecture....

Sorry for brevity of my reply, on mobile. 1. The reason is not to be similar with the table view interface or performance. The reason is to keep the data...

Hi, commenting on your thoughts: > _we oblige the CalendarKit to create custom event views on our own._ That's the point, event creation and configuration is left for the CalendarKit....

> I believe that by this step we artificially limit the flexibility of the CalendarKit. A situation may arise when the logic of initializing a custom event view may differ...

> For what purposes is there EventView#descriptor? Why does the view layer keep a reference to the model object? This is in order to figure out which event has been...

Btw, feel free to email me at [email protected] or reach via Telegram https://t.me/richardtop to discuss this feature more in detail.

Hi @johnnyperdomo, Could you please share the result you're trying to achieve? You can mock it with Sketch/Photoshop or any other graphic editing software. We could rephrase the question and...

@johnnyperdomo could you put these screenshot in context? I.e. how they would look on a timeline?

@johnnyperdomo if you look inside e.g. `Timeline`, you'll notice the code to support a custom `UIView` subclass, but there is no interface to connect a custom view to the rest...

1. It's impossible now to register a custom view to be used as the `EventView`, similarly to how the `UITableView` or `UICollectionView` supports custom views. 2. No, currently the layout...