Hi Jamie.<br><br>You should be able to replace kaLegend with my modified one and then add a few lines in some other files to make it work. There is also a javascript library that handles the hierarchical menu. You'll likely want to play around with your
screen.css to make it look pretty, too. <br><br>Currently there are some bugs that should be worked out before committing it to the code base. For example, moving layers up/down doesn't work. <br><br>I'll attach my modified kaLegend code so you can feel free to use it. I'd be happy to have some help working out the bugs, if you feel so inclined. In the attached archive take a look at the
kaLevendExpandable.js comments at the top that outline the changes you'll have to make to get it working.<br><br>Let me know if you need any help.<br><br>Sam<br><br><br><br><br><br><div><span class="gmail_quote">On 10/31/07,
<b class="gmail_sendername">Jamie</b> <<a href="mailto:jamiee@email.cz">jamiee@email.cz</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Sam,<br>it's an excellent idea. Organizing layers to hierarchy groups is necessary for broad databases and displaying a lot of SHPs. This function will be very useful.<br>In my opinion the tag "parents" is fully apposite.
<br>When can we look forward for implementation to Ka-map? Or is it possible to download and replace just the kaLegend.js file?<br>Thankee<br>Jamie<br><br>> ------------ Původní zpráva ------------<br>> Od: Samuel Hiatt <
<a href="mailto:samhiatt@gmail.com">samhiatt@gmail.com</a>><br>> Předmět: [ka-Map-users] Expandable/collapsible groups or sub-layers in kaLegend<br>> Datum: 25.10.2007 20:44:41<br>> ----------------------------------------
<br>> Hello kaMappers!<br>><br>> Yesterday I finished implementing some modifications of kaLegend.js that<br>> allow layers to be grouped in a hierarchy and presented in<br>> expandable/collapsible menus. I am aware that a few others have requested
<br>> this functionality, so I'd like to be sure that my implementation can be<br>> useful to all.<br>><br>> In order to implement this functionality I had to invent a new metadata tag<br>> for the layer. Currently I use the tag "parents" and then list the parents
<br>> of a sub-layer. For example, for layer "streets" the metadata could look<br>> like...<br>> "parents" "Infrastructure::Transportation"<br>><br>> saying that "streets" is a child of transportation, which is a child of
<br>> Infrastructure.<br>><br>> I am not sure if the name "parents" and the syntax I chose for the metadata<br>> makes much sense, so I would like to hear from y'all to determine what would<br>> be the best way to represent a layer's position in the hierarchy with a
<br>> metadata tag. Does anyone have any suggestions?<br>><br>> If this enhancement to the kaLegend is useful to many more people I'd like<br>> to make sure it is polished up and can be committed to the ka-map
<br>> distribution.<br>><br>> Thanks for your input.<br>><br>> Sam<br>><br>><br>><br><br>Jamie<br></blockquote></div><br>