> Building one at the moment. Nothing to share though since there's
> nothing specific about it. It just a web app.
>
I don't actually need to link to access as this will be a complete rewrite.
> Key is PYTHON. Django is very modular and loosely couple and you get
> immediate access to the world of Python in your models and views and
> then only the sky is the limit.
> If there's a Python module for ODBC, Access, etc. then YES it can be
> used in Django.
>
I am already sold on Django/Python, but my question is are there good
descriptions of the benefits written for non-technical people?
Benefits of Django as well as the whole idea of a web app.
Thanks,
Matthew
also look at satchmo
--
regards
KG
http://lawgon.livejournal.com
A project I worked on over the summer used a Database that was 130
tables, and getting 1gb updates every 2 minutes. I was witting a new
web app to do calculations on the data and the company wanted to use
Java since thats what they knew best and had spend huge amounts of
money (1 mil +) to support with Sun Servers, and such. But I knew
python and django would be a better fit for this particular app, but
the boss wouldnt listen. So we had 10 Developers working on the Java
version (Including me) and over 3 months we got it about 85% done,
though it had no unit tests. During the same three months, I worked on
my own time after work and basically had no life for the whole time, I
was able to get the web app 100% complete with unit tests. That
convinced my boss that Django was a good fit.
The site is an internal app that I cannot give access to (And I
actually had to get permission to give what info I have), but I can
say that Django is a suitable framework for what you are looking for.