[forms-devel] Opening up custom renderers for extension

[Michael Ridland]

To give a bit more context, what I'm trying to do is remove the inset from
the separators in iOS. I got it working override the ViewCellRenderer for a
normal listview but never when using cell recycling. I gave up with trying
to get it working with the cell recycling and now I'm adding the divider
manually in my views but for performance and in order to reduce nesting I
didn't want to add a extra layer to my layout that are nice and fast in
grids. I'm now creating a boxview that ignores the grids padding.

[image: Inline image 1]

All so I can do this...

[image: app 1.png]


*Michael Ridland | Technical Director | Xamarin MVP*

XAM Consulting - Mobile Technology Specialists

www.xam-consulting.com

Blog: www.michaelridland.com



On Thu, Jun 23, 2016 at 11:01 AM, Michael Ridland <rid00z at gmail.com> wrote:

> Hi
>
> 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
> them.
>
> 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
>
> www.xam-consulting.com
>
> Blog: www.michaelridland.com
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ximian.com/pipermail/forms-devel/attachments/20160623/bb8a6214/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/bb8a6214/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-06-23 at 11.09.03 AM.png
Type: image/png
Size: 61151 bytes
Desc: not available
URL: <http://lists.ximian.com/pipermail/forms-devel/attachments/20160623/bb8a6214/attachment-0003.png>