Hi Keith That sounds reasonable to me.... although I haven't been through the implementation process of an 'EntrySource' myself. Others may comment further if bits are missing.
Artemis (v6) already can take URL's on the command line (equivalent to GET I guess) so you may want to look at extending that to POST: art http://www.sanger.ac.uk/Software/Artemis/v6/af063097.embl You are right there is an 'invisible_qualifiers' list that could be used. Tim On Tue, 24 Aug 2004, Keith James wrote: > > It's been a long time since I last looked inside Artemis (pre the > Swing version), so I'm trying to refresh my memory. > > Say I had an hhtp server which could send out bits of > sequence/annotation for clients doing a GET and receieve updates when > they did a POST. > > If I wanted Artemis to be such a client, am I right in thinking I > would need to create just these: > > SomeSortOfEntrySource implements EntrySource > SomeSortOfEntry implements Entry > SomeSortOfFeature implements Feature > SomeSortOfSequence implements Sequence > > If I model this on the CORBA system I can make a RWSomeSortOfFeature > analagous to a RWCorbaFeature. This would implement VersionedFeature > instead of DateStampFeature, but with the same purpose - optimistic > locking. > > Does this sound reasonably sane? You can see where I'm going with > this... > > I'll probably want to take a complex gene structure and flatten into > generic features, then build it back up again later. That would mean > keeping parent/child tags as qualifiers. Presumably it's up to the > RWSomeSortOfFeature to stop people deleting these? > > Has anyone requested the ability to make some qualifiers invisible to > the in the viewer/editor/ > > cheers, > > Keith > > -- > > - Keith James <[EMAIL PROTECTED]> Microarray Facility, Team 65 - > - The Wellcome Trust Sanger Institute, Hinxton, Cambridge, UK - > The Wellcome Trust Sanger Institute Wellcome Trust Genome Campus, Hinxton, Cambridge, CB10 1SA, UK
