Opened 14 years ago

Last modified 12 years ago

#146 new task

GeoPrisma proxy - used to get core element informations

Reported by: adube Owned by:
Priority: minor Milestone: 1.8.0
Component: server Version: trunk
Keywords: bis-1.8.0 Cc:

Description

requires : #145

task

Create a new proxy to access the GeoPrisma core elements themselves. Such a proxy would allow requests returning core informations (in JSON).

For example, if we wanted to plug an external lib to GeoPrisma and would want to let it know all the widget types available, we would have something like :

http://host/geoprisma/proxy?osmservice=__geoprisma__&osmprocess=getWidgetTypes

that would return the list of widget types supported by GeoPrisma in JSON.

Here's an other example : get all widget possible options.

http://host/geoprisma/proxy?osmservice=__geoprisma__&osmprocess=getWidgetOptions

That would return all possible widget options with their possible values as well (again in JSON).

to do

In order to be able to do so, each elements would required to be listed somehow in the core elements (in php). Here's the list of elements :

  • service :
  • resource
  • fields
  • mapcontext
  • widget

In each core files, there would be new methods exclusively used for returning these values (i.e. not used by the code). For some elements (such as resources and fields), they would be defined inside the .php files of the widgets. The mapcontext would use the 'map' widget options. Some resource options would use the map 'layers' options.

Change History (7)

comment:1 by adube, 14 years ago

Summary: GeoPrisma proxy to get core element informationsGeoPrisma proxy - used to get core element informations

comment:2 by adube, 13 years ago

Milestone: 1.2.0

comment:3 by adube, 12 years ago

See if that could be used by Borealis as a way to communicate with GeoPrisma.

comment:4 by adube, 12 years ago

Keywords: bis-1.2.0 added

comment:5 by adube, 12 years ago

Keywords: bis-1.4.0 added; bis-1.2.0 removed
Milestone: 1.2.01.4.0
Version: trunk

No patch, pushed to 1.4.

comment:6 by adube, 12 years ago

Keywords: bis-1.6.0 added; bis-1.4.0 removed
Milestone: 1.4.01.6.0

No patch, pushed to 1.6.

comment:7 by adube, 12 years ago

Keywords: bis-1.8.0 added; bis-1.6.0 removed
Milestone: 1.6.01.8.0

No patch, pushed to 1.8.

Note: See TracTickets for help on using tickets.