More 'About Storm'

[Gustavo Niemeyer]

Hi Ram,

> My questions would be like:
>
> -- what widget system would i use to work with this store? wxWidgets, Qt?
examples please...
> -- how would i populate these widgets with data from the data store?
> -- how would i make the widgets data aware?
> -- how would i commit the data updates in the widgets?
> -- how is the store used to refresh pagination in a datagrid?

As Tim pointed out, these questions are related to areas of your
application that Storm doesn't cover.  Storm is just the
database <=> object mapper.

I'll tackle the next few ones..

> -- can the store cache be used offline and then subsequently be used
> to update the backend db?

No, that's not supported.

> -- is the data store synchronized with the db? if not how do we check
> before committing updates?

It's synchronized at transaction boundaries.  Between transactions
values may be cached.

> -- how are database error messages handled by the store so we can
> inform users in the client application? or decide upon a course of
> action.

Exceptions are raised as per DBAPI2:

    http://www.python.org/dev/peps/pep-0249/

Exceptions may be found at storm.exceptions.

> -- how do we work with stored procedures at the back-end db?

It depends on where the stored procedure is hooked on.

> -- etc...
> -- python is cross-platform, but what is the store's compatibility
> with win32, gtk, kde? what are the nuances? (surely, i'm gonna get
> shot here by someone on the list as a stupid question)

Storm should work on the windows platform, even though I've never
tried myself.  It's fully compatible with gtk and kde, even though
saying so doesn't make much sense.

> whatever stuart says below is great, it throws a lot more light on
> storm.

I hope these will throw some more.

Regards,

-- 
Gustavo Niemeyer
http://niemeyer.net