Re: [pmapper-users] roadmap and acl

2012-03-17 Thread G. Allegri 
>
>
>>> well, there are frameworks like GeoExt that might already have offered
>> this type of functionality. Did you ever try them?
>
>
> As you know, GeoExt is more a client viewer, decouled by the server side.
> What I like in Pmapper is the integrated environment, where with few
> configurations you obtain a full-featured system (client+server).
> Having an admin API would allow the configuration to be made through a web
> based UI, or even a desktop app. This would simplify/streamline the process
> of setting up and deploying maps and services for the end-user.
>

PS: and I love jQuery lot more then ExtJS! :)

About the OL integration, it could also permit to the use of external
services, like ArcGIS Server, Geoserver, etc. on top of the MS based
services. A lot of chances more to be welcomed in various application
contexts.

giovanni
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users

Re: [pmapper-users] roadmap and acl

2012-03-17 Thread Serge Claudio Rafanoharana 
Hi Armin,

Great job, and your explanation are very clear...

Serge

On Sat, Mar 17, 2012 at 7:26 PM, Armin Burger  wrote:

>
>
> On 17/03/2012 12:38, G. Allegri wrote:
> > Having an admin API would allow the configuration to be made through a
> web
> > based UI, or even a desktop app. This would simplify/streamline the
> process
> > of setting up and deploying maps and services for the end-user.
>
>
> Hi Giovanni
>
> I find the management of the map file and all layers, with classes,
> symbols, etc the most time consuming part. Setting up a GUI for that
> would require quite a bit of work. Maybe you could give a look at the
> QGIs plugin and just modify it to add some specific settings for
> p.mapper (mainly the query fields and result headers under METADATA).
> Another web-based map file creator was never really finished.
>
> I once set up an extension for ArcView 3 for this but I guess not many
> people are still using it.
>
> The configuration style for p.mapper 5 will be more or less similar to
> the previous version. Originally I wanted to move more config settings
> from the XML to the js_config file since I'm now more used to writing
> JSON like notations. But I mainly left it in the way it was. So the most
> important settings to be changed typically for every application remain
> in the XML. The category/group definition can be a bit more difficult
> now in order to allow more complex set up, there were some compromises
> necessary to put everything in XML. An example is e.g
>
> 
> countries
> cities1eu
> 
> 
>description="Infrastructure" type="PMTile">
> roads
> railroad
> 
>
> Settings that are very OL-oriented are in Javascript since it allows to
> directly use OL-generic properties and options. But since this is
> de-facto JSON, it should be possible to write this also somehow via a GUI.
>
> armin
>
>
>
>
>
> --
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> ___
> pmapper-users mailing list
> pmapper-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>



-- 
Serge
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users

Re: [pmapper-users] roadmap and acl

2012-03-17 Thread Armin Burger 


On 17/03/2012 12:38, G. Allegri wrote:
> Having an admin API would allow the configuration to be made through a web
> based UI, or even a desktop app. This would simplify/streamline the process
> of setting up and deploying maps and services for the end-user.


Hi Giovanni

I find the management of the map file and all layers, with classes, 
symbols, etc the most time consuming part. Setting up a GUI for that 
would require quite a bit of work. Maybe you could give a look at the 
QGIs plugin and just modify it to add some specific settings for 
p.mapper (mainly the query fields and result headers under METADATA). 
Another web-based map file creator was never really finished.

I once set up an extension for ArcView 3 for this but I guess not many 
people are still using it.

The configuration style for p.mapper 5 will be more or less similar to 
the previous version. Originally I wanted to move more config settings 
from the XML to the js_config file since I'm now more used to writing 
JSON like notations. But I mainly left it in the way it was. So the most 
important settings to be changed typically for every application remain 
in the XML. The category/group definition can be a bit more difficult 
now in order to allow more complex set up, there were some compromises 
necessary to put everything in XML. An example is e.g


 countries
 cities1eu
 


 roads
 railroad


