Documentation of tool.jar classes?

I did, well, two of them anyway. Too big. Too complex. Too long a learning curve. Not all the features I'd like. Not simple enough.

I'm currently using Crimson Editor. I was using TextPad. My teacher last year told us to download the "free" version. Truth be told, it's an evaluation version, not free. When I got a new computer, I just didn't want to rip off the people who made TextPad. So I tried out NetBeans. Slow, extremely complex. Scrapped it. Tried jEdit. Less complex, but still not what I wanted. Mainly, I wanted easy project management which it just plain didn't provide, and I didn't feel like hunting down a good plug-in. I considered trying to write my own plug-in, but the code made very little sense. That may be because I'm used to very object oriented (as in I was brought up in programming by Java). Anyhow, thne I tried BlueJ. Crud. Scrapped it. Found Crimson, and am fairly satisfied with it, but...

I'm interested in making a Java editor for dummies, so to speak. ^_^ I want to cut out dealing with the command line stuff. Setting the classpath every time I want to compile or run the program/leaving it permanently set inside a tool, an easy to deal with error system for compilation, a simple jar/zip maker, and other stuff. To do that, I need to know what I have to work with inside the JDK. Hence, the need for documentation. I was actually trying to make a program that would read and analyze all the classes but ran into rather annoying problems, and I'll probably just do that if there isn't any documentation on what's inside tools.jar.

*bangs head on wall* Ooooohhhhh. You mean look inside those programs to see how they deal with calling javac. A good idea, but if Sun has something, I'd rather use that. Thanks. I appriciate the suggestion. I have a feeling that will come in handi.

It occured to me that running javadoc would be easier than what I'm trying to do. Will javadoc work on pure class files, no source files?

Legend_Keepera at 2007-7-8 1:57:49 >