GUI framework in kde4

[Thomas Zander]

On Sunday 2 July 2006 21:08, Hamish Rodda wrote:
> Hi,
>
> Please see the following document created at Trysil about improving
> XMLGUI (actually, mostly replacing it, but preserving + improving
> features):
>
> http://wiki.kde.org/tiki-index.php?page=KDE+4+GUI+framework
>
> Feedback encouraged :)

I find the overview a bit vague; can you give me a workflow for, for 
example, kword?
I write code in various classes (and thus various KActionCollections) to 
instantiate KAction classes currently, and load an rc file from the 
KWView widget.
* How will I create KAction instances in kword from now on?
* Will using designer mean the actions are datamined from the running app? 
If so, how will that work with kword registering a different set of 
KActions if its in read-only or in read-write mode?

Hmm reading further some points don't make sense to me, how can you assign 
kactions to actioncollections. The connection between an action and the 
resulting code to be called can not be done in a GUI tool, right?
A general data-flow, or workflow would be appreciated.


Requirements that I find important (and are not in kde3):
- store the (relative) position of a floating toolbar so a restart does 
not open it at the top of my screen, but always directly right of my app 
if I left it there.

- in the shortcuts dialog (I'm looking at kwords now) there is a distinct 
lack of context for each action.
I'm thinking we want to have multiple KActionCollections, each with a user 
viewable name for contect, and more than one per widget (since we tend to 
create almost all actions in the View widget).

- User should be able to make extra toolbars. KMail only provides one, and 
I'd love to split that into two. (well, I did in my own rc file; but I'm 
talking about the GUI config tools here ;)

-- 
Thomas Zander
-------------- 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/20060702/65158807/attachment.sig>