From: Zaleski, M. \(M.E.\) <mza...@fo...> - 2007-07-26 15:59:42
|
> -----Original Message----- > From: jed...@li...=20 > > I've made many improvements to my CamelComplete plugin since=20 > last time. > In addition to what it did before, it now has >=20 > -Multiple "engines" so that you don't have to rescan all your=20 > JAR's, Ctags, etc. when only one of them changes. > -Option groups to remember commonly used word sources. > -Configurable popup list size > -More shortcuts (0-9, a-z, A-Z) for the popup list. > -Ability to scan through all open buffers for words using a=20 > user-defined regex. > -Use BeanShell to easily plug in your own word sources. > -Public API if other plugins want to add some camel completion. >=20 > For me, it does everything I want and saves a lot of keystrokes. >=20 > A downside is that its options panel is daunting. >=20 > I've submitted it to the tracker, but do please download it=20 > and try it out, from >=20 > http://www.illengineer.com/jpavel/Prog/CamelCompletePlugin/ >=20 > Best, > Jesse >=20 I just installed and tested it. This plugin is very handy for me since I work with several languages not supported by the normal ctags-type parsers and I can use the BufferWords and text file parsers for completions. You are right, the options panel is daunting and probably needs some changes to layout. I'd have to think about what would be easier to understand while still having the flexibility. Is it possible to set up a BufferWords that uses ONLY the current buffer? Many times I'm working on a file with custom names and being able to restrict which buffers it scans would shorten the match list considerably. --=20 Matthew Zaleski |