[Chameleon] Non-WMS Contexts?

[Roland Martin]

Hi,

Thanks for your reply. I think you misunderstood what I'm looking for -
right now I'm not interested in producing OGC compliant XML; simply in
saving the user's extent and layer settings. Since both this and the context
widgets effectively do the same thing (just producing different output), I
assumed most of the code would be there already.

Unfortunately, as always I was having a bit of difficulty untwining the
widget coding, which is why I sent the message out to the list...

Looking at it now it's starting to look as though the relevant bits are
embedded in MapScript, so I might be onto a lost cause anyway...

Cheers,
Roland.


On 27/06/06, Kralidis,Tom [Burlington] <Tom.Kralidis at ec.gc.ca> wrote:
>
>
> WMS context is designed only for OGC:WMS type connections.  OWSContext
> (draft OGC paper out later this year hopefully) covers OGC:WFS, OGC:WCS,
> OGC:GML, etc.  In either case, both approaches work on HTTP accessible data,
> not local filesystem, etc.
>
> Having said this, you can serve your local data as OGC:WMS and have it
> accessible that way?
>
>
>         -----Original Message-----
>         From: chameleon-bounces at lists.maptools.org on behalf of Roland
> Martin
>         Sent: Tue 27-Jun-06 11:21
>         To: chameleon at lists.maptools.org
>         Cc:
>         Subject: [Chameleon] Non-WMS Contexts?
>
>
>         Hi,
>
>         Is there an equivalent of the DownloadContext/UploadContext for
> locally hosted data? i.e. something that allows users to save their
> current extent & layer settings and return to them later?
>
>         If not, how might one go about adapting the existing code?
>
>         Ta,
>         Roland.
>
>
>


-- 
Please note my new email address. Use other addresses at your peril.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.maptools.org/pipermail/chameleon/attachments/20060627/0a88716a/attachment.html