[pmapper-users] A couple of questions...
Hi all Is it possible to make a block of text/image etc dependent on the active (visible/ticked) layers on the screen? I.e.pseudo watermarking. Also I am using the searchtool plugin for searches and wondered if there is a way to either keep the selected search option selected in the drop-down list or populate a html tag with the relevant search option name? At the moment you select an option and get the input fields, but are reliant on the field labels for describing what you may have chosen. On that note can you use default values in parameter fields? Many thanks Chris -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
Re: [pmapper-users] A couple of questions...
Hi, Responses below Le 10/05/2011 14:28, Chris Jackson a écrit : Hi all Is it possible to make a block of text/image etc dependent on the active (visible/ticked) layers on the screen? I.e.pseudo watermarking. LAYER NAME credits REQUIRES ([layer1] AND ![layer2]) STATUS DEFAULT TRANSFORM lr TYPE ANNOTATION FEATURE POINTS -40 -2 END TEXT 'blabla' END CLASS LABEL ... END END END Also I am using the searchtool plugin for searches and wondered if there is a way to either keep the selected search option selected in the drop-down list or populate a html tag with the relevant search option name? At the moment you select an option and get the input fields, but are reliant on the field labels for describing what you may have chosen. On that note can you use default values in parameter fields? I'm not sure to understand what you mean. The searchtool plugin only show the form that is by default included in the main pmapper page. Could you sent me more explanations maybe with screenshots please? Many thanks Chris -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
Re: [pmapper-users] A couple of questions...
Le 10/05/2011 15:39, Chris Jackson a écrit : Hi Thomas Thanks for the response, I guessed the mapfile method was one way, though does the layer always appear on the screen irrespective of zoom (i.e. floats top left of map port - like GMap/earth APIs)? Haven't got it to work yet but will get back to it. I noticed grouping the layer with the respective watermark seems to be another way - again I wasn't sure how the watermark element was positioned on the screen. I think it is the way to add watermarks with mapserver. As the layer has the TRANSFORM tag is will be drawn in this example at the lower right position, relative to the map image. In the FEATURE part, it is the offset to place it correctly. The REQUIRE is optional and allow to show different credits informations depending on activated layers. The STATUS has to be DEFAULT and the layer not listed in pmapper groups. Look at the mapfile doc here for more details : http://mapserver.org/mapfile/index.html#mapfile As for the search side of things - attached is a screenshot of the search window after I selected the first search from the drop-down list, as you can see no visual clue to which search I selected (you can guess it is related to spring peak flow from the field label). It would be good to either mod the drop-down list so the selected search is still highlighted (not the phrase 'search for') or just push the search descriptor into an empty span tag. OK! I have already done it. I will check the changes you have to made for that. What I also wanted to do was pre-populate the inputs with values too - can this be done in the within the search xml? I think this point will require specific development because it is not already implemented. If you plan to do it, please make a plugin. So I could try to integrate it in the QueryEditor plugin. Many thanks Chris On 10 May 2011 13:41, Thomas RAFFIN traf...@sirap.fr mailto:traf...@sirap.fr wrote: Hi, Responses below Le 10/05/2011 14:28, Chris Jackson a écrit : Hi all Is it possible to make a block of text/image etc dependent on the active (visible/ticked) layers on the screen? I.e.pseudo watermarking. LAYER NAME credits REQUIRES ([layer1] AND ![layer2]) STATUS DEFAULT TRANSFORM lr TYPE ANNOTATION FEATURE POINTS -40 -2 END TEXT 'blabla' END CLASS LABEL ... END END END Also I am using the searchtool plugin for searches and wondered if there is a way to either keep the selected search option selected in the drop-down list or populate a html tag with the relevant search option name? At the moment you select an option and get the input fields, but are reliant on the field labels for describing what you may have chosen. On that note can you use default values in parameter fields? I'm not sure to understand what you mean. The searchtool plugin only show the form that is by default included in the main pmapper page. Could you sent me more explanations maybe with screenshots please? Many thanks Chris -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net mailto:pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net mailto:pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay
Re: [pmapper-users] A couple of questions...
Here are the changes for search behaviour that have to be done in
javascript/pm.search.js.
- to keep the selected value, replace the setSearchInput method with
this one:
setSearchInput: function() {
var searchForm = _$('searchForm');
// Modified by Thomas RAFFIN (SIRAP)
// to change the searchbox behaviour (reset the fields)
/*
var searchitem =
searchForm.findlist.options[searchForm.findlist.selectedIndex].value;
var url = PM_XAJAX_LOCATION + 'x_search.php?' + SID
+'action=searchitemsearchitem=' + searchitem;
_$('searchForm').findlist.options[0].selected = true; // reset
parent select box to Search for...
this.createSearchItems(url);
*/
if (searchForm.findlist.selectedIndex == 0) {
$('#searchitems').html('');
_$('searchForm').findlist.options[0].selected = true; //
reset parent select box to Search for...
} else {
var searchitem =
searchForm.findlist.options[searchForm.findlist.selectedIndex].value;
var url = PM_XAJAX_LOCATION + 'x_search.php?' + SID
+'action=searchitemsearchitem=' + searchitem;
//alert(url);
this.createSearchItems(url);
}
},
- to reset the value with the cross button, replace
onclick=$(\'#searchitems\').html(\'\')
with
onclick=$(\'#searchitems\').html(\'\');_$(\'searchForm\').findlist.options[0].selected
= true;
If you are using compress js files, don't forget to compress them...
Le 10/05/2011 15:59, Thomas RAFFIN a écrit :
Le 10/05/2011 15:39, Chris Jackson a écrit :
Hi Thomas
Thanks for the response, I guessed the mapfile method was one way,
though does the layer always appear on the screen irrespective of zoom
(i.e. floats top left of map port - like GMap/earth APIs)? Haven't
got it to work yet but will get back to it. I noticed grouping the
layer with the respective watermark seems to be another way - again I
wasn't sure how the watermark element was positioned on the screen.
I think it is the way to add watermarks with mapserver.
As the layer has the TRANSFORM tag is will be drawn in this example at
the lower right position, relative to the map image. In the FEATURE
part, it is the offset to place it correctly.
The REQUIRE is optional and allow to show different credits
informations depending on activated layers. The STATUS has to be
DEFAULT and the layer not listed in pmapper groups.
Look at the mapfile doc here for more details :
http://mapserver.org/mapfile/index.html#mapfile
As for the search side of things - attached is a screenshot of the
search window after I selected the first search from the drop-down
list, as you can see no visual clue to which search I selected (you
can guess it is related to spring peak flow from the field label). It
would be good to either mod the drop-down list so the selected search
is still highlighted (not the phrase 'search for') or just push the
search descriptor into an emptyspan tag.
OK! I have already done it. I will check the changes you have to made
for that.
What I also wanted to do was pre-populate the inputs with values too -
can this be done in the within the search xml?
I think this point will require specific development because it is not
already implemented. If you plan to do it, please make a plugin. So I
could try to integrate it in the QueryEditor plugin.
Many thanks
Chris
On 10 May 2011 13:41, Thomas RAFFINtraf...@sirap.fr
mailto:traf...@sirap.fr wrote:
Hi,
Responses below
Le 10/05/2011 14:28, Chris Jackson a écrit :
Hi all
Is it possible to make a block of text/image etc dependent on
the active
(visible/ticked) layers on the screen? I.e.pseudo watermarking.
LAYER
NAME credits
REQUIRES ([layer1] AND ![layer2])
STATUS DEFAULT
TRANSFORM lr
TYPE ANNOTATION
FEATURE
POINTS
-40 -2
END
TEXT 'blabla'
END
CLASS
LABEL
...
END
END
END
Also I am using the searchtool plugin for searches and wondered
if there is
a way to either keep the selected search option selected in the
drop-down
list or populate a html tag with the relevant search option
name? At the
moment you select an option and get the input fields, but are
reliant on the
field labels for describing what you may have chosen. On that
note can you
use default values in parameter fields?
I'm not sure to understand what you mean. The searchtool plugin only
show the form that is by default included in the main pmapper page.
Could you sent me more explanations maybe with screenshots please?
Many thanks
Chris
Re: [pmapper-users] A couple of questions...
Hi Thomas Makes sense. Thanks for the code works well, note - one of the // in the code below is on the wrong line. As for taking the pre-populated values further - I am not codey (clever) enough for that, I am guessing you could extend the search xml/xsd side of things to take more information. I already have a little Aide-mémoire table of min/max values for users so will use that for now and hardwire a link to it in the search form! Cheers for the help, much appreciated. Chris On 10 May 2011 14:59, Thomas RAFFIN traf...@sirap.fr wrote: Le 10/05/2011 15:39, Chris Jackson a écrit : Hi Thomas Thanks for the response, I guessed the mapfile method was one way, though does the layer always appear on the screen irrespective of zoom (i.e. floats top left of map port - like GMap/earth APIs)? Haven't got it to work yet but will get back to it. I noticed grouping the layer with the respective watermark seems to be another way - again I wasn't sure how the watermark element was positioned on the screen. I think it is the way to add watermarks with mapserver. As the layer has the TRANSFORM tag is will be drawn in this example at the lower right position, relative to the map image. In the FEATURE part, it is the offset to place it correctly. The REQUIRE is optional and allow to show different credits informations depending on activated layers. The STATUS has to be DEFAULT and the layer not listed in pmapper groups. Look at the mapfile doc here for more details : http://mapserver.org/mapfile/index.html#mapfile As for the search side of things - attached is a screenshot of the search window after I selected the first search from the drop-down list, as you can see no visual clue to which search I selected (you can guess it is related to spring peak flow from the field label). It would be good to either mod the drop-down list so the selected search is still highlighted (not the phrase 'search for') or just push the search descriptor into an empty span tag. OK! I have already done it. I will check the changes you have to made for that. What I also wanted to do was pre-populate the inputs with values too - can this be done in the within the search xml? I think this point will require specific development because it is not already implemented. If you plan to do it, please make a plugin. So I could try to integrate it in the QueryEditor plugin. Many thanks Chris On 10 May 2011 13:41, Thomas RAFFIN traf...@sirap.fr mailto:traf...@sirap.fr wrote: Hi, Responses below Le 10/05/2011 14:28, Chris Jackson a écrit : Hi all Is it possible to make a block of text/image etc dependent on the active (visible/ticked) layers on the screen? I.e.pseudo watermarking. LAYER NAME credits REQUIRES ([layer1] AND ![layer2]) STATUS DEFAULT TRANSFORM lr TYPE ANNOTATION FEATURE POINTS -40 -2 END TEXT 'blabla' END CLASS LABEL ... END END END Also I am using the searchtool plugin for searches and wondered if there is a way to either keep the selected search option selected in the drop-down list or populate a html tag with the relevant search option name? At the moment you select an option and get the input fields, but are reliant on the field labels for describing what you may have chosen. On that note can you use default values in parameter fields? I'm not sure to understand what you mean. The searchtool plugin only show the form that is by default included in the main pmapper page. Could you sent me more explanations maybe with screenshots please? Many thanks Chris -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters. http://p.sf.net/sfu/intel-dev2devmay ___ pmapper-users mailing list pmapper-users@lists.sourceforge.net mailto:pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users -- Achieve unprecedented app performance and reliability What every C/C++ and Fortran developer should know. Learn how Intel has extended the reach of its next-generation tools to help boost performance applications - inlcuding clusters.
