commits
This however does mean the original rendering is rendered useless, but we keep it for backwards compatibility, beit with a deprecation sticker.
This is possible, because the widget module does not expose any widget/base specific API's and so can just point to the new implementation, leaving widget/base behind for compatibility (but with deprecation notice)
Signed-off-by: strawmelonjuice <mar@strawmelonjuice.com>
Signed-off-by: strawmelonjuice <mar@strawmelonjuice.com>
This however does mean the original rendering is rendered useless, but we keep it for backwards compatibility, beit with a deprecation sticker.
This is possible, because the widget module does not expose any widget/base specific API's and so can just point to the new implementation, leaving widget/base behind for compatibility (but with deprecation notice)