[BioPython] gui + pickling
Cayte
katel@worldpath.net
Sun, 14 May 2000 23:39:10 -0700
This is a multi-part message in MIME format.
------=_NextPart_000_0023_01BFBDFD.9A7E3080
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Maybe, Brad and I should coordinate our experiments, because I started =
a gui prototype and I was thinking of how to add persistence. The =
prototype gui is at bio.perl.org/pub/katel/biopython/Bio/ on ftp. The =
gui is a first cut. A first cut is all I can do at this time:), but I =
just received a Tkinter manual in the mail. Hopefully, this summer, I =
can curl up with the Tkinter book, while I'm camping on weekend.
I thought of adding a transaction class that could be shelved or =
pickled. The class would have attributes
index
alphabet
translation table
operation ( translate, transcribe. backtranslate, etc )
input sequence
output sequence
The transactions could be stored to a file. A printer utility could =
pretty print the transactions.
Re back translate. I wonder if we should use the autodetect for the =
alphabet. Asking the user to pick an alphabet may be a complication we =
don't need at the prototype stage.
Cayte
------=_NextPart_000_0023_01BFBDFD.9A7E3080
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2> Maybe, Brad and I should coordinate our =
experiments,=20
because I started a gui prototype and I was thinking of how to add=20
persistence. The prototype gui is at=20
bio.perl.org/pub/katel/biopython/Bio/ on ftp. The gui is a first=20
cut. A first cut is all I can do at this time:), but I just =
received=20
a Tkinter manual in the mail. Hopefully, this summer, I can curl =
up with=20
the Tkinter book, while I'm camping on weekend.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2> I thought of adding a transaction class that =
could be=20
shelved or pickled. The class would =
have attributes</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2> index</FONT></DIV>
<DIV><FONT size=3D2> alphabet</FONT></DIV>
<DIV><FONT size=3D2> translation table</FONT></DIV>
<DIV><FONT size=3D2> operation ( translate, =
transcribe.=20
backtranslate, etc )</FONT></DIV>
<DIV><FONT size=3D2> input sequence</FONT></DIV>
<DIV><FONT size=3D2> output sequence</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT size=3D2> The transactions could be stored to a =
file. =20
A printer utility could pretty print the transactions.</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT size=3D2> Re back translate. I wonder if we =
should=20
use the autodetect for the alphabet. Asking the user to pick an =
alphabet=20
may be a complication we don't need at the prototype stage.</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV><FONT=20
size=3D2> &nbs=
p;  =
; =
&=
nbsp; =20
Cayte</FONT></DIV></BODY></HTML>
------=_NextPart_000_0023_01BFBDFD.9A7E3080--