[forms-devel] Opening up custom renderers for extension

Michael Ridland rid00z at gmail.com
Thu Jun 23 01:01:39 UTC 2016


So I'm wondering what's the plan for opening up custom renderers for
extension, I'm trying to solve a (would be) simple issue in my app but the
closed nature of the renderers can continually become a issue.

Today I wanted to override the BoxRenderer and implement my own draw
method, but it contained two private fields which stopped me for
implementing my simple requirement. I know you don't want to worry about
backwards compatibility of renderers, I (like most forms developers) don't
feel you should have to either, when we're extending your custom renderers
we assume that it's now our responsibility for maintenance for our custom
code. I don't feel there's a reason not to have more protected fields and
protected virtual methods and there's a great reason why we should have

I would gladly do the work if it was approved.

[image: Inline image 1]

*Michael Ridland | Technical Director | Xamarin MVP*

XAM Consulting - Mobile Technology Specialists


Blog: www.michaelridland.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/forms-devel/attachments/20160623/bd8c1b8d/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-06-23 at 10.53.33 AM.png
Type: image/png
Size: 65485 bytes
Desc: not available
URL: <http://lists.ximian.com/pipermail/forms-devel/attachments/20160623/bd8c1b8d/attachment-0001.png>

More information about the forms-devel mailing list