Settings that are very OL-oriented are in Javascript since it allows to 
directly use OL-generic properties and options. But since this is 
de-facto JSON, it should be possible to write this also somehow via a GUI.

armin




--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users

Re: [pmapper-users] roadmap and acl

2012-03-17 Thread G. Allegri 
Thanks Armin for these notes. I reply inline:


>> well, there are frameworks like GeoExt that might already have offered
> this type of functionality. Did you ever try them?


As you know, GeoExt is more a client viewer, decouled by the server side.
What I like in Pmapper is the integrated environment, where with few
configurations you obtain a full-featured system (client+server).
Having an admin API would allow the configuration to be made through a web
based UI, or even a desktop app. This would simplify/streamline the process
of setting up and deploying maps and services for the end-user.


>
>
>  Armin, do you have any plans about it? Will you put it out when things are
>> done, or will you share the code while working on it?
>>
>
> So far quite some parts are still a bit under construction with frequent
> and possibly still deeper changes. It was not always easy to understand the
> sometimes strange logic of OL, and the OL mailing list was of no help for
> very specific questions (I practically never got any reply). So I was
> sometimes close to abandon the idea of using OL. Now I found most ways for
> workarounds, and the map navigation and interaction tools are mainly
> working.
>
> I'm currently in the final stage of rewriting the old and badly structured
> query code of p.mapper, this might be even possible to port it back to the
> p.mapper 4 (the new one will be version 5). The query stuff is again a bit
> of a mess, this time from the side of MapServer. But the new query classes
> should allow more easily to write you own functionality for the query
> result display if needed since this is now decoupled from actually getting
> the query result.
>
> A missing part is also the printing where I will mainly have to
> investigate how to print tiled layers that are not available via Mapserver
> (like OSM layers, Google layers will anyway not be allowed to be included
> in printings).
>
> Just to give an idea how the composition of layers from mapserver and OL
> works: You can define as now to have all MS layers (or groups) being
> rendered on a single map image, with or without tiling. Or you can split
> groups of layers into a few blocks, each block is an OL layer (I call the
> OL layers 'olThemes' to avoid too much of naming confusion). The
> combination which layers are rendered together or separately can be done in
> any type of combination. Using tiled layers for the time being will require
> to use the Google spherical mercator projection for the map. I cerated 2
> new types of new OL layers, one tiled and the other non-tiled. Both are
> based on MapScript and will only work inside a user PHP session.
>
> It will be very likely that the first release version of p.mapper 5 will
> have some very specific functionalities not yet included, and most likely
> also only a few plugins will work already then.
>
> When the code is a bit more stable I will put it on the SVN, depending
> also if anyone is interested in contributing some developments. I might put
> a preliminary beta version out in the next week or so, so that people can
> have a look at it on their own installation.
>
>
Great work. I'm not able to comment your points in this moment, I need to
have a look to the code, but it sounds great!
I hope to have a ride on it soon ;)


> A first draft version (already 2 weeks old) is available at
> http://www.pmapper.net/demo/**pmapper-5-dev/
> http://www.pmapper.net/demo/**pmapper-5-dev/?config=**singletile


OSM within Pmapper! That's what I was longing for ;)

giovanni
--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users

Re: [pmapper-users] TOC - Category with only one layer

2012-03-17 Thread Armin Burger 
On 16/03/2012 16:35, Chris forum wrote:
> Sorry, sent it too fast... here again without errors:
>
> Sometimes there is a category that contains only one layer, e. g. in this
> example:
> http://www.pmapper.net/demo/p42/map_default.phtml?winsize=medium&language=en&config=default
>
> Category: Nature-spatial Data / Layer: Rivers
>
> For cases like that, is there an easy way to only display the layer in the
> tree, in 1 line without the +/-?

There is in my opinion no easy way, I would even say it could be quite 
cumbersome to achieve this. You will need to modify pm.toc.js and 
toc.php and try to understand the logic there. And

