[prev in list] [next in list] [prev in thread] [next in thread]
List: kwrite-devel
Subject: Re: subversions markers in icon border
From: "Ivo Anjo" <knuckles () gmail ! com>
Date: 2008-12-18 23:06:17
Message-ID: 557ea2710812181506p1e8211eal3bde4d5dfc63e141 () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
On Thu, Dec 18, 2008 at 10:13 PM, Will Angenent <will.angenent@ntt.eu>wrote:
> Hi,
>
> I've been thinking about an overambitious project I'm looking into, and
> that's to have markers in the icon border showing which lines have been
> added/edited/deleted since the last cvs/git/svn commit. For example, see
> the green and blue things on the side of this screenshot of netbeans:
> http://www.collab.net/collabXchange/NetBeans/images/svn.gif
>
> Integrating it with the KateIconBorder seems easy enough. I haven't
> looked into the rest of the nitty gritty stuff yet. I'd like to hear
> what you think about these questions:
>
> 1. Do I use cervisia or kdesvn? They both seem like separate projects.
> Is it going to be worth my time to try and use them? Also, I'm going to
> want git support in there too. I'd have to write something brand new for
> git.
> 2. Do I use cvs/svn/git libraries or command line tools? If I use
> libraries, how does this work when using/compiling kate when those ones
> aren't available? Am I better off writing a wrapper around the command
> line binaries cvs, svn, git? Or should it be some dynamic library
> loading thing?
> 3. To keep things up to date, regular calls to "cvs/svn/git status" will
> have to be made to see if a commit has been done in the background.
> Should this be done on a one second timer or something? An alternative
> for svn is to check the .svn/text-base directory for changes, since the
> commit will update a file in there, so I can use inotify/kdirwatch or
> something.
>
> If I don't get horribly demotivated and actually pull this off, I could
> continue to add more functions, but one step at a time!
>
> Thanks for your thoughts & comments,
> Will
> _______________________________________________
> KWrite-Devel mailing list
> KWrite-Devel@kde.org
> https://mail.kde.org/mailman/listinfo/kwrite-devel
>
Hi :)
This seems a great idea! I put most of my stuff in svn and edit most of it
with kate so it would be a match made in heaven.
I personally use a mix of command-line svn and eSvn. esvn is pretty simple,
but gets the job done.
Also, esvn parses the output of subversion, and I currently have to run it
with a wrapper script because it expects something that has changed in the
latest svn version, so I would venture that using a library would be much
better.
Finally, I think esvn also uses some kind of timer (by me experience I think
it's 5-10 seconds) to check for new info; but I think that as you suggest
watching the svn control directory for changes would be much better -- less
cpu wakeups and it should react faster to changes.
As for git and cvs, I don't really use them so I wouldn't know :)
Ivo Anjo
[Attachment #5 (text/html)]
On Thu, Dec 18, 2008 at 10:13 PM, Will Angenent <span \
dir="ltr"><will.angenent@ntt.eu></span> wrote:<br><div \
class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br>
<br>
I've been thinking about an overambitious project I'm looking into, \
and<br> that's to have markers in the icon border showing which lines \
have been<br> added/edited/deleted since the last cvs/git/svn commit. For \
example, see<br> the green and blue things on the side of this screenshot \
of netbeans:<br> <a href="http://www.collab.net/collabXchange/NetBeans/images/svn.gif" \
target="_blank">http://www.collab.net/collabXchange/NetBeans/images/svn.gif</a><br>
<br>
Integrating it with the KateIconBorder seems easy enough. I haven't<br>
looked into the rest of the nitty gritty stuff yet. I'd like to \
hear<br> what you think about these questions:<br>
<br>
1. Do I use cervisia or kdesvn? They both seem like separate projects.<br>
Is it going to be worth my time to try and use them? Also, I'm going \
to<br> want git support in there too. I'd have to write something brand \
new for<br> git.<br>
2. Do I use cvs/svn/git libraries or command line tools? If I use<br>
libraries, how does this work when using/compiling kate when those ones<br>
aren't available? Am I better off writing a wrapper around the \
command<br> line binaries cvs, svn, git? Or should it be some dynamic \
library<br> loading thing?<br>
3. To keep things up to date, regular calls to "cvs/svn/git \
status" will<br> have to be made to see if a commit has been done in \
the background.<br> Should this be done on a one second timer or something? \
An alternative<br> for svn is to check the .svn/text-base directory for \
changes, since the<br> commit will update a file in there, so I can use \
inotify/kdirwatch or<br> something.<br>
<br>
If I don't get horribly demotivated and actually pull this off, I \
could<br> continue to add more functions, but one step at a time!<br>
<br>
Thanks for your thoughts & comments,<br>
Will<br>
_______________________________________________<br>
KWrite-Devel mailing list<br>
<a href="mailto:KWrite-Devel@kde.org" \
target="_blank">KWrite-Devel@kde.org</a><br> <a \
href="https://mail.kde.org/mailman/listinfo/kwrite-devel" \
target="_blank">https://mail.kde.org/mailman/listinfo/kwrite-devel</a><br> \
</blockquote></div><br>Hi :)<br><br>This seems a great idea! I put most of \
my stuff in svn and edit most of it with kate so it would be a match made \
in heaven.<br>I personally use a mix of command-line svn and eSvn. esvn is \
pretty simple, but gets the job done.<br> <br>Also, esvn parses the output \
of subversion, and I currently have to run it with a wrapper script because \
it expects something that has changed in the latest svn version, so I would \
venture that using a library would be much better.<br>
<br>Finally, I think esvn also uses some kind of timer (by me experience I \
think it's 5-10 seconds) to check for new info; but I think that as you \
suggest watching the svn control directory for changes would be much better \
-- less cpu wakeups and it should react faster to changes.<br>
<br>As for git and cvs, I don't really use them so I wouldn't know \
:)<br><br>Ivo Anjo<br>
_______________________________________________
KWrite-Devel mailing list
KWrite-Devel@kde.org
https://mail.kde.org/mailman/listinfo/kwrite-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic