Fixing and regulating certain types of search fields across KF5 apps

[Sebastian Kügler]

On Monday, February 09, 2015 13:12:24 Jeremy Whiting wrote:
> > The way I'd like to see this fixed is placing an API like
> > isMinimumSearchableLength(QString) somewhere in KF5 and to
> > start using it everywhere. Realistically developers won't
> > find this on their own, but it means I could go around and
> > patch up all these places without copying code around.
> 
> That's a great idea imo.

+1. I imagine in every instance it's used it provides a huge advantage, so 
it's very much worth having it in more and more places, even if we don't 
cover 
them all, yet.

> > Which framework would be a good place for this?
> 
> Without giving it much thought I would think either KI18n or Sonnet.

Or perhaps kcodecs, sounds like an encoding-related problem to me.

Cheers,
-- 
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9