[Solved] Using RadWindow without skins

[Daniel]

Hello,

I am replacing my ASP.NET AJAX ModalPopupExtender panels with the RadWindow.

I am attempting to use the 'Border' and 'CssClass' attributes of the RadWindow to create a custom window without the default borders provided with the TitleBar. This would be the equivalent of using a regular Panel and setting its CssClass to define the borders.

I have attempted to set EnableEmbeddedSkins="false", VisibleTitleBar="false", and then set the BorderStyle, BorderWidth, CssClass, etc., to customize the window. Unfortunately this results in a window with no styling or borders at all. I don't want to create a custom skin to achieve a simple CSS-based theme. Is there any way to achieve this?

[Martin]

Hello Daniel,

You can easily achieve the desired changes of the appearance of RadWindow by editing the Skin/Window.[SkinName].css file. Unfortunately, RadWindow does not support the CssClass, BorderWidth, etc. properties, because we believe that they are not that flexible as writing pure css. If you have problems editing the css, we will gladly help you.



Greetings,

Martin Ivanov
the Telerik team

Instantly find answers to your questions at the new Telerik Support Center

[Daniel]

Hi Martin,

Yes it turned out to be quite easy to use custom skins and integrate them with ASP.NET 2.0 Themes. Thanks!

Daniel

[Brad]

HUH??????

You can write the CSS but the RadWindow doesn't support CSSClass? 

I'm still flaying away at this. Here's my desired result:

A three column table that autoresizes. In the left column a Panelbar. In the center column a space which holds RadWindows which waterfall stack. Each window has NO borders only a Title and close, minimize, and restore icons. The minimize icon executes a dock to a panel in the third column of the table and shows just the title and the restore icon. 

I have the panel bar working. I can open multiple windows and minimize them to the dock panel. BUT the owner thinks the windows look funky and wants them limited to the center section. A lot of this I have working but can't seem to get a skin to work the way I'd like (or even work at all). Yes, I've been through the demo/tutorial at :

http://www.telerik.com/help/aspnet-ajax/appearance-css-classes-usage.html

but can't get it to work. I've gotten rid of the title bar and the status bar but not the borders. I'd really like to get that part to happen using CSS instead of skins. The minimize and dock/undock I can get to work with image buttons on the page itself but the borders are defying my attempts to make them go away. 

Any help would be greatly appreciated, thanks,

Joe 

[Georgi Tunev]

Hi Joe,

The CssClass property will affect the RadWindow with the next update.


Best wishes,
Georgi Tunev
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.

[Brad]

UH-OH.....

An update.

Every time I do one of those I have a ton of issues. Any way to just update the RadWindow? Any idea on when the update will happen?

Thanks,

Joe B

[Georgi Tunev]

Hello Joe,

The service pack is scheduled for the next month. The feature is also available in our internal builds that you can download from your Client.Net account.



All the best,
Georgi Tunev
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.

[Brad]

Georgi,

I seem to always have a lot of issues when I do an upgrade. We are actually in beta test with some of our clients and would hate to have the site be unavailable for an extended period of time while I figure out why the upgrade broke so many things. I think a lot of this has to do with my install process. Is there a DEFINITIVE description of how to do an upgrade without breaking the site?

Thanks,

Joe B

[Georgi Tunev]

Hello Joe,

I would suggest to follow this pattern when upgrading

1. Check the Changes and Backward Compatibility topics in the documentation for every control that you are using. Such topic is available in every control's section.
2. Backup your project
3. Update the DLL files and the references (if they are not updated automatically). 
4. Revise your logic if revision is necessary because of a major change in any of the controls that you are using.
5. Build and run.

Regards,
Georgi Tunev
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.