Hi Seb. On 16 September 2014 04:34, Sebastian Wilzbach <[email protected]> wrote:
> I already upload the minified MSA code to a CDN, so just linking to sth. > like [1] should be easier. > Do you think it is important that the rendered web page works without > internet? > That's useful in some circumstances - particularly when connectivity is poor. The other issue is where the rendered alignment is to be deployed on a site where the domain policy is to avoid external code references, or - purely for speed, all dependencies are shipped locally. > > > 2. are the JSON/BSON structures employed by msaviewer sufficiently > standard that we can commit time to create new parsers/emitters in Jalview ? > > Nope. Imho a standard would require more than one person to agree on it. > > Point taken. How about stability/coverage ? > > we just write vanilla alignment, sequence feature and alignment > annotation files and improve msaviewer so its compatible with Jalview's > standard formats. > > Currently the msaviewer only allows a user to import alignment files - it > does not support the import of sequence features nor alignment annotation > files. > I will work on this. > Let's discuss what's possible over at JIRA http://issues.jalview.org/browse/JAL-1541 > > 3. My idea was to show a basic configuration dialog to toggle some options > of the msaviewer (before the generation of the JS files). > -> What is your preferred way to receive those changes? As git patch? > A git patch is fine - but I can also give you commit rights if you need them. Please work off the Release_2_8_2_Branch - that's what Mungo and are currently working on. Jim
_______________________________________________ Jalview-dev mailing list [email protected] http://www.compbio.dundee.ac.uk/mailman/listinfo/jalview-dev
