It 'a troublesome problem, because you can no longer edit in design mode in the construction of the web page.
I hope this is only an initial problem and not a desired behavior, as it is extremely annoying.
Thanks.
17 Answers, 1 is accepted
Indeed, working with the RadPageLayout in design mode in the Visual Studio is about to be implemented.
I will update you in this thread once the feature is available or you could track our release history here.
Regards,
Nencho
Telerik
DevCraft Q1'14 is here! Watch the online conference to see how this release solves your top-5 .NET challenges. Watch on demand now.
You mentioned 4 months ago this was "about to be implemented" well when is this actually going to be implemented? This is a very problematic issue.
Robert
The RadPageLayout is designed to render its nested content in PlaceHolders. Hence, when the control is used in a MasterPage and the defined PlaceHolders of the MasterPage are placed in the elements of the RadPageLayout, the result is - nested PlaceHolders. In such scenario the controls from the Content Page are unable to be managed in the Designed Mode view of that page. However, you could still use the smart tags of those controls, like demonstrated in this video:
http://screencast.com/t/YkiyGAKKoh
Regards,
Nencho
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
I am afraid that this is a limitation of the VisualStudio 2010 and the smart tag is not available in the markup source code.
Regards,
Nencho
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
I am trying to use radPageLayout in the content div of a child page - I guess this is the same problem as when used in master page?
Either way it appears to be unusable for me.
​
As of now, RadPageLayout does not have proper design mode and certain issues, including the one pointed out by you may arise.
It doesn't matter where you use RadPageLayout -- page, master page, control -- you will always have this behaviour. Until we create proper design time, the control will not be that useful in design view.
Regards,
Ivan Zhekov
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.
I can not comment on a date when it's going to be implemented, as it's not planned yet.
Regards,
Ivan Zhekov
Telerik
Indeed the "capability to change content of radpagelayout while in design view" feature has been approved, because it is useful and will make the component much easier for configuration under Visual Studio. The only problem is that it is not among the top rated features in our backlog and for that reason we cannot provide a firm estimate when it will be implemented.
Best regards,
Rumen
Telerik by Progress
It's 2018, did this ever get implement in design view?
If not, what's a good alternative to RadPageLayout as it seems this control isn't a priority?
Cheers, Rob.
The demand for this useful feature is still low and for the time being there aren't plans for implementation. My advice is to give your vote for the feedback item.
The other Layout component in the suite is RadSplitter. Other than this, the dev developers also base their layouts on Bootstrap.
Regards,
Rumen
Progress Telerik
Hi Rumen,
I was able to get the RadPageLayout working to my specifications, however, one minor issue ... the control doesn't seem to response to your RadSkinManager ... if I set a different Skin the RadPageLayout does adjust but all my other Rad controls do.
This is a problem because if the "Black" skin is set to RadSkinManager, label text becomes white but the BackColor of the RadPageLayout doesn't adjust to Black ... so I end up with white text (labels) on a white background making them impossible to see.
I can manually set the BackColor via code behind when a Skin is changed, but is that what the RadSkinManager is supposed to do, it does it fall all the other control but not RadPageLayout?
Is that expected?
Cheers, Rob.
Thank you for the nice idea!
The RadSkinManager can update only the skin of the Telerik controls which have appearance and offer Skin property. The RadPageLayout is a light-weight layout component, which renders invisible on the page and for this reason its does not have skins and a Skin property, respectively.
Can you please file a feature request in the Feedback portal, so that we can measure the interest of such a built-in feature and implement it? Thank you!
Best regards,
Rumen
Progress Telerik
Rumen,
One more comment on RadPageLayout which really make the control useless for any serious development work ... any control contained within it's scope can't be selected in the Designer. This is a serious flaw IMHO, and not really a "feature request".
Similar issue with the RadGrid NOT rendering in the designer ... because of this rather serious limitation, we're having to make changes to xml/html code (even just very minor ones), then run our app just to see those changes and verify they are what we want. This is incredibly tedious and a huge waste of time ... this isn't why we bought and/or renew our Telerik subscriptions, your tools are supposed to make development faster, not slower.
Many of your controls suffer from "property overload" ... too many options/properties some conflicting with each other while key necessities like rendering in the designer are ignored. This is not what we want, we're looking into alternatives and/or just going back to using Microsoft's set of controls.
I don't know who makes the feature implementation decision choices at Telerik, but that person doesn't seem to be aware the less is "more" ... we need easy to implement and intelligent features that "just work".
Not trying to be harsh because I thought that perhaps Telerik's overload philosophy was just Silverlight, but I see it's extended and really seems to have infected all your product line. I think Telerik has lost focus of what rapid development means? Most developers I know have bigger fish to fry than being sucked into the quagmire that is Telerik overload of properties.
Not all bad, you folks have some good features, but you also have way too many features that really should be encompassed and not exposed, embrace AI in your products to make intelligent decisions on layout.
My 2 cents, Rob.
Thank you very much for your feedback.
To be frank we always strive to provide easy configuration and properties in order to avoid the properties hell. You know that the AJAX suite is pretty mature (~16 years old) and during the years due to multiple feature requests by the community, some of the top controls become very-very feature rich, which required to introduce a large number of properties to control the behavior of features and functionality. To ease the configuration some of the components were rewritten or splitted in sub-controls like the Button as well as the documentation and demos improved.
Regarding the Design time support in the controls, it is needed to explain the following limitations:
- The Visual Studio Design view is not so suitable for preview and editing purposes, because it uses a very old version of Internet Explorer (IE6) to preview the page contents and that IE version does not support CSS3 and the other contemporary technologies. Nowadays the developers use the browser to preview and test their work and the Designer is used just for launching the controls smart tags and wizards, rather than a previewer. That's why it is better to directly work with the browser instead of using the Visual Studio Designer. The Designer is also not available for the ASP.NET MVC projects.
- The controls representation in Visual Studio Designer relies on the WinForms technology (System.Windows.Forms.Design), which means that we should implement yet another version of the controls for Winforms, which is time consuming. This time is usually spend on bug fixing, feature and accessibility development, stability and security improvements, which are more popular and required for mature bundles.
Once again thank you for sharing your point of view. I do appreciate it! If you have any concrete ideas and suggestions on improving the suite, please log them in the Feedback portal so that they can get prioritized by the community. If they become popular we will implement them.
Best regards,
Rumen
Progress Telerik