Re: [ccp4bb] CCP4 GUI

Protein crystallography Programs for crystallography X-ray detectors
Basic tutorials:
Protein Peptide

CCP4bb navigation

CCP4bb <-- 2007 <-- May 2007 <-- 10 May 2007

Previous message:
Subject: Biophysicist position in crystallography at LBNL, SF Bay Area
From: Amy Pagsolingan avpagsolingan {- at -} LBL {- dot -} GOV
Date: 2007-05-10

Next message:
Subject: Re: CCP4 GUI
From: "Winn, MD (Martyn)" m {- dot -} d {- dot -} winn {- at -} DL {- dot -} AC {- dot -} UK
Date: 2007-05-10

Subject: Re: CCP4 GUI
From: Peter Adrian Meyer pam52 {- at -} CORNELL {- dot -} EDU
Date: 2007-05-10

Hopefully my offhand remark wasn't taken as a criticism of ccp4i (it
wasn't meant as such); but seeing as I don't use it, it's not a place
where I could tell someone how to find an option.

> As developers, we also have to think about long-term maintainability.
> Options, in particular little-used options, can soon become out-of-date.

This is might be a bad idea*, but I'll throw it out there anyhow: What
about the storing program keywords in a grammer file (something along the
lines of yacc/lex), reading gui options from the grammer, and generating a
parser subroutine from the grammer for the data-processing programs?
This would mean changes to the parser library (and to a large number of
existing programs which already work), but would eliminate the issue of
keeping the gui options in sync with the program options.

Pete

*specifically, bad idea type #2 - probably more trouble than it's worth

Pete Meyer
Fu Lab
BMCB grad student
Cornell University

CCP4bb navigation

CCP4bb <-- 2007 <-- May 2007 <-- 10 May 2007

Previous message:
Subject: Biophysicist position in crystallography at LBNL, SF Bay Area
From: Amy Pagsolingan avpagsolingan {- at -} LBL {- dot -} GOV
Date: 2007-05-10

Next message:
Subject: Re: CCP4 GUI
From: "Winn, MD (Martyn)" m {- dot -} d {- dot -} winn {- at -} DL {- dot -} AC {- dot -} UK
Date: 2007-05-10