2011/12/30 Armin Burger :
>> changes in order to do what I was looking for ie. adding support for
>> custom (human-readable) column names and definition in query results
>> based on layer's metadata.
>
>
> in case you haven't found it yet, the column names can be defined in the
> metadata for each
> changes in order to do what I was looking for ie. adding support for
> custom (human-readable) column names and definition in query results
> based on layer's metadata.
in case you haven't found it yet, the column names can be defined in the
metadata for each layer using the tag "RESULT_HEADERS
2011/12/29 Armin Burger :
> Francois
>
> in order to use the non-compressed JS files you need to define the path
> in the config XML to
> javascript/src
> Which will then use the single files from the "src" dir.
That's perfect Armin, thanks.
> The "compression" of the files was done with a PHP sc
Francois
in order to use the non-compressed JS files you need to define the path
in the config XML to
javascript/src
Which will then use the single files from the "src" dir.
The "compression" of the files was done with a PHP script from the
utilities folder, now not any more included in the r
Hi list, I'm new to p.mapper and I was looking for a way to update
some JS files (at least pm.query.js) and then check my changes.
I did not find a way to run p.mapper in "debug" mode using the plain
JS instead of the merged one.
Is there any parameters to use plain JS or any utilities to create t
