From: Brian P. <bri...@in...> - 2012-05-30 18:34:15
|
And I can't disagree with you - it's a terrible attitude, generally speaking. Although it sounds like msconvert wouldn't be the only source of such files, so in this case it might not be all that cavalier. On Wed, May 30, 2012 at 11:16 AM, Jimmy Eng <jk...@gm...> wrote: > Brian, I'm just being a devils advocate here ... > > The "others will adapt" statement might be amended to "others will > adapt or not bother adapting as there are other ways to generate mgf > files and the percentage of users this affects is tiny". What about > a pipeline developer's response like "Well, msconvert generated mgf > files used to work with our pipeline. Here's the required TITLE > string that's the issue. Not sure why they broke it, maybe you can > ping the pwiz guys to give you an option to compliant mgf files like > msconvert used to do. Otherwise, here's a tool or workaround that you > can use to generate compliant mgf files until that msconvert fix > happens." > > Again, it will be a trivial update to Mascot2XML to support the > change. I'm just thinking the notion that others will automatically > adapt could be viewed as a bit presumptuous. > > On Wed, May 30, 2012 at 10:55 AM, Brian Pratt <bri...@in...> wrote: >> output file. A robust parser will use or ignore it, others will adapt >> and it probably won't be the first or last time for them. > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > proteowizard-developer mailing list > pro...@li... > https://lists.sourceforge.net/lists/listinfo/proteowizard-developer |