I will try not to break too many things, but it should at least compile :)
On Sat, Jul 31, 2010 at 3:56 PM, Robert Hanson wrote:
> Great! Sounds like I should take a vacation for a while!
>
> Let me know if you are going to upload changes that will break the build
> temporarily, Nico. I'll plan
Great! Sounds like I should take a vacation for a while!
Let me know if you are going to upload changes that will break the build
temporarily, Nico. I'll plan on NOT doing coding at the BCCE this next week,
I think, or perhaps the 6-hour time difference will keep us on different
schedules. Anyway,
Hi,
I have started working on going to Java 1.5 and its advantages.
I have committed many changes to take into account the following points :
- Eclipse 3.6
- Java 1.5 compiler
- Annotations @Deprecated and @Override
Still a lot of work to do and help is welcome if someone is interested
sounds good to me.
On Tue, Jul 27, 2010 at 3:39 AM, Nicolas Vervelle wrote:
> Yes,
>
> That's part of the optimizations that could be made.
>
> For going to real Java 1.5 code, I suggest waiting until the 12.0 branch is
> created, and I will start doing some modifications on the trunk (12.1.x)
>
On Tue, Jul 27, 2010 at 10:39 AM, Nicolas Vervelle wrote:
> Adding @Deprecated and @Override annotations (boring, but easy)
> Starting to use Generics (that won't be simple and it will take time)
> And optimizations when I see some (for example, I have cleaned up the
> Profiling class that was usi
Yes,
That's part of the optimizations that could be made.
For going to real Java 1.5 code, I suggest waiting until the 12.0 branch is
created, and I will start doing some modifications on the trunk (12.1.x)
I think, I will do in this order :
- Adding @Deprecated and @Override annotations (bor
On Sat, Jul 24, 2010 at 8:17 PM, Nicolas Vervelle wrote:
> In fact, that would already be the case with Java 1.5.
> Generics are in Java 1.5 (Vector and so on...)
More importantly...
Replace Vector with ArrayList as much as possible, unless you access
the List by more than on thread... that will
In fact, that would already be the case with Java 1.5.
Generics are in Java 1.5 (Vector and so on...)
Java 6 doesn't have a lot of changes in the Java language itself (I think
only new libraries but no language changes)
Nico
On Sat, Jul 24, 2010 at 8:13 PM, Robert Hanson wrote:
> 1.6
>
> On Sa
On Sat, Jul 24, 2010 at 8:13 PM, Robert Hanson wrote:
> On Sat, Jul 24, 2010 at 1:13 PM, Robert Hanson wrote:
>> The big change would be to go to 11.6. I will leave that to my successor,
>> however, because it requires thousands of instances where Vector and
>> Hashtable and such have to be expli
1.6
On Sat, Jul 24, 2010 at 1:13 PM, Robert Hanson wrote:
> The big change would be to go to 11.6. I will leave that to my successor,
> however, because it requires thousands of instances where Vector and
> Hashtable and such have to be explicitly identified as to content variable
> type. It get
The big change would be to go to 11.6. I will leave that to my successor,
however, because it requires thousands of instances where Vector and
Hashtable and such have to be explicitly identified as to content variable
type. It gets you nothing whatsoever except less of a chance to hit a
class-cast
On Sat, Jul 24, 2010 at 1:26 PM, Jonathan Gutow wrote:
> On Jul 24, 2010, at 6:00 AM, Nicolas Vervelle wrote:
>> On the other side, it won't be possible to compile Jmol with older
>> versions of Java.
>
> I don't think this is much of an issue as 1.4 is no longer supported.
> Jonathan
Even 1.5 is
On Jul 24, 2010, at 6:00 AM, Nicolas Vervelle wrote:
> Hi everyone,
>
> We are currently building Jmol for at least Java 1.5.
> What about modifying Jmol code to take more advantages of Java 1.5
> features (annotations, generics, ...) ?
I'm all for anything that improves performance or makes th
Hi everyone,
We are currently building Jmol for at least Java 1.5.
What about modifying Jmol code to take more advantages of Java 1.5 features
(annotations, generics, ...) ?
On the other side, it won't be possible to compile Jmol with older versions
of Java.
Nico
On Tue, Apr 27, 2010 at 5:17 PM, Robert Hanson wrote:
> Does it matter that Jmol 12 will require Java 1.5?
Java 1.5 was released in Sept 2004
Requiring 1.5 should not be an issue for anyone.
Miguel
--
That's ok for me.
Java 1.5 will enable a lot of code cleanup with the generics.
Maybe ask the question on the users list ?
Nico
On Tue, Apr 27, 2010 at 11:17 PM, Robert Hanson wrote:
> Does it matter that Jmol 12 will require Java 1.5?
>
> Bob
>
>
> --
> Robert M. Hanson
> Professor of Chemist
Should be OK for Macs. Linux users that are not updating should. I
assume Windows is beyond that version too.
Jonathan
On Apr 27, 2010, at 4:17 PM, Robert Hanson wrote:
> Does it matter that Jmol 12 will require Java 1.5?
>
> Bob
>
>
> --
> Robert M. Hanson
> Professor of Chemistry
> St. Olaf
Does it matter that Jmol 12 will require Java 1.5?
Bob
--
Robert M. Hanson
Professor of Chemistry
St. Olaf College
1520 St. Olaf Ave.
Northfield, MN 55057
http://www.stolaf.edu/people/hansonr
phone: 507-786-3107
If nature does not answer first what we want,
it is better to take what answer we
18 matches
Mail list logo