Re: [ jEdit-devel ] JSwat plugin

[Slava P. <sl...@je...>]

Hi,

I think both Dirk's debugger and the JSwat plugins can co-exist.
Just like we have Clipper and XInsert, or AStyle and JavaStyle.

Slava

On Fri, Aug 24, 2001 at 11:39:26AM +0200, Dirk M=F6bius wrote:
> It looks great!!! What a wonderful contribution. Thanks a lot!
>=20
> Some remarks:
>=20
> * I tried to download the plugin JSwat.jar file from your site, but it =
was
> corrupted. Could you please check? (I was, however, able to build from
> source, thanks to the good build file.)
>=20
> * Exiting JSwat exits the whole VM and jEdit.
>=20
> * Did you know that I started a Debugger plugin some weeks ago?
> Coincidentally I updated it yesterday. It can now step through the
> source (step in/over/out), and shows thread, stack and local variable
> info. Program output goes to the system shell of the Console plugin. No=
t
> more. Support for breakpoints is in the framework, but you can not set
> them right now. A source manager is missing.
>=20
> I created it from scratch, without using JSwat. This is why there is no=
t
> much there yet. Reasons why I don't use JSwat:
>=20
> - I wanted tighter integration with jEdit, e.g. use the dockable
> windows, the key/action framework, the Console, and maybe later the
> ProjectViewer.
>=20
> - I looked over the JSwat code and found no easy way to integrate it
> with jEdit. You proved the opposite, but it was too much for me.
>=20
> - The integration of JSwat must always be in form of a patch. You canno=
t
> take an unpatched version of JSwat and, say, simply put it in the
> classpath or jEdit jars/ folder, along with the plugin code in a
> separate jar. JSwat is not designed to be used as a library. (Neither i=
s
> my debugger...{:-). As a consequence, you'll have a hard time to keep
> "your" JSwat consistent with new JSwat releases.
>=20
> - I didn't like some of JSwat's design, e.g. there's not enough
> model-view-controller separation. I don't want to deprecate Nathan's
> great work, and I wouldn't say that my code is in any case better,
> but... well, it's just personal taste. But most of all:
>=20
> - I wanted to play around with JDI myself.
>=20
> The code is on the plugin CVS. Alas, You need the current CVS versions
> of Console (3.0), EditBus (1.1), ErrorList (1.1.1), too. Please have a
> look and tell me what you think!
>=20
> Thanks,
> Dirk.
>=20
>=20
> --=20
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> http://lists.sourceforge.net/lists/listinfo/jedit-devel