The future of KAction

[Richard Moore]

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.
 Cheers
 Rich.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20051119/9987030b/attachment.htm>