[Kommander-devel] context menus

[Eric Laffoon]

On Friday 06 October 2006 6:20 am, Andras Mantia wrote:
> On Wednesday 04 October 2006 12:48, Eric Laffoon wrote:
> > Hi Andras,
> > I wanted to ask if you could take a look at Kommander for use with
> > context menus. After your pointing out the DCOP solution to the
> > wizard problems I'm wondering how much we are missing here. I haven't
> > worked with the KDE code for context menus much. MainWindow editing
> > in Kommander is possible using a generated window like the one in the
> > project tools I just released. It has Actions and menus.
> >
> > Here's what I'm wondering...
> > 1) Is there any possible hack to make a context menu appear and work
> > with the current executor? (We're often surprised what can be done)
>
> So you want to be able to create context menus in a Kommander dialog?

Or MainWindow, yes. Currently you can create actions and menus. What I'm 
curious about is if it may be possible to create a menu, optionally make it 
not visible on the menu bar and visible or not on the bar, make it display. 
I'm not familiar with the code in KDE for context menus, but there are 
already signals for about to show that pass X and Y points. I'm not sure what 
to pass it to. 

Michal thinks it will require changes to the executor and he's probably right, 
but then we thought there was no work around for the wizard and it turned out 
to be not that hard. So I'm curious if it can be done.
>
> > 2) What ideas would you have for adding context menus?
>
> We could expose some of the API of KPopupMenu via DCOP, but I'm not sure
> yet how to do the signal/slot connection there.
>
> Andras
There are already Actions available. During the conference Michal and I 
discussed that the following new ideas for using them.

1) When working with a MainWindow creating an action would automatically 
create a script action with it and then create a signal/slot relationship.
2) Scripts tied to actions would not show in a revised editor but would exist 
in a separate list in a script panel.
3) Regular stand alone scripts would work as always.

The only thing not discussed was allowing actions for dialogs or managing them 
for a dialog as part of a MainWindow application. Maybe we should discuss 
that.

So my suspicion is that we may be close if not able to do this. In the likely 
event this involves the executor then I think we should look at what is most 
logical. As we discussed the editor change as a pending target release it 
should be backward compatible with older executors and if we need to note an 
exception for the use of context menus we could do that. If we have to make 
changes to both editor and executor I think we should consider what makes the 
most sense.

BTW I'm still in agreement with Michal about nominal editor changes for 3x now 
with executor/language changes we can carry into KDE 4 as a transition. I 
just feel that as the MainWindow functionality basically works we should 
exploit it and release it with more improvements to project tools and context 
menus to me are very important. I think this would spur a lot of new 
development with Kommander.
-- 
Eric Laffoon
Project Lead - kdewebdev module
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://mail01.fortunecookiestudios.com/pipermail/kommander-devel/attachments/20061006/7596cbeb/attachment.pgp