Are you using the schematics from our gel box project? And if not, how
about you upload some of the CAD files to describe the projet that you
are implementing? That would be really nice. Alternatively, there's
the electrophoresis.py script that was released on the list last
year-- and it even outputs in SVG format, which would be a suitable
format to attach in an email.
I'd suggest django for rapid web prototyping with python. You can even
expose the function signature as an HTML form automagically IIRC if
you just throw the parameters to the script into a class/object of
their own.
- Bryan
Django is the Bees Knees if you're making a web site, but probably
overkill if you're doing nothing more than putting a web front end on
a python script.
Not to discourage anyone from doing it as an exercise, of course. But
if a novice is reading this, they should be aware that digging into
Django to accomplish the task at hand is going to get them more than
they bargained for.
-Dan
How about you ask for help in interpreting what these mean?
> "wire a command line script like that to run from google appspot"
Google AppSpot hosts applications on their cloud/cluster, so a
developer can register an account and upload some applications, it's
kind of like virtualization.
> "throw a web front-end on it and run the script under mod_python or
> simply cgi"
The mod_python package is an addon for apache, there are many mod_*
packages for the apache web server. CGI is an ancient, though still
useful gateway interface method, and you either tell the apache in the
/etc/apache2/sites-available/000-default or /etc/apache2/httpd.conf
file that a certain directory is to be run as CGI or not (and then you
get to use your #!'s to say what particular interpreter should be
running the script, blah blah blah).
> "expose the function signature as an HTML form automagically IIRC if
> you just throw the parameters to the script into a class/object of
> their own"
Well, that's django-specific. What django does is take a class
definition and export that to a backend database like MySQL or
PostgreSQL- or really whatever other plugins the developers for django
have written- and for each of the variables there is a column in the
table, and then it knows the maximum lengths and so on to specify in
the HTML form elements per the W3C standards blah blah blah.
> "sanitizing form input and generally just providing a sane
> programming
> API for web-application tasks"
Haven't you ever had to deal with crappy data before? :-)
> Would you understand me if I discussed the realtive merits of
> lipofectamineLTX vs FUgene for tx into H1299s to generate permanent
> KIs using an ATF3 delta102-139/neo vector?
Yes.
> How about I just draw a picture of what I'm doing in Microsoft Paint
> and email it to you :-) ?
That would be like me keeping ethidium bromide gels with my food in
the refrigerator.
*chuckle* Point taken, Ellen. However, since the discussion in
question was over the best way to accomplish a specific programming
task, and was held largely between programmers, I think that the use
of programming gobbledygook was justified. (Yes, gobbledygook is the
right word here. Yes, I am a word geek.)
If you'd like to learn to program, I can point you to several
tutorials aimed at non-programmers. It's not hard.
> For example, when my computer tried to open that schematic of yours
> with a .py extention, it freaked out and did not know what to do. I'm
> sure there's a program out there somewhere that will open it, but why
> not just a drawing?
.py files are programs written in a language called Python. (Named
after Monty Python, not the snake.) The program that was suggested
will create a new blueprint for you based on certain parameters - the
thickness of the plastic you're using, etc.
> biolotechnology portion of this DIYbio movement seems so down-to-earth
> and uncomplicated, the preference for complicated computer stuff seems
> puzzling to me.
The biotech portion of the DIYbio movement seems complicated to me,
and the computer stuff seems simple ;-)
-DTC
I encourage anyone to do as much drawing as they like. There has been
a long history of blueprints and drawings in mechanical engineering
and for machine shops and craftsmen, even hobbyist craftsmen. There
are even international standards for drawing blueprints too, there's
all sorts of standards from ASCII, ASME, IEEE, tons of specialty
associations, and so on. But these days, computers describe hardware
more accurately and better than engineers can with pen and paper--
blueprints are of course still a cultural tradition, and if that's
what you're comfortable contributing, that's fine, but let the rest of
us package it up into a better form, or let us help you install Python
so that you don't repeat unnecessary work, etc.
That's actually what the discussion was about earlier =)