X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;ds=sidebyside;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=8333f7266bd69f387a8c9c09cb844b615856a626;hp=693b0f0227b0a41f5ecfc8f9f9977c25fd0f8169;hpb=a5a0d509e08a0b6db7fd92a14006b7a3f2be22cf;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index 693b0f0..d1d141d 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -24,64 +24,55 @@

- What's new ? + What's new in Jalview 2.10.1 ?

- Jalview 2.9 has been in development since December 2014. In addition - to a multitude of bug fixes and minor improvements (both small, and - rather big!), it also brings major new capabilities for codon-level - analysis of protein alignments and the retrieval and manipulation of - structural data.

For the full list of changes, see the - Jalview 2.9 Release Notes. + Jalview 2.10.1 was released on 29th November 2016. Full details are + in the Jalview 2.10.1 + Release Notes, but the highlights are below. This is also the + first release to include contributions from Kira Mourão, who + joined Jalview's core development team in October 2016.

-

- Highlights in Jalview 2.9

+

+ Warning dialog about updating + your configured URL links
In the desktop prior to Jalview + 2.10.1, the only way to configure custom links for a particular + database cross-reference for a sequence was to give it a name that exactly + matched the database source, and a regular expression for filtering + out any spurious matches generated when the custom linked was tested + against the Sequence's ID string. Since the introduction of the + $DB_ACCESSION$ token, however, $SEQUENCE_ID$ will not be used for + database cross-reference accession strings, and if you have custom + links configured, Jalview will raise a warning message so let you + know that you may need to update your links to use $DB_ACCESSION$. +