A KSelectAction dedicated to QTextCodec selection ?

[Robert Knight]

> IMO, a single "Manage..." button would be better, which brings up a
> dialog to add/remove favorite charsets

I second the idea for a single button, but I suggest that it should be
called "Add / Remove..." , for familiarity.

Regards,
Robert.

On 26/09/06, LiuCougar <liucougar at gmail.com> wrote:
> On 9/25/06, Michel Hermier <michel.hermier at gmail.com> wrote:
> > Hi,
> >
> > I just commited the code available here:
> > http://websvn.kde.org/trunk/KDE/kdenetwork/kopete/protocols/irc/ui/kcodecaction.cpp?rev=588417&view=auto
> > http://websvn.kde.org/trunk/KDE/kdenetwork/kopete/protocols/irc/ui/kcodecaction.h?rev=588417&view=auto
> > http://websvn.kde.org/trunk/KDE/kdenetwork/kopete/protocols/irc/ui/kcodecactiontest.cpp?rev=588417&view=auto
> > http://websvn.kde.org/trunk/KDE/kdenetwork/kopete/protocols/irc/ui/kcodecactiontest.h?rev=588417&view=auto
> >
> > The class is named KCodecAction (for historical reasons), but maybe a
> > better name would be KTextCodecAction or KCharsetsAction. Also
> > included a test code, so that it can be tested.
> >
> > I was thinking instead of adding an Add/Remove button,
> IMO, a single "Manage..." button would be better, which brings up a
> dialog to add/remove favorite charsets
>
> Regards,
> Cougar
>
> > maybe we can
> > add some auto hidden fields (based on date of last clicks and stored
> > in a KConfig), and add a "More ..." action class at the end of the
> > list, if not all the elements are shown ?
> >
> > Michel
> >
>
>
> --
> "People's characters are strengthened through struggle against
> difficulties; they are weakened by comfort."
> - Old Chinese adage
>