Shaun Peet
Top achievements
Rank 2
Rank 2
Shaun Peet
asked on 16 Apr 2008, 03:33 PM
It looks like this slipped under the radar and didn't get updated. setUrl(url) still works and set_url(url) does not work. The other client-side methods were updated (set_Width is now set_width, etc) so I figured this was an oversight.
Great job with the Q1 2008 release so far! I've only had to make minimal changes from the Promethues Q3 2007 release.
Great job with the Q1 2008 release so far! I've only had to make minimal changes from the Promethues Q3 2007 release.
4 Answers, 1 is accepted
0
Hi Shaun Peet,
Thank you for the nice words - we are glad that you like the Q1 release.
As for the setUrl() property, we never planned to change its syntax. There is another client-side method - set_navigateUrl() which has to be executed before showing the window (w.g. before show()) and its casing is set accordingly to the ASP.NET AJAX convention. We decided to use this method as it maches the NavigateUrl property on the server.
All the best,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Thank you for the nice words - we are glad that you like the Q1 release.
As for the setUrl() property, we never planned to change its syntax. There is another client-side method - set_navigateUrl() which has to be executed before showing the window (w.g. before show()) and its casing is set accordingly to the ASP.NET AJAX convention. We decided to use this method as it maches the NavigateUrl property on the server.
All the best,
Georgi Tunev
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
Shaun Peet
Top achievements
Rank 2
Rank 2
answered on 18 Apr 2008, 12:53 AM
Hi Georgi,
I appreciate the explaination you gave, but I must admit that it doesn't make a whole lot of sense. Are the setUrl and set_navigateUrl methods exactly the same? The trend seemed to be with Q1 2008 that all the extra fluff was being taken out of the scripts and that naming conventions were being followed. It'll be hard to justify any method that begins with "set" to not automatically be a "set_whatever" method. Just my 2 cents...
Shaun.
I appreciate the explaination you gave, but I must admit that it doesn't make a whole lot of sense. Are the setUrl and set_navigateUrl methods exactly the same? The trend seemed to be with Q1 2008 that all the extra fluff was being taken out of the scripts and that naming conventions were being followed. It'll be hard to justify any method that begins with "set" to not automatically be a "set_whatever" method. Just my 2 cents...
Shaun.
0
David Harrison
Top achievements
Rank 1
Rank 1
answered on 03 Apr 2009, 04:22 PM
So.. Why is the set_navigateUrl() method not in the documentation? Thankfully, I found this post, as the setUrl() was not working correctly for me. The documentation seems spotty at best, and several of the examples don't seem to work. Very frustrating.
Regards.. David Harrison
Regards.. David Harrison
0
Accepted
Hello David,
To our best knowledge, all code samples in the RadWindow documentation should work (or we would not keep them there). On occasions, however, it can that a change in functionality can cause sample code to not function anymore. If you point to us the exact examples and the exact errors that you encountered, we will immediately correct the documentation.
We believe for RadWindow documentation to be extensive and to cover the public, "advertised" functionality of the control - and it is meant to be used in complement with the RadWindow online demos. Certainly, some hacks that have been provided in the forums to address bugs or specific scenarios are not (and will not be) included in the documentation.
The setUrl function does work correctly. It is meant to change the URL of the RadWindow object - and it does so. This is the exact function that has to be used, and is properly documented. On the contrary, the set_navigateUrl is not to be used, and - hence - is not documented.
To summarize, if you provide us with concrete problems, examples of failed code or missing documentation for particular methods/features - we will quickly address these ommisions. In your last post, however, no such data is provided.
Best regards,
Tervel
the Telerik team
Check out Telerik Trainer , the state of the art learning tool for Telerik products.
To our best knowledge, all code samples in the RadWindow documentation should work (or we would not keep them there). On occasions, however, it can that a change in functionality can cause sample code to not function anymore. If you point to us the exact examples and the exact errors that you encountered, we will immediately correct the documentation.
We believe for RadWindow documentation to be extensive and to cover the public, "advertised" functionality of the control - and it is meant to be used in complement with the RadWindow online demos. Certainly, some hacks that have been provided in the forums to address bugs or specific scenarios are not (and will not be) included in the documentation.
The setUrl function does work correctly. It is meant to change the URL of the RadWindow object - and it does so. This is the exact function that has to be used, and is properly documented. On the contrary, the set_navigateUrl is not to be used, and - hence - is not documented.
To summarize, if you provide us with concrete problems, examples of failed code or missing documentation for particular methods/features - we will quickly address these ommisions. In your last post, however, no such data is provided.
Best regards,
Tervel
the Telerik team
Check out Telerik Trainer , the state of the art learning tool for Telerik products.