smas1 / geoext-viewer Goto Github PK

It's possible to make featureinfopanel show layer information in text/html 
format?

the point is that i've some pictures widthin the layer table and want to show 
this pictures at the featureinfopanel...

Currently the geoext-viewer is configured through two files:

(Default)catalog.js
(Default)config.js

It would be better if there would be a single configuration file that needs to 
be clearly documented.

For 'branding' (logo, menu, html content) there needs to be a similar 
procedure. 

The implementation of configuration needs to be immune to updates and patches, 
when the source (svn) changes, user specific information and configuration 
should remain intact.

What steps will reproduce the problem?
1. make app with ActiveLayersPanel (ALP)
2. select some layers
3. change stacking using drag&drop in ALP

- What is the expected output? What do you see instead?
Top layer should be on top in map. Unclear what does happen but not the right 
layer stack ordering. This could be due to the way order of Layers added to the 
tree (ALP has a tree) initially.

There is an urgent need for technical documentation that gives users and site 
managers an easy manifest on how tom implement and configure the geoext-viewer. 
Enduser documentation is outside the scope of the geoext-viewer and should be 
managed by the parties that create derived work.

Design a new layer manager a la edugis 

What steps will reproduce the problem?
1. select some overlay layers
2. select info button
3. click on feature

What is the expected output? What do you see instead?
tab panel with feature info should show feature type as tab name.
Instead empty tabs are shown.

The fix is simple: move title ("title : type.featureType,") from 
Ext.grid.ColumnModel to Ext.grid.GridPanel (where it was originally) as below

                var grid = new Ext.grid.GridPanel({
                    title : type.featureType,
                    store : new Ext.data.JsonStore({
                        autoDestroy : true,
                        fields : type.fields,
                        data : type.records
                    }),
                    colModel: new Ext.grid.ColumnModel({
                        defaults: {
                            width: 120,
                            sortable: true
                        },
                        columns : type.columns,
                        autoScroll : true,
                        listeners : {
                            "render" : function(c) {
                                c.doLayout();
                            }
                        }
                    })
                });


(Milo, did not fix this as you are making changes right now to 
FeatureInfoPanel).

In order to help developers this project needs technical documentation
how to setup a custom viewer. This should be illustrated with examples.

Currently the head section of most pages gets cluttered with all the 
geoext-viewer scripts. Change this to dynamic loading as with openlayers

We would like a opacity/transparancy slider that can be implemented as a tool 
in the geoext-viewer

1. Go to http://kademo.nl/lib/geoext-viewer/trunk/geoviewer/examples/geoportal/
2. Open firebug or some other monitoring tool
3. You will see layers loading while there is no map displayed
4. Clear firebug 
5. Switch to map
6. You will see layers loading again, this time a map will be displayed

What is the expected output? What do you see instead?
Loading layers is a resource consuming task. It should be limited as much as 
possible. I expect this behaviour in other environments too.

For one thing "geoext-viewer" does not sound juicy. Having been through several 
iterations for renaming we settled on the name "Heron" (dutch: Reiger), also 
since the historic figure Heron of Alexandria is the inventor of the 
triangulation and possibly the Theodoliet.

See 
http://en.wikipedia.org/wiki/Hero_of_Alexandria
http://en.wikipedia.org/wiki/Heron%27s_formula
http://en.wikipedia.org/wiki/Heron

This issue deals with making the name changes all over the code and 
documentation, directory renaming etc. 

We also have a domain name http://www.heron-mc.org

All examples show a web mapping app with a main panel that is an ExtJS 
ViewPort, i.e. filling the entire browser window (body). We need an example 
where a map is embedded within any div within a browser page. This has
impact on the main Heron MC app code in App.js (showfullScreen()) , since 
ViewPort is hardwired now.
We need a "renderTo" option at the highest layout level.

This enhancement should allow a user to provide a WMS URL such that the layers 
of that WMS become available for viewing. This is a powerful feature that 
enables "exploration" of remote WMSs and integration with predefined (in 
config) layers.

The intended scenario could be as follows:

- user clicks "add WMS" button/icon
- a popup/form appears where the user can paste in a WMS URL
- the viewer gets WMS layer info from the server using WMS GetCapabilities (may 
need proxy for this)
- the WMS layers are added to the list/tree of existing layers
- the user can view layers by selecting from the new WMS layers
- a selected layer has the same possibilities as predefined layers, 
transparency, stacking order etc.

