Hi all!
I've got a branch I'd like for you to take a look at at your convenience. It
completely removes zca from the pyogp.lib.base package (though i have left
behind the interfaces.py files for reference for now). It does NOT remove
all zope references throughout pyogp. Once the zca-removal branch merges
into trunk, I suppose we'd explore what else to trim...
merge-enus-zca-pyogp is a very recent cut of pyogp.lib.base/trunk, with the
enus-zca-removal branch merged into it.
to check out the branch, you can just switch to the repo in an existing dev
sandbox.
1. cd {libdev/trunk} - aka the root of your checkout
2. cd src/pyogp.lib.base
3. svn switch
https://svn.secondlife.com/svn/linden/projects/2008/pyogp/pyogp.lib.base/branches/merge-enus-zca-removal.
(to switch back: svn switch
https://svn.secondlife.com/svn/linden/projects/2008/pyogp/pyogp.lib.base/trunk.)
and you are ready to go!
Some highlights:
1. and now for the place where zca is nice... in general I have replaced
calls for utilities with a direct import of the reworked object that was
implementing that utility. I found a need to accomodate 2 networking
implementations in the lib, 1 for standard usage, 1 for the unit tests.
perhaps there are better solutions, but this is a stop gap to get the branch
available for checkin to the trunk... see agentdomain.py and login.txt for
samples
2 bin/login (aka example.py) has been updated. this is our base runtime test
3. all unit tests have been updated (run bin/client_unittest). zope tests
have been removed from the test run. there is still plenty of opportunity to
add tests.
4. moved the IPlaceAvatar class to a function in the AgentDomain class
5. merged the Avatar and Agent objects (added Agent.login)
6. In a related, but separate package, added
pyogp.interop.tests.test_sim_presence_nozca,
which fully tests the messaging sytem (including Saijanai's packet parsing
fixes). To run this, run bin/interop_testharness test_sim_presence_nozca
Please take a look and provide feedback! And let me know how I can help
improve things.
Note: This is NOT intended to be a final api or object model. We do
collectively need to identify a stable base api, and I envision that as
being next steps for the lib.
as always, in #pyogp
~e
_______________________________________________
Click here to unsubscribe or manage your list subscription:
https://lists.secondlife.com/cgi-bin/mailman/listinfo/pyogp
