[KDev4] CVS plugin
Robert Gruber
R.Gruber at gmx.net
Wed Apr 11 09:12:26 UTC 2007
On Wed, 11 Apr 2007 10:36:14 Andreas Pakulat wrote:
> On 11.04.07 10:05:28, Robert Gruber wrote:
> > I just committed a first version of my CVS plugin for KDevelop4.
> > Currently it's only possible to run actions via the menubar. The action
> is
> > always performed on the currently displayed file.
>
> And I just disabled it again, sorry.
No problem, I just commited it to not risk losing it on my local hard drive.
> We first need a CMake macro to
> check for cvs-existence, so we can conditionally compile cvs plugin.
I'm not sure if it's a good idea to make the compilation of the plugin
depending on the existence of the cvs client. Otherwise one would have
to recompile KDevelop if he installed CVS after KDevelop. cvs is not required at compiletime at all. Therefore (although I don't know if that's
possible) I think we should rather check for it's existence at runtime
and maybe disallow the loading of the plugin if cvs client is missing.
> Also I guess you could've saved you a bit by waiting a bit longer, we're
> still discussing the SCM interfaces so you may need to change stuff
> sooner or later...
I think that shouldn't be a problem.
The plugin is seperated into three parts.
The Interface does not more than collecting the files and
requesting a certain action (add, update, ...) for that files.
The Proxy handels all the stuff related to the cvs client, like
building the commandline, creating the job, and so on...
The Output-Views get connected to a job and will parse and display it's output
So (hopefully) chaning one of these parts will have no or little inpact on the others...
> > The output of basic actions like "cvs add", "cvs update", "cvs edit",
> "cvs
> > unedit"... gets continuously written as plain text to the first
> tabwidget of the outputview.
> >
> > More advanced actions like "cvs diff", "cvs log", "cvs editors"... will
> create a new tabwidget which allows to display their output more
> beautified. This is currently only implemented for "cvs editors"
> >
> > Any comments are welcome....
>
> Sounds good so far, except of course for the main menu actions. But we
> can tackle that later once we know what our SCM interfaces need to look
> like.
Well, I just added the mainmenu stuff in order to be able to test the actions somehow. As soon as we have an other option to issue VCS actions I'll remove it from the mainmenu.
Robert
--
"Feel free" - 10 GB Mailbox, 100 FreeSMS/Monat ...
Jetzt GMX TopMail testen: http://www.gmx.net/de/go/topmail
More information about the KDevelop-devel
mailing list