I've currently downloaded the source code to the MVC wrappers and am writing improved versions of the Renders to support Knockout.
In order to try and maximizer compatibility I've implemented my changes as additional classes and extension methods, so that any source code upgrades should be easy to maintain, I've had to implement them inside the infragistics project due to needing to access/inherit from internal classes.
Could you make all the classes public, expose the _helper and _model fields as properties of the wrappers and allow us to use alternative renderers.
Hello,
I would recommend you to download source code and modify the code based on your requirements. Log in to your account in order to download source code:
https://www.infragistics.com/my-account/keys-and-downloads/
Once you log in click on the product version you are using. It will show public download in below tab. Click on the “SourceCode” tab. You can download source code and modify it based on your requirements.
I hope this helps.
I am just following up to see if you need any further assistance with this matter.
Well the reply was a little disappointing, basically telling me to do what I already said I was doing. Altering the source code means that integration is a little more complex with every service release update.
Hi there,
My understanding is that you are overriding the Render() method of each controls Renderer. We can expose the helper and the model as properties, but we would need a work item logged for that. I will ask Developer Support to log it.
Thanks you for using the Infragistics forums!
I have logged the feature request PI13040041 on your behalf. I have sent that feature request directly to product management team. Our product team chooses new feature requests for development based on popular feedback from our customer base.
If your feature is chosen for development, you will be notified at that time. Your reference number for this feature request is PI13040041.
Feel free to update me if you have any further questions.
Thankyou for this.
What also would be useful would be a way to register an alternative renderer at the page level. Then the model Render() function would use the alternative renderer without needing change the code at the model level.
for example..
@Html.Infragistics().ReplaceEditorRenderer<MyRenderer>()
@Html.Infragistics().TextEditorFor(m => m.Name).Render()@Html.Infragistics().TextEditorFor(m => m.Address).Render()