Hi Peter,
Yes, the problems exist in this engine. It needs future works. Now, Google
suggests us the students "pencil-down" after August 18th and make final
evaluation on these gsoc projects. So, during this time, I didn't add any codes
and functions. The version of this physics engine
Hey all!
I wondered if the these two issues will be addressed?
1) The fact that heavy mass objects fall through static objects with low
mass. Static objects should probably be treated like inf mass.
(it's as if they first hit water and then slowly sink through)
2) Locked joint rotation. There s
Hello again.
Is there a list of planned features for the finished module?
Specifically, I'm thinking of joint restrictions on rotation, as an example
joint.restriction = 10, 349 # joint can only rotate between 10 and 349
# degrees.
joint.restriction = -10, 10 # joint
Hi there, Zhang!
I think what Brian meant is that we should get rid off all warnings now so
we can find warnings that may be of concern easier.
Also, I keep nagging :) but I'd really like to see name changes of the types
to follow the PEP. I also found a spelling error on line 152 in rev 1390
On, Sun Jun 22, 2008, Peter Gebauer wrote:
> > Something must be wrong on your side with that. Anything fine here.
>
> Yeah, SVN tried merging with the sources I changed, that was the prob. But
> I'm definately getting warnings.
>
> > For the unix way of building software.
>
> The Python setu
Hi,
Thank you for your attention. In fact, these warnings are because of forward
types' declarations. When I compile these codes with my VC solution, there are
no such warnings, However, with GCC compiler, These warnings tell us such types
may be not defined yet. So, the warnings won't cau
On Sun, Jun 22, 2008 at 4:21 AM, Peter Gebauer <
[EMAIL PROTECTED]> wrote:
> Yeah, SVN tried merging with the sources I changed, that was the prob. But
> I'm definately getting warnings.
>
> Yeah, everybody gets the warnings - they were looked over to check for
obvious errors, and are now mostly c
> Something must be wrong on your side with that. Anything fine here.
Yeah, SVN tried merging with the sources I changed, that was the prob. But
I'm definately getting warnings.
> For the unix way of building software.
The Python setup seems to work fine though.
As for testing, I have no prob
On, Sat Jun 21, 2008, Peter Gebauer wrote:
> Hey there!
>
> Who currently has write access to the SVN repos? I checked out and tested
> 1382 just now and aside from failing compile it also yielded plenty of
> warnings. Do you want me to help clean up? For instance, there was SVN
> versioning d
The module compiles and installs with MinGW and distutils. It can be
imported. world and body instances can be created. Looks good so far.
Lenard
帆 张 wrote:
> Hi,
> Now, Makefile and setup.py is added. I've tested compilation on my
> Ubuntu Linux, it works well.
> just go to the project path and
Hey there!
Who currently has write access to the SVN repos? I checked out and tested
1382 just now and aside from failing compile it also yielded plenty of
warnings. Do you want me to help clean up? For instance, there was SVN
versioning diffs saved to the repos, that's easy to avoid, just make
Hi,
Now, Makefile and setup.py is added. I've tested compilation on my Ubuntu
Linux, it works well.
just go to the project path and type following command: "sudo ./setup.py
install"
Best wishes
Zhang Fan
Marcus von Appen <[EMAIL PROTECTED]> 写道：
On, Fri Jun 20, 2008, Peter Gebauer
Hi Richard!
We've gone through the details already, pymunk is not a Python extension,
but both Zhang and I seem to have had the same idea and share design goals
currently outside the scope of pymunk.
/Peter
On 2008-06-21 (Sat) 11:43, Richard Jones wrote:
> On Thu, 19 Jun 2008, Peter Gebauer wr
# hello.
#
# I've prepared a set of python computer instructions for your consideration.
# Warning: Not safe for work! But it's the weekend, so that doesn't matter.
# TODO: these computer instructions could be optimised.Only achieves 0.5 fps.
def inately__for_your_consideration():
# a quote f
On Thu, 19 Jun 2008, Peter Gebauer wrote:
> I read Zhang Fan's post regarding his gsoc project, I've been looking to do
> something similar, a Python extension for an already existing library.
> So far I've extended Chipmunk partially over a few days of prototyping, but
> there's no point in having
On, Fri Jun 20, 2008, Jake b wrote:
> Zhang: What font do I need to view your name? [ I'm using winXP, firefox3
> and it's showing as 0x5e06 0x5f20 ]
Go to the control panel -> region and language settings and check the
"support for east asian languages" option (on the second register, I
think).
Zhang: What font do I need to view your name? [ I'm using winXP, firefox3
and it's showing as 0x5e06 0x5f20 ]
2008/6/19 帆 张 <[EMAIL PROTECTED]>:
> Hi,
>
> In fact, just as I said before, all data structures of this engine are
> based on python basic type data structures. 2d vector type is just sa
On, Fri Jun 20, 2008, Peter Gebauer wrote:
> Hi again!
>
> I've tried compiling what you've submitted so far, it fails with many
> errors. For instance, what's with the double typedef's? Are you still just
> prototyping?
>
> Also, I'm writing cmake build scripts to test your code, is anybody e
Hi again!
I've tried compiling what you've submitted so far, it fails with many
errors. For instance, what's with the double typedef's? Are you still just
prototyping?
Also, I'm writing cmake build scripts to test your code, is anybody else
interrested in this or should I use whatever PyGame i
Hi,
In fact, just as I said before, all data structures of this engine are based
on python basic type data structures. 2d vector type is just same as complex
type in concept and C implementation, so I just use Python complex type and add
some functions for advanced vector usages. I think m
Thanks for the clarification, Zhang and Peter. I love playing with
physics stuff, so I'm pretty excited about this. Now just imagine the
possibilities of combining physics and computer vision :-)
Nirav
On Thu, Jun 19, 2008 at 8:57 PM, Peter Gebauer
<[EMAIL PROTECTED]> wrote:
> Hi Nirav!
>
> As
On, Thu Jun 19, 2008, Peter Gebauer wrote:
> Hello!
>
> Yes, I've been looking continously at your source codes, I saw you were
> getting your Python C structs together yesterday, nice. My first advice
> would be this: all types/classes must start with capital case letter. I saw
> in your docu
Hello!
Yes, I've been looking continously at your source codes, I saw you were
getting your Python C structs together yesterday, nice. My first advice
would be this: all types/classes must start with capital case letter. I saw
in your documentation that your prototype API used lowercase, I thin
Hi Nirav!
As you can see from Zhang's post there's a difference between making soft
bindings using ctypes and hard bindings using the Python C API.
While ctypes is convenient to use and easy to modify since only Python code
is involved, it lacks the ability to let the programmer to extend Python
Hi ,
Thank you very much, I'd like to see your advices and get help from you. I
also want to tell the difference between chipmunk(and Pymunk) and this project,
this one is not separated with python, all of its basic data structures are
based on python data structures, which means it can b
I may be missing something, but aren't there already python bindings
for Chipmunk? http://code.google.com/p/pymunk/
I've only experienced it as http://wiki.laptop.org/go/Pymunx although
they use Box2d now: http://elements.linuxuser.at/
Nirav
On Thu, Jun 19, 2008 at 12:23 AM, Peter Gebauer
<[EMAI
Hi!
I read Zhang Fan's post regarding his gsoc project, I've been looking to do
something similar, a Python extension for an already existing library.
So far I've extended Chipmunk partially over a few days of prototyping, but
there's no point in having two projects doing the same thing, I'd lik
27 matches
Mail list logo
