Where to populate Version Control entry

[Aleix]

First of all I'd like to say that I think this is very needed if we want to
bring some central support for vcs.

I think that the proper way to implement it would be creating a plugin such
as the Project Manager that added the context menu entries querying the vcs
plugins (using the project management plugin hooks or adding new ones if
necessary).

Hope this helps.
Aleix

On Sat, Aug 16, 2008 at 10:13 PM, Andreas Pakulat <apaku at gmx.de> wrote:

> Hi,
>
> I wanted to move the code that populates the "Version Control" context
> menu from the individual vcs plugins into a more central place.
> Unfortunately I couldn't quite figure out the apropriate place for it.
>
> My problem is mostly that in shell/ there's only plugin controller who
> can contribute to the context menus, but I don't want the VCS-code
> there.
>
> So I'm looking for ideas how to do this in a clean way, ideally
> something inside the vcs library would do this, but that would need
> either the vcs lib linking to shell or a public signal in the
> interfaces. I don't really like either of the options, but has anybody
> got a better idea?
>
> This might not be just for VCS context menu, I think in the future there
> maybe other things that could use this - if we find a proper API to do
> it.
>
> Oh, and I fixed the problem with the VC-Context menu having duplicate
> entries, the dvcsjob had a small bug.
>
> The reason to still have the VC-Menu populated in a central place
> instead of by the plugins individually is to make sure that any
> VCS-plugin provides some common base functionality with common widgets
> so users don't need to learn a completely different UI everytime they
> have to switch the VC-System.
>
> Andreas
>
> --
> You can do very well in speculation where land or anything to do with dirt
> is concerned.
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20080817/04cb57f4/attachment.html>