jdiff-devel

[ JDiff-devel ] Re: JDiff (fwd)

[mike d. <md...@st...>]

ditto.

-md

---------- Forwarded message ----------
Date: Tue, 10 Oct 2000 08:56:05 -0700 (PDT)
From: mike dillon <md...@gj...>
To: Victor Volle <v....@co...>
Subject: Re: JDiff

On Mon, 9 Oct 2000, Victor Volle wrote:
> Hi!

hi! indeed!

> The only thing I miss from jEdit is a diff-mode/tool.  You have been
> developing JDiff, but AFAIK you have stopped any further development.

this is true. i have posted a number of messages to both the jDiff mailing
lists and to the jEdit mailing lists seeking advice as to how to proceed, but
no one has been more than passively interested. until now.

i believe the latest concensus was that jDiff as a separate application should
cease to exist and instead should continue on only as a jEdit plugin. for those
who would have liked to see jDiff move toward being more of a visual diff _and_
merge tool, this is not too satisfying. being that i am more than happy with
command line diff and patch, this didn't bother me personally, but i was kind
of saddened by the curtailing of potential usefulness.

> I am interested in stepping in if you don't mind, but need to further
> evaluate the code of jEdit, since I would like to use much of its codebase.
> Therefore I do not want to commit myself, yet. 

great! and it's fine that you aren't sure. take your time to make a proper
decision and don't get sucked in. the main reason why my motivation to work on
this project sputtered was that i have never really had any need for jDiff
myself. i haven't used WinDiff or anything like it in actual work.

using jEdit as a code base is a good idea, since it has a lot of solid code.
also, as it says in the jDiff CREDITS file, and in the derived sources
themselves, much of the jdiff.gui package is based on the excellent text area
Slava wrote for jEdit 2.0.

in addition to that, i myself am probably the second-most familiar with the
jEdit source of anyone in the world (except maybe Andre Kaplan), so i should be
able to provide you with worthwhile and insightful feedback to comparisons or
design issues that arise. (and, Slava is both on the jDiff project and on the
mailing lists, so he can discuss as well)

> But before I explore any further: Is anybody else doing something in this
> area? I am not "pressed" doing it myself. It is just a feature I really would
> like to see implemented.

Andre Kaplan took a rather early version of the jDiff code and turned it into a
usable jEdit plugin, which i is still available from his development page at
http://jedit.sourceforge.net/devel/people/akaplan/.

that plugin has not been updated in quite a while. i don't know whether it will
work with a current version of jEdit. it was never on Plugin Central.

Daniel Lemire recently committed some small changes to the jDiff code to allow
files to be chosen and compared from within jDiff, but i don't think he has any
interest in doing further development.

i'll close for now, but i urge you to at least join the jDiff-devel mailing
list so that we can discuss in public. i look forward from hearing back from
you.

-md

p.s. woo hoo!

Re: [ JDiff-devel ] Re: JDiff (fwd)

[Slava P. <sp...@gj...>]

(Mike -- is this dude subscribed to jdiff-devel?)

mike dillon wrote:
> i believe the latest concensus was that jDiff as a separate application should
> cease to exist and instead should continue on only as a jEdit plugin. for those
> who would have liked to see jDiff move toward being more of a visual diff _and_
> merge tool, this is not too satisfying. being that i am more than happy with
> command line diff and patch, this didn't bother me personally, but i was kind
> of saddened by the curtailing of potential usefulness.

Why can't it be both an app and a plugin? Doing this is not terribly hard,
and can be done with one code base.

Slava

Re: [ JDiff-devel ] Re: JDiff (fwd)

[Daniel L. <Dan...@Vi...>]

Good day,

I tend to agree with Slava here. Building everything into one monolitic (à la Emacs)
tool is fine. I like jEdit a lot and I use it everyday. I might enjoy it very much
if there was a jDiff plug-in. But at the same time, with all the plug-ins I've got
running under jEdit, it is becoming a crowded place so I'd probably enjoy using
jDiff both as a plug-in and as a separate app.

Well, in any case, I'm using jDiff as a separate tool right now and it works! Now
that it was hacked it so it doesn't have to be used as a command line tool and we
can actually use file dialogs, I find it very useful.

What I am really looking for is replacement for the "diff" command line tool. Just
like diff isn't bundled with a text editor... I don't see why jDiff should
necessarily be.

> (Mike -- is this dude subscribed to jdiff-devel?)
>
> mike dillon wrote:
> > i believe the latest concensus was that jDiff as a separate application should
> > cease to exist and instead should continue on only as a jEdit plugin. for those
> > who would have liked to see jDiff move toward being more of a visual diff _and_
> > merge tool, this is not too satisfying. being that i am more than happy with
> > command line diff and patch, this didn't bother me personally, but i was kind
> > of saddened by the curtailing of potential usefulness.
>
> Why can't it be both an app and a plugin? Doing this is not terribly hard,
> and can be done with one code base.
>
> Slava
> --
>
> jDiff-devel mailing list
> jDi...@li...
> http://lists.sourceforge.net/mailman/listinfo/jdiff-devel

--
Daniel Lemire

http://www.ondelette.com/
ICQ: 8733252

Re: [ JDiff-devel ] Re: JDiff (fwd)

[mike d. <md...@st...>]

On Wed, 11 Oct 2000, Daniel Lemire wrote:
> What I am really looking for is replacement for the "diff" command line tool.
> Just like diff isn't bundled with a text editor... I don't see why jDiff
> should necessarily be.

one of the first things i did after finding the underlying diff code that's
behind the scenes in jDiff was to create a simple command line diff. it only
dumped in the default diff(1) format ('>', '<', etc. no unified output), but it
was useful in getting an idea of what i could do with this diff implementation.
unfortunately, that code is long gone, but IIRC, it wasn't too hard to put
together.

-md

Re: [ JDiff-devel ] Re: JDiff (fwd)

[mike d. <md...@st...>]

On Wed, 11 Oct 2000, Slava Pestov wrote:
> Why can't it be both an app and a plugin? Doing this is not terribly hard,
> and can be done with one code base.

i don't think that was the issue. more that very little application framework
code has been written yet, whereas much of the code for actually creating and
displaying diffs is already done. i think it was a matter of where to put
limited development effort.

-md