From: Dominic S. <do...@ss...> - 2000-07-19 23:32:37
|
> OK. Dominic. We need to be REALLY carefull here. > > You just forked development :( I thought that was a possibility but I wanted to just fix a few minor things - that is why there are no major changes in 0.4.9 > > When you get jEdit CVS access please check this into CVS as a new > branch. The current JCompiler CVS code is in a REAL state of flux > because it is being rewritten (didn't get time to finish it) to support > PluginHolder and Jikes. I will try to do that but I am new to CVS - so I'll have to start reading the docs :(. > I would merge your code into this version and get it working. Currently > it compiles but most of it is commented out. I would just go through > the sections and let me know if you have any questions. Does his mean that 0.6 is mostly written but not tested? > I would assume the rewrite you are talking about is the same reason I am > rewriting it. Most of the code was static :( and it wont' work with > PluginHolder. I also have a init() of a Compiler interface so that we > can have a Factor for JikesCompiler, ClassicCompiler, etc. Maybe we > could even use Ant tasks for this. I don't quite understand about what you mean about init() of compiler interface? What are Ant tasks? > -1 on adding this to PluginCentral until the code is in CVS. I will put this into the CVS, but as it is only minor changes I don't see the problem with releasing it. > > I will be releasing another version with many more changes including using > > ErrorList, this will involve rewriting quite a lot of JCompiler. > > Slava suggested this. I don't have any major opinion. Just that we can > do things like add an icon to the JList, etc. It's just that I have never managed to get it to work when I double click on a line in the output and I know from previous messages that other people have had the same problem. I haven't looked at this as I was thinking of using ErrorList to make it easier to maintain etc., although I do agreee there would be an advantage about having a proprietry and therefore more customisable interface? > > I would > > also like to know whether I should continue Kevin's development of the Load > > Stack Trace dialog (to decompile classses in the Stack trace of errors) as > > the code for it now is still not finished? Do people use this feature? > > It was written as a bootstrap into more IDE style features. IE if you > run a java process and it gives you a stacktrace as output (within > jEdit) you should be able to see all the source, even if that means > decompiling all its classes. IMHO this really should be a seperate plugin - or part of JavaInsight not JCompiler. > > I > > would also like to hear about other features people would like me to > > include. > > The jikes support infrastructure was done in 0.6.0. I would really like > to see this finished and released. If you beat me to it I can help you > :) Yes I would like to have Jikes support, I haven't used Jikes so I don't know how different it is? I suppose i should download it and try it out, but I am currently quite low on disk space... A problem I was having with understanding some of it is that there are quite a few empty methods and I am not sure what you intended them to do, but I will have a look at 0.6. |