Aleksandar
Top achievements
Rank 1
Rank 1
Aleksandar
asked on 14 Nov 2008, 04:37 AM
Another info missing in your documentation: How to disable custom (template) pager from client side? How to refference it on client side as a first info.
Suggestion for your (bad) documentation:
Each control needs COMPLETE info on:
-Client object model
--Examples - simple cases
--Examples - complex cases
-Server object model
--Examples - simple cases
--Examples - complex cases
Each controll needs standardised information, so finding info is not an issue (like now is).
Regards,
Alex
Suggestion for your (bad) documentation:
Each control needs COMPLETE info on:
-Client object model
--Examples - simple cases
--Examples - complex cases
-Server object model
--Examples - simple cases
--Examples - complex cases
Each controll needs standardised information, so finding info is not an issue (like now is).
Regards,
Alex
3 Answers, 1 is accepted
0
Aleksandar
Top achievements
Rank 1
Rank 1
answered on 14 Nov 2008, 08:16 AM
Add to this: How to disable complete radgrid control?
Alex
Alex
0
Hi Aleksandar,
Thank you for your feedback.
I can assure you that our constant goal is to enhance and organize the RadControls for ASP.NET AJAX documentation further to make it easy for navigation/search and at the same time provide simple and complex examples in the relevant sections either as how-to or general articles.
This is the case with our grid control as well, although organizing the content in Client object model/Server object model main chapters may not be the best idea (as it is with the navigation controls for example) and we think that arranging the chapters based on the concrete functionality in question can be more useful for our clients. That is why we separated the content in Rows/Columns/Sorting/Grouping/etc. chapters and included how-to topics as subchapters and general How-to in the main tree of the help application.
Additionally, we have 'Visible/Enabled conventions' chapter with a couple of help articles which explain how to enable/disable or show/hide RadGrid either client-side or server-side:
http://www.telerik.com/help/aspnet-ajax/gridoverview.html
To disable your custom pager in particular client-side, you will need to liocate the relevant tr element inside the tfoot tag (part of the grid html table rendered in the browser) and disable its elements using similar approach as this demonstrated here.
I hope this explanation makes sense and is useful to you.
Kind regards,
Stephen Rahnev,
Thank you for your feedback.
I can assure you that our constant goal is to enhance and organize the RadControls for ASP.NET AJAX documentation further to make it easy for navigation/search and at the same time provide simple and complex examples in the relevant sections either as how-to or general articles.
This is the case with our grid control as well, although organizing the content in Client object model/Server object model main chapters may not be the best idea (as it is with the navigation controls for example) and we think that arranging the chapters based on the concrete functionality in question can be more useful for our clients. That is why we separated the content in Rows/Columns/Sorting/Grouping/etc. chapters and included how-to topics as subchapters and general How-to in the main tree of the help application.
Additionally, we have 'Visible/Enabled conventions' chapter with a couple of help articles which explain how to enable/disable or show/hide RadGrid either client-side or server-side:
http://www.telerik.com/help/aspnet-ajax/gridoverview.html
To disable your custom pager in particular client-side, you will need to liocate the relevant tr element inside the tfoot tag (part of the grid html table rendered in the browser) and disable its elements using similar approach as this demonstrated here.
I hope this explanation makes sense and is useful to you.
Kind regards,
Stephen Rahnev,
Technical Support Director, Telerik
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Check out Telerik Trainer, the state of the art learning tool for Telerik products.
0
Aleksandar
Top achievements
Rank 1
Rank 1
answered on 19 Nov 2008, 02:03 AM
Hi Stephen,
Thanks for usefull link you pointed me to (second one). Unfortunately, that link was in documentation I always have opened in front of me, but, for some reason I couldn't find it.
I am sure your intention is to provide clients with accurate and comprehensive documentation.
I disagree that client / server object model documentation for some controls is less usefull then arranging the chapters based on the functionality. Client/Server object model is a well known standard many (if not all) vendors are using and we as programmers are very familliar and used to it. If we need quick info on something, we go there for help. While, when learning about new controll or if Client/Server model is difficult to understand, we go through case scenarios and examples. That takes much more time and clashes with the purpose of RAD controlls, which is to save time. I am amaised by functionality of your controlls and realy enjoy learning about all available options, but I also have my own deadlines to follow. Major reason for investing in RAD controlls was faster delivery of a more complex content. I have acheived "more complex" but still far away from reaching the goal of providing final product proportionately faster then before. Documentation is the one reason for that.
At the end, I am suggesting you to include all, client/server object model (with ALL APIs thoroughly explained), case scenarios, examples and chapters organised on a base of functionality.
Thanks for your help provided.
Alex
Thanks for usefull link you pointed me to (second one). Unfortunately, that link was in documentation I always have opened in front of me, but, for some reason I couldn't find it.
I am sure your intention is to provide clients with accurate and comprehensive documentation.
I disagree that client / server object model documentation for some controls is less usefull then arranging the chapters based on the functionality. Client/Server object model is a well known standard many (if not all) vendors are using and we as programmers are very familliar and used to it. If we need quick info on something, we go there for help. While, when learning about new controll or if Client/Server model is difficult to understand, we go through case scenarios and examples. That takes much more time and clashes with the purpose of RAD controlls, which is to save time. I am amaised by functionality of your controlls and realy enjoy learning about all available options, but I also have my own deadlines to follow. Major reason for investing in RAD controlls was faster delivery of a more complex content. I have acheived "more complex" but still far away from reaching the goal of providing final product proportionately faster then before. Documentation is the one reason for that.
At the end, I am suggesting you to include all, client/server object model (with ALL APIs thoroughly explained), case scenarios, examples and chapters organised on a base of functionality.
Thanks for your help provided.
Alex