On Feb 16, 2008 4:24 PM, Michael Hipp <Michael@hipp.com> wrote:

> The application I'm (re) writing automates an auction house. In simplest

> form we have tables sorta like this:

>

> customer /* List of pre-approved businesses we hope will buy stuff.

> reps /* The individual buyers from the customer companies

> widgets /* List of specific items we hope they will buy

> transactions /* List of items bought, fees attached, misc charges,

> payments made, etc.

> history /* Old transactions and widgets already finished but needed

> for historical reference.

> performance /* Statistical information about who bought what, when,

> price ranges, fees earned, best sellers, etc.

>

> Auction houses like this one are peculiar because they operate only once

> a week and have a whole 2 hours to make an entire week's worth of

> revenue. The database gets lots of hits in a short time and any problems

> are an instant crisis.

>

> So a typical scenario is:

> - Clerk calls up record for widget #302

> - Auctioneer sells it to bidder #103 which is actually rep #8 from

> customer #2091

> - Along with saving the (now sold) widget record, we enter

> transactions for the purchase price and programatic fees, enter

> stuff in the reps and customer database as well as performance.

> 4-5 tables might be hit at once from the editing of one field from

> one table.

> - Later when bidder wants to check out he makes payment (more

> transactions. - OR -

> - Bidder somehow needs to cancel that purchase and the whole thing

> must be unwound some hours later

>

> That's a smattering. Certainly not "enterprise" class. But plenty of

> places to screw up. And I'm pretty sure I found a lot of them. ;-)

Dabo can DEFINITELY handle this. As I understand it John has a lot

more complicated forms and he is running just fine. I have forms that

are about as complicated as yours and they run without a hitch. The

multiple bizobj transactions are not a problem at all.

>

> The original version was pure wxPython with my own homegrown MVC style

> and psycopg2 into PostgreSQL and a Linux server. All the pieces worked

> great. But every time someone wanted a new screen or a new report or

> just some modifications to an existing screen I wanted to go run and

> hide somewhere because I couldn't maintain it all if I had a whole

> platoon of programmers. So I'm looking for some "help" in the form of

> code I don't have to write.

I know that feeling...I used to be a wxPython programmer before

Dabo...You'll find that the Dabo code is about 5-10X smaller, even

more than that if you were rolling the db stuff as well....

>

> I think I've settled on a mix of Dabo and Django with a common db layer

> (what many would call the "model"). I haven't entirely given up on doing

> it all in Django but the more I look at JavaScript libraries the more my

> head hurts. But certain things *need* to be on the web (for customer

> access) so, in that sense, it's not an option to only use Dabo.

>

Have you tried cherryPy? That might be the better way to go if all

you need is to display purchase info to a customer. Also, you should

check out mod_python for apache and see if that would fit your needs.

Either way, using dabo in conjunction with YAWF shouldn't be a

problem.

Cheers,

Nate L.