File manager context menus

[Emmanuel Pescosta]

> 3) A popupmenu implementation moves to KIO, made of the best stuff from
> dolphin and konqueror.

+1 from my side!

I have made two patches related to context menus (
https://git.reviewboard.kde.org/r/115678/ and
https://git.reviewboard.kde.org/r/115679/) some time ago, to make the
DolpinContextMenu more independent, so that it can be reused in multiple
places within Dolphin.

> enum ContextElements
> ContextMenu(ContextElements::CUT | ContextElements::COPY |
ContextElements::PASTE | ...)

I think the "context" based approach to add the right actions, which is
currently used in Dolphin's context menu, makes sense here and we should
keep it, because we can easily provide default menus for specific contexts
like trash, folder/file, viewport ... and if special contexts are needed,
then they can be added really easily. So different users of the menu
(Dolphin, folderview, ...) will have the same default items in the same
order.

Cheers,
Emmanuel


2014-08-17 16:44 GMT+02:00 Eike Hein <hein at kde.org>:

>
>
> On 17.08.2014 16:13, Eike Hein wrote:
>
>> So perhaps the goal must be to offer QML bindings from the
>> start -- only to validate that things can be instanciated and
>> used outside a C++ environment, and instead in an environment
>> that guarantees QWidget can't be a requirement.
>>
>
> Or maybe it's best to be less ambitious for now: Instead
> of trying to offer a QML API, we could at least try to
> offer a C++ API that doesn't impose external requirements
> on QWidget.
>
> E.g. overloads for both QWidget and QWindow, the latter
> then calling windowHandle()->setTransientParent() on the
> dialog boxes, ...
>
>
> Cheers,
> Eike Hein
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20140817/b431350e/attachment.htm>