>... Also, I think that just because something is hidden due to a scale
range, it shouldn't be exempt from selection.  I'm not sure what happens
with the selection handles though.

I checked and selection feedback still occurs for hidden features.  That
seems like a good thing.

Larry

On Tue, Dec 30, 2008 at 9:13 AM, Larry Becker <becker.la...@gmail.com>wrote:

> Hi Bing,
>
>   Wow!  That was an information-rich post.  Using Lucene goes way beyond my
> usual minimalist approach to feature implementation.  You must have some use
> cases with a lot of attribute data.  So far, I haven't seen the need for
> indexing in my own work, and I would hate to pay the memory/time price for a
> tool that I would use only occasionally.
>
>   Supporting the Editable and Selectable layer settings in plugins is a
> judgment call.  Generally, I try to support them, but for some tools it
> makes sense to ignore the setting.  In the case of a search tool, I would
> think the Selectable setting should be honored.  This would be useful, for
> instance, when you have temporary duplicate layers that you wish to exclude
> from the search.
>
>   I like the approach Michael took in the Simple Query plugin.  Results can
> be displayed in the Feature Info table if selection is impractical.  Also, I
> think that just because something is hidden due to a scale range, it
> shouldn't be exempt from selection.  I'm not sure what happens with the
> selection handles though.
>
> thanks,
> Larry
> On Tue, Dec 30, 2008 at 12:24 AM, Bing Ran <bing_...@hotmail.com> wrote:
>
>>  Hi, Larry,
>>
>> I have implemented a Lucene based global attribute search for my
>> application. Features are indexed when they loaded on the layers. Search
>> results are selected and zoomed-to on the map. What is tricky is that the
>> result map needs a strategy to deal with features that are labeled as hidden
>> in a scale range and also those layers that are tagged as NOT selectable.
>> I'm wondering if I need to make a discrimination between a manually
>> selectable layer and a programmatically selectable layer.
>>
>> Bing
>>
>>
>>  *From:* Larry Becker <becker.la...@gmail.com>
>> *Sent:* Tuesday, December 30, 2008 4:12 AM
>> *To:* OpenJump develop and use <jump-pilot-devel@lists.sourceforge.net>
>> *Subject:* [JPP-Devel] Search tool for Attributes
>>
>> Question:
>>
>> You can use Simple Query to search Attribute fields for specific values,
>> but have you ever wanted to do a Google style search in a map?  In other
>> words, search all attributes in all layers for any occurrence of one or more
>> target words.  I have a tool that could be morphed into this capability
>> fairly easily, or it could be added to Simple Query.
>>
>> Any comments?
>>
>> regards,
>> Larry
>>
>> --
>> http://amusingprogrammer.blogspot.com/
>>
>> ------------------------------
>>
>>
>> ------------------------------------------------------------------------------
>>
>> ------------------------------
>>
>> _______________________________________________
>> Jump-pilot-devel mailing list
>> Jump-pilot-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> Jump-pilot-devel mailing list
>> Jump-pilot-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>>
>>
>
>
> --
> http://amusingprogrammer.blogspot.com/
>



-- 
http://amusingprogrammer.blogspot.com/
------------------------------------------------------------------------------
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to