[Pyogp] making ground, and plans for tomorrow's pyogp meeting (aka Enus' office hours)

[Enus Linden]

pyogp is plugging along, and now that the basis for interop testing is
available, we are ready to plug even further.

The latest development is that Locklainn is the proud father of the
first OGP teleport executed by pyogp, and he isn't even sure that he was
successful because he left before confirming things! I did the grunt
work and parsed logs etc for him, and yes, we have lift off :) A bit
more work is necessary to make such an action easy for the client
library, but testing can and will proceed in the current context.

At tomorrow's pyogp meeting, I'd like to regroup in a way. I'd like to
present where pyogp is, where help could be used in the short term
(anyone feel like helping test OpenSim with pyogp.interop?), and what's
next.

Topics should cover:
how we want users to be able to work with the library, and does it
require refactoring
what's next?
and why do the tests in interop hang against OpenSim? :)
testing OGP in general

I'd like to commend the accomplishments to date. Thanks to all who have
been playing. Now, let's make us a good codebase....

see you tomorrow at 9:30

thanks, enus

[Christian Scholz]

Post by Enus Linden
pyogp is plugging along, and now that the basis for interop testing is
available, we are ready to plug even further.
The latest development is that Locklainn is the proud father of the
first OGP teleport executed by pyogp, and he isn't even sure that he was
successful because he left before confirming things! I did the grunt
work and parsed logs etc for him, and yes, we have lift off :) A bit
more work is necessary to make such an action easy for the client
library, but testing can and will proceed in the current context.

Wow, that's great news! :-) Good to hear that this fighting with those
packets did pay off! :-)

Post by Enus Linden
At tomorrow's pyogp meeting, I'd like to regroup in a way. I'd like to
present where pyogp is, where help could be used in the short term
(anyone feel like helping test OpenSim with pyogp.interop?), and what's
next.
how we want users to be able to work with the library, and does it
require refactoring
what's next?
and why do the tests in interop hang against OpenSim? :)
testing OGP in general

I would like to concentrate on some process first, maybe we can talk
about my proposal and finetune it and put it somewhere on the wiki then.
I would also like to have some smaller process for smaller changes like
for renaming files (as just suggested in a reply to Tess), moving files
from A to B (also in that reply). The renaming itself should not break
something but other changes might. So we should discuss how these are
done and tested (probably in a branch). It does not require the whole
process for implementing a new subsystem though.

As for how the user might want to work with a library I brainstormed a
little how I would like to use it and that's sort of in a high level
way. I might still need to setup threads to do send stuff to my region
connection and such but I might not want to work with packets directly.
I'd rather want to say

avatar.head_rotation(10,90,30)
avatar.update()

The latter then sends this information to the region (this of course
would also be called by the region thread automatically anyway).

I scribbled down a little how this might be implemented then:

http://svn.secondlife.com/trac/linden/browser/projects/2008/pyogp/sandbox/trunk/sandbox/mrtopf/notes/highlevel_api1.txt

This might not fit what's in the library right now and might not fit how
the protocol works but as said, it's more some rough ideas. I also
spotted some errors already but it was done at 1am or so ;-)

That being said, we probably have far too many topics for this meeting ;-)

I personally would like to concentrate on a process and how we
communicate right now because I at least am not always clear what state
the lib is in and who works on what and how that might look like.

So see you at 9:30! Great work everybody! :-)

-- Christian