X-Git-Url: http://source.jalview.org/gitweb/?a=blobdiff_plain;f=help%2Fhtml%2FwhatsNew.html;h=d1d141d30b133f0a400e7fb369ebe9cce029c4d5;hb=47fd498a6fe7d2e3350a9e87c526bf1e59d00be5;hp=1743f1c4fb6a7bf3589622812bf26752e8218d32;hpb=739e52dd5387687cce4831eaafa24116dcaddcb9;p=jalview.git
diff --git a/help/html/whatsNew.html b/help/html/whatsNew.html
index 1743f1c..d1d141d 100755
--- a/help/html/whatsNew.html
+++ b/help/html/whatsNew.html
@@ -24,55 +24,55 @@
- What's new ?
+ What's new in Jalview 2.10.1 ?
- Jalview 2.10 is the next major release in the Jalview 2 series. Full
- details are in the Jalview
- 2.10 Release Notes, but the highlights are below.
+ 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.
-
- Highlights in Jalview 2.10
- - Ensembl sequence fetcher. Annotated Genes,
- transcripts and proteins can be retrieved via Jalview's new Ensembl REST
- client. Support for import of Ensembl data allows:
-
- - Sequence variant data. Jalview
- propagates variant annotation on genomic regions onto transcripts and
- protein products, complete with associated metadata such as
- clinical significance.
- - Aligned locus view. Transcripts
- retrieved for a gene identifier via the Ensembl or
- EnsemblGenomes sequence databases are automatically aligned to
- their reference genome, and introns hidden from the view.
-
- - Working with structures.
-
- - More accurate structure mappings.
- Jalview now utilises the PDBe's SIFTS database (at EMBL-EBI)
- to match structures
- to UniProt sequences, even for structures containing
- multiple copies of a sequence.
- - Import structures as mmCIF. Jalview
- now downloads data from the EMBL-EBI's PDBe site as mmCIF.
- This allows very large structures to be imported, such as the HIV virus capsid assembly.
-
- - UniProt Free Text Search. The new search
- dialog for UniProt allows you to browse and retrieve sequences
- from UniProt with free-text search and more structured queries
- - Reference sequence alignment view..
- Jalview 2.9 introduced support for reference sequences. In 2.10,
- when a reference sequence is defined for the alignment, the
- alignment column ruler is now numbered according to the reference
- sequence. The reference sequence for alignment views can also be
- saved and restored from Jalview projects.
- - Ensembl and ENA 'show cross-references'
- support.The Calculations menu's 'Show cross-references' will now
- offer Ensembl as well as EMBLCDS and Uniprot when CDS/Protein
- mapping data is available for download or display.
+ - More memory efficient
We've slimmed
+ down the consensus analysis data structures used by Jalview so
+ even wider alignments can be worked with.
+ - Select highlighted region
Press 'B'
+ or use the new menu option in the alignment window's Select menu
+ to mark columns containing highlighted regions generated from
+ structure selections, mouse-overs, or resulting from a Find
+ operation.
+ - New custom link mechanism for opening URLs
+ for database cross references.
If you have customised URL
+ links in your Jalview preferences, then you may already have seen
+ the warning dialog (see below).
+ - New command line export option for BioJS
+ MSAviewer
A number of small bugs with the HTML export
+ functions from the Jalview desktop were also fixed.
+ - Small but significant changes to the
+ physicochemical properties and consensus calculations
Threonine
+ is no longer considered a non-hydrophobic residue in the protein
+ conservation calculation, and minor bugs addressed in PID and
+ consensus colouring.
+ - Correct display of disulphide bond
+ features
In linked structure views, Jalview would
+ highlight all residues between in addition to the two linked
+ cysteines. The 'select columns by feature' function in the feature
+ settings would also select all intermediate columns.
+
+ 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$.
+