[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ve-dev] VE 1.5 themes
|
Jeff,
The container is responsible for indicating
what the IConfigurationContributor is, and this is responsible for manipulating
the build path. It is also responsible for contributing to
the palette. Presumabely if JFCClasspathContributor we able to detect
the JRE level it could decide what entries to add to the palette, what
/override files to use and also what beaninfo jar(s). It's not been
coded yet, but I think the mechanics are there to do JRE context switching.
One issue might be that we'd need a way to detect what the JRE level
is and I think this can maybe only be done once it's started (which is
too late for the ClasspathContributor) but maybe there's something like
a marker in a text file in one of the JRE directories, or perhaps we could
run a "java -version" and stream the output to a buffer to find
the JRE level. SWT I'm not sure about - maybe hard code the dll ranges
for each level and look in the directory to see which ones are there.
Best regards,
Joe
Please respond to ve-dev@xxxxxxxxxxx
Sent by:
ve-dev-admin@xxxxxxxxxxx
To:
ve-dev@xxxxxxxxxxx
cc:
Subject:
Re: [ve-dev]
VE 1.5 themes
One more thought for a possibly important theme for
1.5 would be being
able to support multiple levels of beaninfo and palette components
depending on a given criteria. This is necessary to support targeting
various levels of the JRE (1.4 and 1.5) as our palette and beaninfo is
stuck at 1.3 levels, and would also be necessary to target different
versions of SWT.
- Jeff
_______________________________________________
ve-dev mailing list
ve-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/ve-dev
