X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=47fd498a6fe7d2e3350a9e87c526bf1e59d00be5;hp=c6389d942242997534d11828f6dc5f9ed436718b;hpb=a05186c1168e5e0a96a8825fe4c53d439079fdb3;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index c6389d9..d1d141d 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -1,25 +1,78 @@ - -
-What's new ?
- -Jalview Version 2.2.1
-Non standard characters can be read and displayed
-Annotations/Features can be imported/exported to the applet via textbox
-Applet allows editing of sequence/annotation/group name & description
-Preference setting to display sequence name in italics
-Annotation file format extended to allow Sequence_groups to be defined
--
Issues Resolved
-
- Applet crash under certain Linux OS with Java 1.6 installed
Annotation file export / import bugs fixed
-PNG / EPS image output bugs fixed
-
-
See the Release History page for -details of all new features and resolved issues.
- - + + + ++ 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$.
+