Re: [rox-devel] New ROX App - Find (in files)

[Jonatan L. <th...@ho...>]

On Tue, 24 May 2005 19:29:10 -0700
Ken Hayber <ke...@ha...> wrote:

> Jonatan Liljedahl wrote:
> 
> >On Wed, 25 May 2005 00:35:34 -0300
> >Jonatan Liljedahl <th...@ho...> wrote:
> >
> >  
> >
> >>On Mon, 23 May 2005 19:15:25 -0700
> >>Ken Hayber <ke...@ha...> wrote:
> >>
> >>    
> >>
> >>>OK, first update.
> >>>
> >>>     I tried using gtk.check_version() to handle compatibility with
> >>>     older 
> >>> gtk versions.  Please let me know if this helps.
> >>>         specifically: the ellipsize problem and the
> >>>         FileChooserDialog
> >>>         
> >>> problem.
> >>>     I added code to enable/disable the toolbar buttons
> >>>     appropriately. I added support for dropping a folder on the
> >>>     AppDir to set the 
> >>> initial search path (suggested by Musus Umbra)
> >>>
> >>> Here:  http://www.hayber.us/rox/find/Find-002.tgz
> >>>      
> >>>
> >>Works now, very nice! This is a very usefull tool. =)
> >>
> >>One feature request, it would be nice with a checkbox in the main
> >>window to ignore case. I know I can add "-i" to the find/grep
> >command>in options, and I know it would be hard to know what option
> >to add to>the search command to ignore case since the search command
> >is user>settable... Maybe a variable $IgnoreCase and an entry field
> >in options>to what it should contain?
> >>    
> >>
> >
> >Another thing I'd find usefull is to not recurse into subdirs, i.e.
> >"-maxdepth 1" option to find command.
> >
> >And, one small and easy thing: pass a default pattern as $2 to the
> >AppRun script... Usefull when called from an editor, you could select
> >some text and bring up Find to search for it...
> >
> >  
> >
> Good suggestions, I'll try.  Right now I'm working on using 
> ComboBoxEntry widgets (where available) to add history for the three 
> Entry fields.
> 
> I could use some help if anyone knows a good method to specify
> multiple find patterns (e.g. *.cpp, *.h, *.c, *.py).  I thought one
> way would be to parse the Files entry as a list and literally run the
> find command multiple times, once for each *.blah item.  But I'm not
> sure I like that idea much.

That also depends on the find command used... with standard find you
just pass it
"-name '*.c' -or -name '*.h'" etc..
It could be solved by even more entries in options for:
FILE_PATTERN="-name '$file'"
FILE_SEPARATOR=" -or "

Or maybe you should just hardcode it to use find and grep? Or at least
put all settings for it in an XML file that have to be hand-edited. I
don't think the common user will need to alter the find command so maybe
it shouldn't be in the options GUI.

/Jonatan    -=( http://kymatica.com )=-