[zMoooooritz]

Just a short heads up!

This is more or less the same that I already had impelmented in #22

I decided to place the interval right inside the WidgetConfig since this is a setting that can be applied to every widget.
I would have loved to model the interval as int but this would mean that widgets without a specified interval get the "default value" 0 which is not desireable.
Furthermore I'm not really happy with the setInterval call in every switch-case but I don't know how I could avoid this.

[muesli]

This is more or less the same that I already had impelmented in #22

Awesome, thanks for porting that over!

I decided to place the interval right inside the WidgetConfig since this is a setting that can be applied to every widget.

Sounds good.

I would have loved to model the interval as int but this would mean that widgets without a specified interval get the "default value" 0 which is not desireable.

I just simplified that logic a bit, so we can use a uint here. The default value zero now means the widget will only see an initial paint, with no further repaints. I've also managed to remove the need for a separate initialized bool, and implemented a specific RequiresUpdate method for the RecentWindowWidget.

Furthermore I'm not really happy with the setInterval call in every switch-case but I don't know how I could avoid this.

1. Instead of directly returning a newly generated Widget, we could store it a var first and then have one generic setInterval call outside the switch statement. This works because all widgets we create match the Widget interface, so they can be kept in the same type of variable.
2. Instead of manually setting a default interval, we could implement widget specific RequiresUpdate functions, that for cases where w.Interval is zero (the default) apply their own default interval. This keeps the logic inside the widget itself and widget.go becomes a bit less coupled to the individual widgets.

[zMoooooritz]

I just simplified that logic a bit, so we can use a uint here. The default value zero now means the widget will only see an initial paint, with no further repaints.

Not a huge of using zero as "no repaints required" but for the sake of cleaner code it is ok.

1. Instead of directly returning a newly generated Widget, we could store it a var first and then have one generic setInterval call outside the switch statement. This works because all widgets we create match the Widget interface, so they can be kept in the same type of variable.
2. Instead of manually setting a default interval, we could implement widget specific RequiresUpdate functions, that for cases where w.Interval is zero (the default) apply their own default interval. This keeps the logic inside the widget itself and widget.go becomes a bit less coupled to the individual widgets.

Like the way you moved the attribute unpacking to the widgets. This looks so much cleaner now!