librelist archives

Re: gxp.Viewer layout

Re: gxp.Viewer layout by Andreas Hocevar
- Re: [geonode] Re: gxp.Viewer layout by Andreas Hocevar

Re: gxp.Viewer layout

From:: Andreas Hocevar
Date:: 2010-07-08 @ 07:12

Hi Seb,

see my answers inline.

On Jul 7, 2010, at 23:56 , Sebastian Benthall wrote:

> Trying to work with the new gxp.Viewer-based map composing application 
and running into some trouble figuring it out.
> 
> What I'm trying to do is add an additional panel between the header and 
the topbar with the tools where I can put some extra content and links and
such.
> 
> A few questions:
> 
>  * It looks like the Viewer is rendering to the Ext.Viewport.  What is 
constraining the size of the Viewport so that it isn't taking the full 
screen (i.e., not clobbering the header)?

It is the portalConfig property of the viewer that controls this. If it 
has a renderTo property configured, it will not use the whole viewport, 
but you can tell it to render into a div that you have prepared in the 
html (much like the way you tell an OpenLayers.Map where to go).

> 
>  * Is the hierarchy of panels used by the Viewer/GeoExplorer class 
documented anywhere?  I'm trying to wrap my head around it.  Any info you 
had on it would be helpful.

The viewer can be configured with a portalItems property. This is an array
of containers that make up the space occupied by the viewer (i.e. the 
viewport if no portalConfig.renderTo property is found, and the specified 
div otherwise). The viewport uses a border layout, and all portalItems go 
into the wrapping container with the border layout.

> Anyway, looking forward to learning more about gxp as I work on this.  
Thanks for any advice you can provide.

Let me know if anything is still unclear.

-Andreas.

-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.

Re: [geonode] Re: gxp.Viewer layout

From:: Andreas Hocevar
Date:: 2010-07-08 @ 07:19

Oh, one thing I forgot to explain:

the gxp.Viewer will always add one component to the portalItems: a 
MapPanel with the viewer itself. And the MapPanel will be the "center" 
region of the border layout.

-Andreas.

On Jul 8, 2010, at 09:12 , Andreas Hocevar wrote:

> Hi Seb,
> 
> see my answers inline.
> 
> On Jul 7, 2010, at 23:56 , Sebastian Benthall wrote:
> 
>> Trying to work with the new gxp.Viewer-based map composing application 
and running into some trouble figuring it out.
>> 
>> What I'm trying to do is add an additional panel between the header and
the topbar with the tools where I can put some extra content and links and
such.
>> 
>> A few questions:
>> 
>> * It looks like the Viewer is rendering to the Ext.Viewport.  What is 
constraining the size of the Viewport so that it isn't taking the full 
screen (i.e., not clobbering the header)?
> 
> It is the portalConfig property of the viewer that controls this. If it 
has a renderTo property configured, it will not use the whole viewport, 
but you can tell it to render into a div that you have prepared in the 
html (much like the way you tell an OpenLayers.Map where to go).
> 
>> 
>> * Is the hierarchy of panels used by the Viewer/GeoExplorer class 
documented anywhere?  I'm trying to wrap my head around it.  Any info you 
had on it would be helpful.
> 
> The viewer can be configured with a portalItems property. This is an 
array of containers that make up the space occupied by the viewer (i.e. 
the viewport if no portalConfig.renderTo property is found, and the 
specified div otherwise). The viewport uses a border layout, and all 
portalItems go into the wrapping container with the border layout.
> 
>> Anyway, looking forward to learning more about gxp as I work on this.  
Thanks for any advice you can provide.
> 
> Let me know if anything is still unclear.
> 
> -Andreas.
> 
> 
> 
> -- 
> Andreas Hocevar
> OpenGeo - http://opengeo.org/
> Expert service straight from the developers.
> 

-- 
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.