portfolio
portfolio copied to clipboard
Introduce new event list widget
This PR introduces a new widget for the dashboard. The purpose of the new widget is to display a list of events of various types for a given time period. The events list is sorted in chronological order. Depending on the given reporting period the displayed events can be past events, current events or upcoming events.
The widget currently supports the following different types of events:
- Calendar events
- Holidays
- Account events
- Interest payment/booking
- Security events
- Dividend declaration(*)
- Dividend record date(*)
- Ex-dividend date(*)
- Dividend payday(*)
- Dividend payment/booking
- Shareholder meeting(*)
- Earnings report(*)
- Stock split
- Note/custom event
Changes:
- added the new event list widget
- extended the existing security event types of the model; new types marked by (*) above
- adjusted the UI to also create events for the new security event types
- adjusted context menus
- adjusted event creation wizard pages
Limitations:
- translation is quick and dirty; created with google translate
- for the event type markers I reused already existing icons. I think they are working ok, but using specifically designed icons would of course be nicer
Screenshots:
A demo dashboard with event list widgets of various reporting periods:

The adjusted context menu in the statement of assets listing:

The adjusted context menu in the statement of assets pane:

An example creation dialog page for an earnings report event:

The unchanged creation dialog page for a custom event with a free-form text input field:

Attachments:
- Demo portfolio pp_test_depot_dax.zip
I like the idea. I need more time to review (the update to the protobuf serialization is definitely missing). Today, I am looking only at the "easy/small" changes to put together a release
Thanks Andreas. Protobuf support added
Is there any way I can help to move this along?
This looks awesome! Thought I'd add a comment to bump this & deliver a big Kudos to you @buletti !
Please take a look on #3099
@buletti :
Is there any way I can help to move this along?
Perhaps you could rebase this on master from time to time, to keep in more "ready" state? Currently Github says "This branch has conflicts that must be resolved".