sadiqabbas
Top achievements
Rank 1
Rank 1
sadiqabbas
asked on 19 Jan 2010, 07:19 AM
there are many many of things that can be included as the sky is the limit
but acc. to me below are 2 things which should be done for betterment of new version
1) paypal payment option /paypal cart etc.
2) seperate dll for every control
below is the reasons
nowadays every one is expecting the developers to implement payment system for their website and if developers find telerik an easy option for implementing payment option via paypal then this could surely effect sales of the control in a positive manner i.e increase of sales
and for seperate dll reason is that all wont require all controls to be included for example i am developing a site in which i just only require menu, combobox and editor so rest of all are just aquiring server space with out any requirement but instead if there is seperate dll for every control then on need to include only those dll in bin folder which are used by his website
thakns..
but acc. to me below are 2 things which should be done for betterment of new version
1) paypal payment option /paypal cart etc.
2) seperate dll for every control
below is the reasons
nowadays every one is expecting the developers to implement payment system for their website and if developers find telerik an easy option for implementing payment option via paypal then this could surely effect sales of the control in a positive manner i.e increase of sales
and for seperate dll reason is that all wont require all controls to be included for example i am developing a site in which i just only require menu, combobox and editor so rest of all are just aquiring server space with out any requirement but instead if there is seperate dll for every control then on need to include only those dll in bin folder which are used by his website
thakns..
1 Answer, 1 is accepted
0
Accepted
Hi sadiqabbas,
Thank you for the suggestions - I will forward the first one to the proper authorities to be considered further.
Concerning the second - indeed this can facilitate the development to some extent (adding separate assemblies to be compiled by Visual Studio and expose IntelliSense for them) and that is what we done for the Classic versions of RadControls for ASP.NET. However, this would bring unnecessary implications to the scripts/skins registration and make the deployment process cumbersome. That is why we decided that the optimal choice would be to have a single assembly for our controls.
Best regards,
Sebastian
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Thank you for the suggestions - I will forward the first one to the proper authorities to be considered further.
Concerning the second - indeed this can facilitate the development to some extent (adding separate assemblies to be compiled by Visual Studio and expose IntelliSense for them) and that is what we done for the Classic versions of RadControls for ASP.NET. However, this would bring unnecessary implications to the scripts/skins registration and make the deployment process cumbersome. That is why we decided that the optimal choice would be to have a single assembly for our controls.
Best regards,
Sebastian
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.