X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=7dfc6aec87248b15f6a01c5eb1584f39f21d4233;hp=003ba8bc8145f1bb03b0cf8d29bc2ed98bceda72;hpb=965d7e5e0519eb069d37ea3fb398c571a573d5e7;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index 003ba8b..d1d141d 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -1,37 +1,78 @@ - - -What's new ? - - -

What's new ?

- -

Jalview Version 2.3

- -

Issues Resolved

- -

 

-

See the Release History page for -details of all new features and resolved issues.

- - + + + +What's new ? + + +

+ What's new in Jalview 2.10.1 ? +

+

+ 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. +

+ + +

+ 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$. +

+ +