From: Jordan Krushen <jordan@kr...> - 2004-08-06 23:37:54
Am currently in the design phase for a client's online order processing
system, and I would very much like to build this using PyObjC, bindings
and Twisted as a back-end (speaking PB to a remote server). I know
there's currently a Twisted/PyObjC CFreactor bug, but I'm not quite
there yet anyway :)
The client would ideally have a bunch of Cocoa/Twisted clients at their
office speaking PB with the central server, and probably a Flash
front-end for a web app, speaking XML-RPC back to the server.
What I need is some advice from those of you who have written larger
apps using the bridge:
If the model and controller are in Python, and the model would just
set/get remote data via PB, how deep can Bindings be pushed?
Will I need entirely custom contoller code here, or will Bindings help
me simplify the process? I'm wondering if KVO/KVC being 'forwarded'
over PB to the remote object is doable. Anyone tried something this
foolish before? :) Does it make sense in MVC-speak to have the view
speak to my controller, which speaks to a remote PB model object, or
should I have a local model which is a shim in front of PB, so that KVO
doesn't have to extend into my remote objects?
I would also need to receive events from the remote server via PB (its
bi-directionality is one of the primary reasons for choosing it), so
assumedly I'd like my model object to send the proper KVO messages to
the interface when data changes.
I'm still playing with the best places to put things, and how usable
Bindings will be for something like this (mostly
master-detail-subdetail in this case).
Any advice? I'm hoping to document this to help provide a stronger
tutorial / reference for people struggling to get up to speed with
Cocoa/Python. I'm impressed with how much it does automatically (as
per Bob's password/bindings example), but much of it is still nebulous
(at least to me), and spread out over Apple's site and the PyObjC
I won't be able to disclose the code of this project due to the
contract terms, but I'd gladly present some generic tutorial
encompassing these things once I sort things out myself. Between
Cocoa, the bridge and Twisted, I believe it would result in a
thoroughly enjoyable development (and user) experience, and more
fleshed out documentation on this combination could prove very helpful.
Any other advice would be gratefully accepted as well :)
Get latest updates about Open Source Projects, Conferences and News.