Search functionality needed to search for features within the active (wfs) 
layer/theme. The search function is theme aware and creates different WFS 
filter depending on the active theme.

What steps will reproduce the problem?
1. go to any of the examples (except minimal)
2. open an example in Internet Explorer (v6, 7 or 8)
3. to debug open the URL 
http://local.kademo.nl/lib/geoext-viewer/trunk/geoviewer/examples/default/index-
debug.html

- What is the expected output? What do you see instead?
Expected to see the example but get JavaScript error "Invalid Argument" from 
OpenLayer Util.js function Uti.modifyDOMElement line 194. The problem is that 
the argument "px" (position of tile image) has px.x and px.y with NaN values. 
All other browsers like FF, Chrome, Safari on all platforms (Mac/Win/Linux) do 
not give an error.

- versions used: OpenLayer 2.10 and GeoExt 1.0

The callstack starts when the Heron MapPanel creates a GeoExt MapPanel which 
creates an OpenLayers Map with an array of Layer objects.

I suspect that something in the Map options and or CSS or the order of 
initialization/rendering  causes the position "px" to have NaN values.Map 
options are:

map_options = {
    projection: 'EPSG:28992',
    units: 'm',
    resolutions: [860.160, 430.080, 215.040, 107.520, 53.760, 26.880, 13.440, 6.720, 3.360, 1.680, 0.840, 0.420, 0.210, 0.105, 0.0525],
    maxExtent: '-65200.96,242799.04,375200.96,683200.96',
    center: '155000,463000',
    xy_precision: 3,
    zoom: 2,
        layers: [...] // valid OL Layer object array
};

When creating the GeoExt MapPanel these options and a Layer array, GeoExt 
MapPanel creates the OL Map. The error comes from within the Map constructor.

The call sequence is about:
  new Map()
    addLayers()
      addLayer()
        this.setBaseLayer (Map.js line: 936)
          this.baseLayer.setVisibility(true) (line 1133)
           this.redraw() (Layer.js 694)
             this.moveTo() (527)
               this.initGriddedTiles (Grid.js 192)
                 this.spiralTileLoad() (431)
                   tile.draw() (513)
                     this.renderTile (Image.js 237)
                      this.positionImage() (308)
                         call Util.modifyDOMElement() (326)
                            Util.modifyDOMElement() (Util.js 194) ERROR

