Sorry for the previous message (difficult to read)...
Hi people, thanks for all.
I'm not able to solve the problem, I just tried to interpret a little the
widgetBaseXSL code (see below). Is this interpretation right?
And how should we modify it (did you get it, Denton?) without disturbing
other widgets? I just tried a few things and a lot of problems raised
suddenly!
I think it's not a problem of using getFeatureInfo but it's a problem of
code...
Thanks in advance,
var outputNode=document.getElementById(objRef.outputNodeId);
//stores elements with Id (objRef.outputNodeId) in outputNode variable
var tempNode=document.createElement("DIV");
//stores the function of creating DIVs in tempNode variable
var s=objRef.stylesheet.transformNodeToString(objRef.resultDoc);
//stores the result of applying the XSL to GetFeatureInfo result (a
FeatureCollection) in the s variable. Here s=<div><table>... from
featurelist.xsl (you can see that if you use the <debug/> option in
<featureInfo> widget)
if(config.serializeUrl&&objRef.debug)postLoad(config.serializeUrl,s);
if(objRef.debug)alert("painting:"+objRef.id+":"+s);
tempNode.innerHTML=s;
//writes the info (the resulting table after applying XSL) as innerHTML (for
IExplorer)
if(tempNode.firstChild!=null)
//if there is something written previously ( DIV)...
{tempNode.firstChild.setAttribute("id",objRef.outputNodeId);
//we set an Id to the DIV
if(outputNode){
//if we got some outputNode previously (it means we generated previously an
objRef.outputNodeId)...
objRef.node.replaceChild(tempNode.firstChild,outputNode);
//we put a new child replacing the old one (outputNode)
}else{ //there was nothing
objRef.node.appendChild(tempNode.firstChild);
// we add a child
}
Cameron Shorter wrote:
>
> Yes, if the code is functional, then it would be a good idea to write a
> tutorial. Thankyou for offering.
>
> The best place for the tutorial would be linked from:
> http://communitymapbuilder.org/display/MAP/Tutorials probably under
> "Extending Mapbuilder".
>
>
> [EMAIL PROTECTED] wrote:
>> Hi Cameron,
>>
>> you said it right!! To avoid the attaching of the new GetFeatureInfo
>> result behind the previous one, it is absolutelly sufficient to change
>> the code in the WidgetBaseXSL.js code, because new GetFeatureInfo HTML is
>> being used as the parameter of the appendChild method instead of
>> replaceChild method. But in my opinion it would be better to provide to
>> mapbuilder users easy tutorial "howto customize FeatureInfo output" ,
>> because as you can see many users have absolutelly no idea how it is
>> working...
>>
>> If you will send me a link where I can post the presentation, I will
>> prepare someting, if you dont mind...;-)
>>
>> regards Denton..
>>
>>
>>
>>
>>
>>
>
>
> --
> Cameron Shorter
> Systems Architect, http://lisasoft.com.au
> Tel: +61 (0)2 8570 5050
> Mob: +61 (0)419 142 254
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> mapbuilder-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
>
>
--
View this message in context:
http://www.nabble.com/Re%3A-simple-getFeatureInfo-question-tf3868457.html#a10972744
Sent from the MapBuilder Devel mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
mapbuilder-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mapbuilder-devel
