More ACD GUI bits

[James Bonfield]

On Wed, Jan 10, 2001 at 04:29:52PM +0000, Peter Rice wrote:
> group: seqs [ info: "Select sequences" ]
> 
> sequence: sequencea [ ..... ]
> 
> endgroup: seqs
> 
> Like your 'frames', groups could be nested.

That's acceptable to me too. Initially I had a hierarchical method:

frame: seqs [
       info: "Select sequences"
 
       sequence: sequencea [ ..... ]
] 

This was easy for me to parse, but I guess it completely breaks the normal ACD 
structure :-} Hence my other suggested change.

> ACD should allow missing endgroups, but -acdpretty should put them in :-)

Missing endgroups wouldn't make it hard to parse (for me). A new group just
appends on to the existing 'path' and the endgroup pops it off. I guess you'd
disallow the following case:

group: g1 [...]
group: g2 [...]
endgroup: g1
endgroup: g2

If so, then we do not need to specify which group is being ended.

> All options within a group would be defined together in the ACD file, and
> prompted for  together. This will keep dependencies in the right order to
> simplify GUIs.

For generating HTML this is probably important. For my own work it doesn't
matter as the order of items in a dialogue does not need to be the same as the 
order of tcl code used to generate the items.

James

-- 
James Bonfield (jkb at mrc-lmb.cam.ac.uk)   Tel: 01223 402499   Fax: 01223 213556
Medical Research Council - Laboratory of Molecular Biology,
Hills Road, Cambridge, CB2 2QH, England.
Also see Staden Package WWW site at http://www.mrc-lmb.cam.ac.uk/pubseq/