From: <ll...@li...> - 2002-12-31 04:16:06
|
I have downloaded and installed Excelsior 3.0 pro in the evaluation edition and jedit4.1pre7 in the source tar. It all compiled without any problems. Took some time though. 4 minutes and 17 seconds to get the .exe vs. 14 seconds to produce the .jar file. Launch time seemed to be about cut in half. 1-2 seconds vs. about 3-4 seconds in normal JRE mode. Memory footprint seems to be nearly identical. I only measured just after launch, it might be noticable different after a full days use - for better or worse! The application seems quite a bit more snappy, but it is just a gut feel. I need some way to really measure the difference. Any ideas ? Maybe I just need to test it at my old 266mzh PII instead. I installed a couple of plug-ins from the plug-in manager (BufferList, ProjectViewer) and it seems like they are running fine. After installing new plugins jEdit starts really slow the first time. Next time it is fast again. The downsides however, are considerable: A lot of stuff didn't work. I got exceptions trying to open files or trying to open the search dialog. Other things worked fine. Incremental+hypersearch, drag and drop, close files, open help. To name a few. Beanshell also seemed to work. The exceptions I got was a NPE from the EditBus. Wonder what that could be ? Another strange error is that I got some (errors+warnings) of my error trace in the console instead of in the Activity Log (just debugs). I will send this on to Excelsior JET support and see what they have to say for their defence ;-) I don't know if jEdit is very far from working perfectly with JET or very close. My gut feeling tells me that they probably has some undiscovered bug that I have triggered and that it will work after that. If I can get it to work perfectly I would surely prefer the JET version over the normal version. But it is a bit harsh on Slava (to say the least) if he has to debug everything on two VMs. So it would have to work perfectly! /Lasse |