X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;ds=sidebyside;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=c650abb5e4572557e1d175ecc72a0f7c8892202e;hp=55e94efd29b7c4861e3f9ca8c34f8afeb1a8154d;hpb=a5eefc708b5f7aaedcd1640f944dd5b2851ea614;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index 55e94ef..d1d141d 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -1,37 +1,78 @@ + -->
- What's new ?
Jalview 2.8.1 includes a range of new features developed in the last 12 months.
As usual you can find the
- highlights below, and the comprehensive list is given in the Jalview 2.8.1 Release Notes.
-
+ 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$.
+