>
> That would simplify/shorten the TOC and make it more logical I think.

Which display is more logical than the other depends on the individual 
perception. It took me some time to set it up in the way as it currently 
is since this was what I personally found most intuitive, but of course 
this may vary much... ;-)

> Indeed, if the layer has been collapsed while being deactivated, it is not
> displayed into the map even if the category has got the check mark, which
> could be confusing.

You can deactivate the checkboxes for the categories, this will remove a 
functionality that could be handy, but also a source of confusion.

armin

--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users

Re: [pmapper-users] roadmap and acl

2012-03-17 Thread Armin Burger 
On 16/03/2012 12:50, G. Allegri wrote:
> Hi,
> the idea to use Openlayers could give a new boost to Pmapper, which I find
> one of the best "technical oriented" WebGIS out there.
> This could give a chance to develop more on it. It's a long time I'm
> thinking to an admin API, for an example, but was discouraged to invest on
> it by the lack of some foundamental features for nowday's WebGIS platforms,
> with OL being the biggest.

well, there are frameworks like GeoExt that might already have offered 
this type of functionality. Did you ever try them?

> Armin, do you have any plans about it? Will you put it out when things are
> done, or will you share the code while working on it?

So far quite some parts are still a bit under construction with frequent 
and possibly still deeper changes. It was not always easy to understand 
the sometimes strange logic of OL, and the OL mailing list was of no 
help for very specific questions (I practically never got any reply). So 
I was sometimes close to abandon the idea of using OL. Now I found most 
ways for workarounds, and the map navigation and interaction tools are 
mainly working.

I'm currently in the final stage of rewriting the old and badly 
structured query code of p.mapper, this might be even possible to port 
it back to the p.mapper 4 (the new one will be version 5). The query 
stuff is again a bit of a mess, this time from the side of MapServer. 
But the new query classes should allow more easily to write you own 
functionality for the query result display if needed since this is now 
decoupled from actually getting the query result.

A missing part is also the printing where I will mainly have to 
investigate how to print tiled layers that are not available via 
Mapserver (like OSM layers, Google layers will anyway not be allowed to 
be included in printings).

Just to give an idea how the composition of layers from mapserver and OL 
works: You can define as now to have all MS layers (or groups) being 
rendered on a single map image, with or without tiling. Or you can split 
groups of layers into a few blocks, each block is an OL layer (I call 
the OL layers 'olThemes' to avoid too much of naming confusion). The 
combination which layers are rendered together or separately can be done 
in any type of combination. Using tiled layers for the time being will 
require to use the Google spherical mercator projection for the map. I 
cerated 2 new types of new OL layers, one tiled and the other non-tiled. 
Both are based on MapScript and will only work inside a user PHP session.

It will be very likely that the first release version of p.mapper 5 will 
have some very specific functionalities not yet included, and most 
likely also only a few plugins will work already then.

When the code is a bit more stable I will put it on the SVN, depending 
also if anyone is interested in contributing some developments. I might 
put a preliminary beta version out in the next week or so, so that 
people can have a look at it on their own installation.

A first draft version (already 2 weeks old) is available at
http://www.pmapper.net/demo/pmapper-5-dev/
http://www.pmapper.net/demo/pmapper-5-dev/?config=singletile

some new functions beyond OL integrations already implemented are:
- hierarchical level above categories (called 'domains')
- more flexible mutual disabling of layers

Do not use IE for it since it will complain about some "console.log()" 
calls.

Hope that helps for now

Armin













> Thanks for you precious work,
> Giovanni
> --
> This SF email is sponsosred by:
> Try Windows Azure free for 90 days Click Here
> http://p.sf.net/sfu/sfd2d-msazure
> ___
> pmapper-users mailing list
> pmapper-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/pmapper-users
>


--
This SF email is sponsosred by:
Try Windows Azure free for 90 days Click Here 
http://p.sf.net/sfu/sfd2d-msazure
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users