hello guys.

i was wondering if anyone can give any feedback on the current status (and even more important, what about the future) regarding the use of web parts with atlas.

i've noticed that the new webpartmanager and webpartzone let's us use web parts in firefox with the same look and feel as if we're using IE. however, these classes seem to introduce some bugs when we put everything inside an update panel...

any comments on this? thanks

Hi ,

The only way I have gotten Web Parts to work with Atlas is to wrap the web part zone with update panels. Then all the web parts in that web zone appear to work using partial rendering.

Alternatively, if you are using a Master Page you can wrap all the controls within the content section of your page in an update panel. Note: I am talking about the content section of the page that uses the MasterPage not the Master Page itself.

 

Hope this helps,

Toki

 

hello.

have you managed to put it working with firefox? you see, i've managed to put everything working with IE (ie, sort of - read my previous post about the bug that exists in the webpartmanager class). however, i was investigating the new webpartmanager and webpartzone controls introduces with atlas and they really work with firefox if you use a full postback; when you wrap everything in a updatepanel, you'll get assertions related with duplicate webpartmanager controls...

hasn't anyone got this error yet?

1. You need to place all WebParts controls inside the UpdatePanel (WebPartManager, WebPartZones, ToolZones).
2. You need to use the Atlas WebPartManager and WebPartZone, not the ASP.NET 2.0 WebPartManager and WebPartZone.

-Mike

Thanks for the info Mike, but where do you find the Atlas WebPartManager and WebPartZone controls?  I could not see them in the Atlas controls toolkit.

I was thinking you mean replacing <asp:WebPartManager /> with something like <atlas:WebPartManager /> but I'm obviously on the wrong track.

Any help appreciated - and keep up the great work.  The framework is awesome!

Hello Mike.

that's what i'm doing. in the previous posts, i mention that the new controls (webpartmanager and webpartzone) work without any problems with a full page postback (and you get the same feel as in IE). however, if I put everything inside an updatepanel and the webpartmanager is set to designmode, i get an assertion during the partial postbak that says that there are duplicate webpartmanager elements oh the page.

i didn't had any time to dig through this...i'll try to to it today and post more info on the problem i'm facing.

thanks.

See this blog post for how to use the Atlas WebPartManager and WebPartZone:

http://davidbarkol.com/blog/archive/2006/03/22.aspx

-Mike

Luis,

The Atlas WebPartManager and WebPartZone should work inside an UpdatePanel, as long as all the WebParts controls are in a single UpdatePanel.  Make sure you are using the April CTP.  If you are seeing otherwise, please post a minimal code sample to reproduce the issue.

-Mike

Hello again Mike.

if you take the code i've wrritten in the other post about the bug of the webpartmanager control and replace the webpartmanager and webpartzones with the ones introduced by atlas, you'll get the errors i'm mentioning here. i've tried it with 2 different machines and the errors persist in that scenario.

 

This doesn't repro for me using the April CTP.  I know there were bugs like this in the March CTP, but they were fixed in the April CTP.  Are you sure you are using the April CTP?

-Mike

hello again.

hum..-j'm almost sure i have that version installed. if you want, i can send you the complete study project i'm using here...

btw, i'm using firefox 1.5.0.1

Found this usercontrol on www.smartjungle.com which provides a WebParts control to get AJAX capabilities and complete Firefox compatibility with no extra code

http://www.smartjungle.com

Demos:
http://www.smartjungle.com/Demos.aspx

Hello,

I have created a very simple application that uses WebParts and Atlas. By placing all of my controls (a WebPartManager, 2 WebPartZones, and 1 DropDownListbox within a single UpdatePanel, I managed to get everything working in IE except the Drag-and-Drop aspect of WebParts. For this,  I used David's posting of the additional code required in the web.config file to add a section called <tagMapping> that directs the application to use the Atlas version of the WebParts. As an aside, I noticed that by using the AutoPostBack feature of the dropdownlistbox, I did not require any triggers, although I have included one in the code below.

My question though is that while my application does work in IE, the Drag-and-Drop ability of Design Mode still does not work in Mozilla FireFox. I have the June Release of Atlas, and version 1.5.0.4 of FireFox. I would appreciate any help as I am out of ideas.

Thanks! (and here is my code below)

JCL

<%@ Page Language="VB" AutoEventWireup="true" CodeFile="Default.aspx.vb" Inherits="_Default" %>

<%@ Register Src="WebUserControl.ascx" TagName="WebUserControl" TagPrefix="uc1" %>

<!

DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">

<

html xmlns="http://www.w3.org/1999/xhtml">

<

head runat="server">

<title>Untitled Page</title>

</head>

<body style="filter:progid:DXImageTransform.Microsoft.Gradient(endColorstr='#C0CFE2', startColorstr='#FFFFFF', gradientType='0');">

<atlas:ScriptManager ID="ScriptManager1" EnablePartialRendering="True" runat="server" />

<form id="form1" runat="server">

<atlas:UpdatePanel ID="p1" runat="server">

<ContentTemplate>

<asp:WebPartManager ID="WebPartManager1" runat="server">

</asp:WebPartManager>

<asp:WebPartZone ID="WebPartZone1" runat="server" BackColor="#FFFF80">

</asp:WebPartZone>

<asp:WebPartZone ID="WebPartZone2" runat="server" BackColor="#C0FFC0">

</asp:WebPartZone>

<asp:CatalogZone ID="CatalogZone1" runat="server">

<ZoneTemplate>

<asp:DeclarativeCatalogPart ID="DeclarativeCatalogPart1" runat="server">

<WebPartsTemplate>

<uc1:WebUserControl ID="WebUserControl1" runat="server" />

</WebPartsTemplate>

</asp:DeclarativeCatalogPart>

</ZoneTemplate>

</asp:CatalogZone>

<asp:DropDownList ID="DropDownList1" runat="server" AutoPostBack="True">

<asp:ListItem>Browse</asp:ListItem>

<asp:ListItem>Catalog</asp:ListItem>

<asp:ListItem>Design</asp:ListItem>

</asp:DropDownList>

</ContentTemplate>

<Triggers>

<atlas:ControlEventTrigger ControlID="DropDownList1" EventName="SelectedIndexChanged" />

</Triggers>

</atlas:UpdatePanel>

</form>

</body>

</html>

Apparently, the July CTP of Atlas addresses some issues related to web parts and Mozilla browsers.  Perhaps, the answer resides there...

Yes, this should be fixed in the July CTP.

-Mike