I have been trying to figure out how to construct a hierarchical tree of
Features. This is a consequence of trying to write a SeqIOListener
that takes a stream of events generated from an XML parse and
constructs an in-memory sequence with nested Features on it. Can you tell
me whether I understa
On Tue, May 29, 2001 at 09:30:48AM +0100, Dr S.M. Huen wrote:
> I have been trying to figure out how to construct a hierarchical tree of
> Features. This is a consequence of trying to write a SeqIOListener
> that takes a stream of events generated from an XML parse and
> constructs an in-memory s
> "David" == S M Huen <[EMAIL PROTECTED]> writes:
[...]
David> If you could send me you renderer code I could have a look
David> at why it might be doing this. Do you have a
David> framing/clipping transform to put it in the panel like the
David> MultilineRenderer and Layered
hai all,
i apolagize if i ask u a simple and stupid question
i am in need of a tool which actually updates (daily or whenever it is
required - automatically ) my local genbank database(this is required for me
to keep track of replacing my draft sequences with the complete sequence)
if u have ans
Hi Subba,
The first file argument should be the name of your index file. All
following file names should be the names of sequence files. You can make
a new index file by running the CreateIndex program specifying the index
name (e.g. emblfiles), the format (e.g. embl, fasta, genbank) and the
> The annotation issue is a bit awkward, since if you create
> a feature with the annotation set to Annotation.EMPTY_ANNOTATION,
> you /can't/ add extra annotation properties. However, if you make
This is arguably a bug. Can we intercept this in the feature constructor
and replace it with somet
Hi-
Is it reasonable to include the Logging API? I am in two minds about this.
On the up side it gives good information for debugging and fine tunning
which can be nice for group projects and it can also let you know what is
going on inside those more complicated objects.
On the downside it ten
I'm generally strongly against logging in library code. Especially in the
case of biojava where there's a nce seperation of interfaces and
implementation its pretty easy to create an aimplementation that logs and
delegates the real behaviour to a seperate implementation class.
Mike
> -Origi
