[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwrite-devel
Subject:    Re: subversions markers in icon border
From:       Dominik Haumann <dhdev () gmx ! de>
Date:       2008-12-19 16:45:05
Message-ID: 200812191745.06028.dhdev () gmx ! de
[Download RAW message or body]

Hi Will,

some thoughs on this: Other editors (e.g. Visual Studio, Eclipse) has a 
similar bar as well. It shows states such as
- what you changed and saved (green)
- what you changed and not yet saved (yellow)
- everything else is not highhlighted.
This approach is a bit more general and maybe more useful also for 
non-developers. This could be implemented by adding the changed-infos to 
KateTextLine and to the KateUndoHistory.
For developers the feature you descrive is maybe useful, but then you can 
quickly view a diff with the external tools (if the plugin isn't broken;) 
as well.

Aynway: I believe integrating it directly into katepart is the wrong 
approch: it makes the editor component even more complex. What I suggest is 
to design a KTextEditor interface that lets you hook into the icon border 
(in fact, there already is one which is called AnnotationInterface, maybe 
that would already be useful). The next step then would be to implement 
your ideas in a KTextEditor plugin.

Dominik

On Thursday 18 December 2008, Will Angenent 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


_______________________________________________
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]