google-code-export / box2dweb

Automatically exported from code.google.com/p/box2dweb
0 stars 0 forks source link

Merge projects? #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Hi Uli

This is not an actual issue, but I could not contact you any other way. I 
thought you might want to get in touch with Jonas Wagner who has also written a 
parser to produce a JS box2d port from AS3, see here:

http://29a.ch/2010/4/17/box2d-2-flash-ported-javascript

His version is 2.0.2, so missing some cool features that 2.1 has. I am using 
his because its stable, else I'd be using yours as I need EdgeShapes and curves 
would be great, too.

I thought maybe together you and him could move things forward more steadily?

Original issue reported on code.google.com by nick.wig...@gmail.com on 25 Oct 2010 at 12:31

GoogleCodeExporter commented 9 years ago
Hi Nick,

thanks, I didn't know that. What is the problem with my version? I use it 
everyday without problems.

The only problem is IE at the moment. But also Jonas suggests to forget about 
IE.

Original comment by Uli.He...@googlemail.com on 27 Oct 2010 at 10:29

GoogleCodeExporter commented 9 years ago
Hi Uli,

I assumed there were some issues because on the Project Home page you state, "I 
removed the downloads, since the port hasn't been tested sufficiently, yet." 
That and your statements of known issues... made it sound like maybe the port 
wasn't stable? But maybe I read too much into that.

I also thought Jonas might have a way around that Dictionary problem, because 
he doesn't mention it on his blog... As for IE8, yeah, I agree with you both :D

Having said that, I saw one strange issue when using Jonas's version, but that 
seemed to disappear after a while -- I think it was in relation to how I was 
placing many static bodies on top of one another on startup. Of course, when 
things go wrong like this in a JS port, there's no static typing, so it's hard 
to know what broke, and where.

For this project, I'm moving things over to XNA with Box2d.XNA, since 
yesterday. HTML5+JS has been cool, and is a super option for simple gameplay 
prototyping.

Original comment by nick.wig...@gmail.com on 27 Oct 2010 at 11:07

GoogleCodeExporter commented 9 years ago
Hi Nick,

>>> I assumed there were some issues because on the Project Home page you 
state, "I removed the downloads, since the port hasn't been tested 
sufficiently, yet."

I think it's time to add the downloads again ;)
After looking into Jonas' code I think that my port should be more stable than 
his. It seems that his converter doesn't even care about getters and setters.

>>>  when things go wrong like this in a JS port, there's no static typing

My converter tracks variable-assignments and converts types if necessary (e.g. 
var i:int = 0.5 => var i = parseInt(0.5)).

>>> For this project, I'm moving things over to XNA with Box2d.XNA

I'm using Box2Dweb, because IMO writing JavaScript takes less time than any 
other language. After developing the specific parts as tiny web apps I'm going 
to assemble everything using C++ ;)

Original comment by Uli.He...@googlemail.com on 28 Oct 2010 at 12:38

GoogleCodeExporter commented 9 years ago
marked as invalid, since this is not an actual bug report.

Original comment by Uli.He...@googlemail.com on 5 Nov 2010 at 10:55