X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=8018887d2917a478af88ab5ed3c7621d7cf18967;hp=39ef82f1fc460d65c7c71428206cf72002eb3c3a;hpb=f6a7e5514230be7ea8c2d4cccb504b4ed95f80ef;p=jalview.git diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html index 39ef82f..d1d141d 100755 --- a/help/html/whatsNew.html +++ b/help/html/whatsNew.html @@ -1,199 +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 brand new logo, which you'll see in file - browsers, splash screens, and also on the new look Jalview site.

-

- In addition to our new look, Jalview 2.8 includes a number of new - features.. some of which have been in development since July 2010. The - highlights are below, and - as usual, for a comprehensive list, take a - look at the Jalview 2.8 Release - Notes. -

-

- Highlights in Jalview Version 2.8 -

- -

- Issues Resolved (a select list - see the release history for full details) - -

-

- Issues in the Jalview Desktop -

- - Issues specific to the JalviewLite Applet - - Issues affecting both applet and application - +

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