[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: The future of KAction
From:       Richard Moore <richmoore44 () gmail ! com>
Date:       2005-11-19 14:10:01
Message-ID: 5491a5150511190610w70d75c56ud92d12c129ecc6d7 () mail ! gmail ! com
[Download RAW message or body]

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.

[Attachment #3 (text/html)]

<div>One thing I would like to see from a new KAction is that it be a bit s=
marter. Currently for example we have a fileOpen action - almost every appl=
ication connects this to a slot which pops up a file dialog, checks the out=
put 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 fur=
ther advantages for automation, as it is possible to code the action to all=
ow the filename to be specified externally, eliminating the need for the au=
tomation engine to deal with the file dialog at all.
</div>
<div>&nbsp;</div>
<div>Cheers</div>
<div>&nbsp;</div>
<div>Rich.</div>
<div>&nbsp;</div>


[prev in list] [next in list] [prev in thread] [next in thread]