[Pythoncard-users] preliminary grid success

i was able to port the grid and vcr widgets
to work under the new components/ framework.
a simple demo of using a grid is attached.

i can work with grid.py two different ways:
    - just drop it in components/
        - this is the "standard" way
    - keep it local, and explicitly import it 

the grid demo should be self-contained - it uses an explicit
import.  it's almost as stunted as before, but it does
convert clicks into SelectEvents now.  the second two
grids don't do anything, but they are there because 
i soon want to demonstrate three 
different ways of supplying the data to the grid.

here are some questions and observations that
came up during the experiment:

- how are GridSpec's "self.events.extend()" and Widget's _events
  related?
    - in list.py
	- ListSpec only extends with 'select', but
        - List adds SelectEvent *and* MouseDobuleClickEvent
        - should ListSpec add "doubleclick", too?

- the import scheme masks syntax errors
    - res.loadComponentModule should log the error
    - makes it hard to find problems
	- only shows up as 
    - might have been a problem with the old import, too

- can i develop a spec in the old "declarative" format?
    - it's now python code
    - composite widgets will want to 

- how is GridSpec bound to Grid?
    - is it implicit in GridSpec.name?
    - is it implicint in that they are in the same file?


finally, if you want to add grid.py to the base distribution,
what are the "minimum essential requirements"?  if there is
interest, i will take responsibility for grid.py, at least
until it is minimally useful.  there is
a long todo list at the top of grid.py, to get things started,
but not all of the items are critical

jeff


__________________________________________________
Do You Yahoo!?
Check out Yahoo! Shopping and Yahoo! Auctions for all of
your unique holiday gifts! Buy at http://shopping.yahoo.com
or bid at http://auctions.yahoo.com