OK, Jim. That’s good to hear.
With this in mind, one thing I will be doing this summer is developing a smooth way that projects can independently link to SwingJS resources. That is, have the SwingJS project and XXXX project in Eclipse and just link them, without having to recompile the SwingJS piece all the time. Right now, for development, we are just putting all source code in the SwingJS project directory itself, so it’s easier to compile everything at once.
Jim, I’m trying to remember what we felt wasn’t there last year that we needed. I can look back at my notes, but I think maybe the menubar for sure, and combo boxes. I can’t remember how the gene scrolling/paging works, but as I remember there was some concern that there might be some very big data sets involved.
We have plenty to work on for now even without Jalview. Just because a few applets are working does not mean we have it all working by a long shot. But I do think Jalview is a great target for us. It would demonstrate success with a complex application similar to Jmol’s complexity.
A major success this summer was working out a way to speed up the sorting out of overloaded methods (formerly “searchAndExecuteMethod”). While it is still true that the more you can NOT overload methods, the better the performance, I’m not seeing that as such a major issue anymore. I don’t have any performance data yet, but I think there’s significant improvement there. At least for constructors there is no longer any search, and that is a huge part of the issue. For other methods we only have to do one search, then after that it is a quick signature match rather than an elaborate search process every time a method is called. Udo believes this is something that should be able to be settled at compile time, not run time, but for now it is still a run-time issue.
I’m turning my attention now to fleshing out JDialog. Basically I am just taking these as they come.
On Thu, Jul 14, 2016 at 7:28 AM, Jim Procter <firstname.lastname@example.org> wrote:
On 14/07/2016 13:24, Robert Hanson wrote:
Jim, just noting that there are two aspects to this:
- Running the j2s Eclipse compiler from the command line to create .js
files (in the bin directory by default)
- Running the ANT task that then puts all the pieces together into a
functional package, including doing the Google Closure compression.
I think (2) is no problem. Since there is a command-line version for (1)
with the standard compiler, there must be some way to do this. I just
don’t know how.
Yup ! Us neither
the plan this month after the 2.9.1 release, is to upgrade our
developerware, and then rebuild Jalview’s CI infrastructure to support
integration testing. Once that’s done, we can definitely look at adding
in new build hooks for j2s, but ideally, without having to script mouse
clicks on an interactive eclipse session (which would probably work, but
would definitely give me nightmares).
Jalview-dev mailing list
Robert M. Hanson
Larson-Anderson Professor of Chemistry
St. Olaf College
If nature does not answer first what we want,
it is better to take what answer we get.
– Josiah Willard Gibbs, Lecture XXX, Monday, February 5, 1900