Summarize your feature idea. (Why)
Many app developers will already do file parsing (eg: upload a Genbank) within their app, and then use SeqViz simply to render it. It's a bit weird for a viewer (presentation) to also do the file parsing. It's a cool trick, but then the consumer of the app doesn't get the benefit of using the parsed annotations/name/seq etc that we took from the files.
Describe your preferred solution. (What)
Break all file parsing into a new pkg, "seqparse" or something lame like that. Could also be used as a CLI and be broadly useful
Summarize your feature idea. (Why) Many app developers will already do file parsing (eg: upload a Genbank) within their app, and then use SeqViz simply to render it. It's a bit weird for a viewer (presentation) to also do the file parsing. It's a cool trick, but then the consumer of the app doesn't get the benefit of using the parsed annotations/name/seq etc that we took from the files.
Describe your preferred solution. (What) Break all file parsing into a new pkg, "seqparse" or something lame like that. Could also be used as a CLI and be broadly useful