Hi Eric,
Eric Berry wrote:
>>> My jEdit starts up and takes around 33M just to run.
(snip)
> It's a trunk build as of about a week ago.
It sounded too large for me, but, possible if you have some plugins
I don't use, or some files are loaded on startup.
> I mean real usage (installed plugins, editing of files, etc...), not startup
> so many times. Real editing. Eg. X% of users have on average 5 files open,
> and 3 plugins installed, and the heapsize is (on average) 12M. This would
> give us a reasonable default value to start with right?
I think it is not relevant to set "-Xms" by default, because the actual
heap size is so different among users, and the heap automatically glows
as needed.
>>> As for the values being all over the place, maybe we should re-examine the
>>> way the installer works? Perhaps we should have basically 3 startup
>>> scripts
>>> and just have the install pointers to those.
>>
>> Sorry but I couldn't understand this part. What do "3 startup scripts"
>> mean?
>
> Startup scripts as in .bat, .sh, and Info.plist files. :)
I think Windows installation could be better by bundling a native
jedit.exe created by Launch4j. It has configured to use a separated
.ini file to specify the JVM options.
http://launch4j.sourceforge.net/
http://launch4j.sourceforge.net/docs.html#Additional_jvm_options
It is working fine on my local. This also makes Windows file type
association far easier. I'll make an actual patch to make this, probably
after the release of 4.3pre16. It might be in 4.3pre16, with some luck.
--
k_satoda
|