The context is: where px.x and .y are NaN
OpenLayers.Util.modifyDOMElement = function(element, id, px, sz, position,
188 border, overflow, opacity) {
189
190 if (id) {
191 element.id = id;
192 }
193 if (px) {
194 element.style.left = px.x + "px";
195 element.style.top = px.y + "px";
196 }
197

This issue is critical since this basically means that the current (trunk) 
version will not work in IE.

This is a knwon issue in GeoExt: somehow when layers are defined and beofore 
they are visible GetLegendPanel requests are fired. Als on every other 
requests. 

To reproduce: open any viewer app with Firebug enabled and watch the 
GetLegendPanel's drop by...Check also in GeoExt dev if/how this is fixed...

Research the extJS way of i18n and implement it

Would it be possible to generate dynamic search functionality:

- Search a WFS layer using ogc filter technology
- vendor specific: using ogc filter and cql filter on geoserver wms
- others

Search would have to be a generic implementation that needs to be modular and 
can be enhanced for future standards.

The current OpacitySlider implementation only allow values from 0-100%. Try to 
see and implement values greater than 100% that would make a layer sharper and 
stand out.

If this is at all possible.

Make it possible to select a layer (or a group layers in a theme) to become 
active.  
Provide visual feedback for the user. eg. add font-weight: bold to .x-tree-node 
.x-tree-selected

The esdin example produces several uncaught exceptions in firefox (and other 
browsers).
uncaught exception: [Exception... "Component returned failure code: 0xc1f30001 
(NS_ERROR_NOT_INITIALIZED) [nsIXMLHttpRequest.send]" nsresult: "0xc1f30001 
(NS_ERROR_NOT_INITIALIZED)" location: "JS frame :: 
http://openlayers.org/api/OpenLayers.js :: anonymous :: line 1150" data: no]

This seems to be a namespace related issue. Which might explain why the GML 
3.2.1 fix for vanilla OpenLayers doesn't work on the geoviewer

What steps will reproduce the problem?
1. Use slider and release
2. Map doesn't show at full size in IE7
3. Mouseclick on map
4. Now the map appears and layers get loaded

What is the expected output? What do you see instead?
Map should respond immediately to slider action

The SearchPanel is now very minimal. When searching the user has no idea if the 
system is busy or hangs or whatever. Especially when there are zero results 
nothing happens. What needs to be provided is:

- a clarification that only exact search is possible (at the moment)
- feedback like a "Searching..." message indication
- feedback when zero results are found
- feedback with multiple results

The exmple "site" (under examples) demonstrates how to build an entire 
website/portal using extra Ext functionality like menu's and dynamic HTML 
loading. In effect many sites use this as thier core function: http://kademo.nl 
and htttp://inspire.kademo.nl.

So this task is to move this functionality to the core library. At the same 
time it needs to be generalized and improved. for example the page 
loading/switching is buggy in many browsers (weird text overflow behaviour) and 
resizing a text page will not resize the Map. All in all it needs to be better 
integrated in the current config framework and with the Map widgets.

The current (GeoExt) LegendPanel tries to display legends for _all_ Layers 
fetching them via a WMS GetLegendGraphic. The problem is that a WMS-layer may 
not have a legend graphic, for example a raster layer, or layer group in 
GeoServer. This gives many error messages in the server log.

What steps will reproduce the problem?
1. configure a layer without a legend
2. configure a LegendPanel
3. observe 404 messages from server

What is the expected output? What do you see instead?
Somehow we should be able to indicate that there is no legend for an 
(OpenLayers) Layer object.

Currently the geoviewer only supports wms getFeatureInfo. For INSPIRE we need 
to support WFS features. It would be nice to use the I-tool to transparantly do 
a WMS getFeatureInfo request in case there is a WMS layer or a WFS get Feature 
request when there is a WFS layer.

mainpanel.js shouldn't do this

1- all examples and apps now use GeoExt 0.7, but GeoExt 1.0 is available for 
some time
2- if you use the hosted version use this URL: 
http://kademo.nl/lib/geoext/1.0/GeoExt-min.js
3- affects all examples and apps, now mainly i18s.js and MapPanel.js
but extensive testing is required to find possibly broken functionality.

What and Why
1. In order to harvest and view layers from a WMS a new configuration and
view option should be added that allows the self-configuration of
layers through a WMS GetCapabilities Request. This enhancement allows for
quick and future-proof (when WMS layers change or are added) layer
configuration.

Scenarios
2. Developers only need to configure a WMS URL. When initialized with
remote layers the end-user can immediately browse and view all WMS layers.

New and Affected Components
3. A new Layer container is needed and an extension to the configuration
system that recognizes this component.

Note: this feature is basically equal to the "WMSCapabilityBrowser" from the 
RVOB project fase1.

Create a tooltip for each layer with additional information on the layer

What and Why
1. In order to harvest and view layers from a WMS a new configuration and
view option should be added that allows the self-configuration of
layers through a WMS GetCapabilities Request. This enhancement allows for
quick and future-proof (when WMS layers change or are added) layer
configuration.

Scenarios
2. Developers only need to configure a WMS URL. When initialized with
remote layers the end-user can immediately browse and view all WMS layers.

New and Affected Components
3. A new Layer container is needed and an extension to the configuration
system that recognizes this component.

Note: this feature is basically equal to the "WMSCapabilityBrowser" from the 
RVOB project fase1. See attachment.

Note: examples of this component may also be found in GeoExt itself.

Make the toolbar configurable to allow the user/dev to choose which tools are 
available

What steps will reproduce the problem?
1. select a layer in ActiveLayersPanel
2. change opacity e.g. to 75
3. select another layer into ActiveLayersPanel

- What is the expected output? What do you see instead?
The last layer should have 100% opacity but takes over the value from the first 
layer.

Please use labels and text to provide additional information.

Create a function to save the features in the client to disk.

Note: this issue in IE-only but very annoying.

What steps will reproduce the problem?
1. use the examples/site
2. try using an <iframe> as content html
3. observe that the iframe does not fill the page in IE6+ 

What is the expected output? What do you see instead?
The frame should fill the available window height. This is 
a knwon issue in IE.

Please use labels and text to provide additional information.
Possible solution is to use ExtJS ManagedIFrame ux: 
http://www.sencha.com/learn/Extension:ManagedIframe

Other solutions on the net show JS onload hacks that resize the iframe onload 
and window resize but this is less ideal.

best is that the Pages object in the "site" example is aware of IFrames and 
loads/resizes the iframe, possibly using ManagedIFrame.

Add an extra toolbar-icon to zoom to the extent of the active layer

1. Most JavaScript libraries provide a "minified" version of all JavaScript in 
a single .js file. This enhancement should provide such a script 
similar to what GeoExt, OpenLayers and other frameworks have. Also a 
"debug-version" should be provided in such a build. This is also a step to 
create a downloadable version version of the entire product. 

Currently the geoext-viewer is depending on GeoExt 0.7

What steps will reproduce the problem?
1. Open http://inspire.kademo.nl in Internet Explorer 6
2. You will get a blanc page
3. The Internet Explorer 6 error is: 
    Line: 24, Char: 1, Error: OpenLayers is 'undefined'

What is the expected output? What do you see instead?
Expecting to see a web-gis client, instead see a blanc page

What version of the product are you using? On what operating system?
Internet Explorer 6.0.3790.3959 on Windows 2003 through Citrix client

Provide a user-interaction for defining at least a print-area in the map and 
possibly other parameters such as resolution. The print result should be a PDF 
returned to the user.

Use the facilities of [http://geoext.org GeoExt] printing as much as possible. 
This feature will also need a server side component, most likely candidate is 
[http://mapfish.org MapFish] printing.

Provide a combobox for the map toolbar to be able to search for names and based 
on a name found that zooms the map. 
See the GeoExt UX example. Maybe this can be used as-is.
http://trac.geoext.org/browser/extensions/geoext.ux/ux/GeoNamesSearchCombo/lib/G
eoExt.ux/GeoNamesSearchCombo.js

Also a PoC has been done with Nominatim, see ToolBarBuilder.js and the example 
on
http://local.kademo.nl/lib/geoext-viewer/trunk/heron/examples/namesearch

Currently for i18n to function properly, a specific
language file needs to be included in the JS section of the
html file. 

In order to reduce the number of JS files and have just obe Heron.js single 
file or DynLoader.js make a default language that can be overridden where 
required. 

The aim is to require the minimum number of JS files to include for the default 
case.

In the current state end-user developers can only use the viewer library by 
downloading the trunk version from SVN. 

This enhancement should deliver a script that takes the entire product and 
builds a version as a .zip/.tar.gz such that it can be made available for 
download. 

What steps will reproduce the problem?
1. open the examples/site/index.html
2. navigate to a (non-Map) content Panel via menu
3. resize the browser window and navigate back to the Map

What is the expected output? 
- that the Map is resized as well

What do you see instead?
- the Map is not resized properly


Please use labels and text to provide additional information.
- when on the Map Panel, resizing works ok. Only if the window is resized
from another standard HTML content Panel (via menu) does the Map Panel fail to 
resize. 

Add the option to create groups of layers (themes) in the layer browser.

What steps will reproduce the problem?
1. Request feature info for a layer
2. Find a field that contains "http://some-server.com/some-url"
3. The links do not become click able

What is the expected output? What do you see instead?

Automatically generate a hyperlink

In order to minimize the number of JS files to include and since most heron 
apps use the Launcher.js, that file is to be included in the single file 
Heron.js and the DynLoader.js . In order to still be able to explicitly create 
and render Heron components, supply a mechanism by including a JS file 
NoLaunch.js that surpresses autolaunching.

Also provide an example how to use NoLaunch.js This is also handy for the 
documentation example (with button).

In the current stylesheets, a lot of resources are hardcoded against 
http://kademo.nl

Need to remove this dependency

What steps will reproduce the problem?
1.Click the ( i ) button
2.Click on the map
3.The featureinfo panel opens if you clicked on multiple objects and shows a 
grid with multiple results
4. Left click on the down arrow next to a column title, a pulldown opens 
showing three options: Sort ascending, Sort descending and Columns
5. Sort ascending and sort descending are grayed out making it impossible to 
sort

What is the expected output? What do you see instead?

I would like to be able to sort ascending or descending on a given column.

We need to be able to define themes (for example INSPIRE Annex I themes) and 
assign a theme to a WFS layer.

A theme can have the following properties:
1) A name
2) A set of feature types (i.e. feature types that are relevant)
3) A set of fields per feature type (for display in the data grid)