[mapserver-dev] RFC 102: Styleitem Javascript Plugin

[Umberto Nicoletti]

Interesting.
As Steve said one attractive use of a scripting engine embedded in
mapserver could be in dynamic query templates.

Alan, was there a particular reason for choosing V8 instead of other
engines like LUA?

Umberto


On Mon, Aug 19, 2013 at 7:52 PM, Lime, Steve D (MNIT) <
Steve.Lime at state.mn.us> wrote:

> I remember chatting about this a bit at FOSS4G-NA. Javascript has such
> broad support these days it seems a reasonable choice for an embedded
> language. Could presumably consider others. Have you actually got this
> integration working even in just a simple way? I'd be interested in seeing
> code. I could see templates evolving this way. That is, we expose the
> result set and other query/render time values. With the other potential
> uses out there we should make sure exposing objects can be done using a
> standard syntax.
>
> Steve
>
> ________________________________________
> From: mapserver-dev-bounces at lists.osgeo.org [
> mapserver-dev-bounces at lists.osgeo.org] on behalf of Alan Boudreault [
> aboudreault at mapgears.com]
> Sent: Monday, August 19, 2013 12:27 PM
> To: thomas bonfort
> Cc: mapserver-dev at lists.osgeo.org
> Subject: Re: [mapserver-dev] RFC 102: Styleitem Javascript Plugin
>
> All,
>
> - V8 allows us to embed a javascript interpretor in an application. It
> implements ECMAScript 5th edition and runs on Windows, Mac and Linux.
>
> The idea behind its addition is to have a scripting language to
> implement various plugins. The one suggested here is a plugin that
> generates styles, but we could imagine some other use cases: ie. a new
> datasource that return the shape object from a javascript plugin or
> maybe the ability to use a javascript plugin to extend the geomtransform
> for a specific case.
>
> V8 provide an embeded javascript engine (syntax, interpretation,
> execution) and it is absolutely not related to anything *client-side*
> (browser). So no, it is not needed for scribeUI.
>
> - The shapeObj will be exposed as a wrapper created for the v8 engine. I
> will only expose shape attributes for this RFC. A new rfc will be
> written later for a *complex symbology plugin* and the geometry will be
> expose for this need.
>
> - nothing to push in a branch yet
>
> On 13-08-19 12:50 PM, thomas bonfort wrote:
> > Alan,
> > - For those of us who haven't followed up closely on the v8 engine and
> > its possibilities, could you expand your RFC or follow up here with
> > some use-cases where this would be used in mapserver? Is this
> > something that is needed for scribeUI?
> > - How and what do you plan on exposing of a shapeObj to V8? Direct
> > member access or wrappers? Will you expose only attributes or also
> > geometry?
> > - You seem to have some or most of the code ready? Can you push your
> > branch publicly?
> >
> > thanks,
> > Thomas
> >
> > On 19 August 2013 18:17, Alan Boudreault <aboudreault at mapgears.com>
> wrote:
> >> Devs,
> >>
> >> Please take a look at RFC 102 which propose the addition of a styleitem
> >> javascript plugin as an alternative to style our features.
> >>
> >> http://mapserver.org/development/rfc/ms-rfc-102.html
> >>
> >> I'll be calling for vote on it next week.
> >>
> >> Thanks,
> >> Alan
> >>
> >> --
> >> Alan Boudreault
> >> http://www.mapgears.com/
> >> _______________________________________________
> >> mapserver-dev mailing list
> >> mapserver-dev at lists.osgeo.org
> >> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
>
> --
> Alan Boudreault
> http://www.mapgears.com/
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
>
> _______________________________________________
> mapserver-dev mailing list
> mapserver-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/mapserver-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/mapserver-dev/attachments/20130820/9c6da9ee/attachment.html>