X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=c650abb5e4572557e1d175ecc72a0f7c8892202e;hp=9eaf83e4352208e8889381ece559ac222f88481d;hpb=e2b0b250d21b61c876bdb2303c34d66922336a86;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index 9eaf83e..d1d141d 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -1,130 +1,78 @@ + * You should have received a copy of the GNU General Public License + * along with Jalview. If not, see . + * The Jalview Authors are detailed in the 'AUTHORS' file. + --> What's new ? -

- What's new ?
- Jalview 2.8 includes a number of enhancements and new features that - have been in development since July 2010. It is also the first Jalview - release to incorporate RNA visualization features developed by Lauren - Lui and Jan Engelhart during their Google Summer of Code projects - (http://code.google.com/soc/). As usual you can find the highlights - below, but to see the comprehensive list take a look at the look at - the Jalview 2.8 Release Notes. -

- Highlights in Jalview Version 2.8 - -

- Issues resolved in the Jalview Desktop -

- -

- Issues specific to the JalviewLite Applet -

- -

- Issues affecting both applet and application -

- +

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