The future of KAction

[Hamish Rodda]

On Sunday 20 November 2005 01:10, Richard Moore wrote:
> One thing I would like to see from a new KAction is that it be a bit
> smarter. Currently for example we have a fileOpen action - almost every
> application connects this to a slot which pops up a file dialog, checks the
> output then calls a load function. The fileOpen action itself could handle
> the dialog. The saving of this approach is even greater for fileSave where
> the action can handle backups, check for overwriting etc. The approach has
> further advantages for automation, as it is possible to code the action to
> allow the filename to be specified externally, eliminating the need for the
> automation engine to deal with the file dialog at all.

This is already possible with KAction from KDE 3, it's just that nobody has 
created "KFileOpenAction".

Also, it will be just as easy to do with KAction inheriting from QAction in 
KDE 4, should the change be accepted.

Cheers,
Hamish.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051120/0c69f964/attachment.sig>