Re: Debugging with JDEE

I've always used jdb, so jswat 3 is my first try.

I used it several times today for debugging some exceptions with a new
release we have coming out.  It launched fairly fast on my 1.8 GHz
with 1GB RAM laptop.

I could find a way to remote edit back with gnuclient.  It looks like
they are (now?) using net
beans for the internal editor, thus it's not so light with 28 of total
32 MB devoted to net beans support.  It's okay for debugging code, but
definitely more used to jde, ecb, flymake in emacs for productive
work.  JDB is only way to go for that level of integration.  But jswat
is a nice
addition to the arsenal of tools, since I like the filtering of
classes and options for breakpoints.

I also found a few issues with the jswat.el which I sent last night,
and attached one with more fixes after using all day.

On 6/23/06, Nascif Abousalh-Neto <[email protected]> wrote:
> Hi Jeffrey,
>
> Thank you for your feedback. What is your impression of JSwat? And how would you compare 2.39 with the JSwat latest version? Is it worth the update?
>
> I really liked the 2.x version because it was fully functional, and yet very light and launched fast. Not only you can start JSwat from Emacs using jswat.el, since JSwat supports the customization of the source code editor, using gnuclient you can go back to Emacs after a problem is found.
>
> I will try your version with the 3 version as soon as I have a chance.
>
> Many thanks for taking the time to make changes to jswat.el, I appreciated it.
> Regards,
>   Nascif
>