Many questions about processing, processing.js, etc

microsi

Many questions about processing, processing.js, etc

in Processing with Other Languages • 2 years ago

So, I've known about processing for a few years but never really had any use for it.

Recently I've been increasingly interesting in topics like game system emulation or retro game development so processing might come in hand.

So, the first question should be asked quite a lot but I didn't manage to pull relevant results using the forum search or google:

In which aspects do processing and processing.js differ the most? I'm comfortable with both languages, so I'm really after technical differences.

What are the advantages disadvantages of each?

Another question: how is developing with processing different from using for example awt's graphics? I'm guessing processing does rely on it, but still, from a developer's perspective, what's most significantly different?

Does processing or processing.js support collision detection?

Replies(1)

PhiLho

Re: Many questions about processing, processing.js, etc

2 years ago

Differences: perhaps speed for P, ease of deployment (except on old IE...) for PJS. P has lot of libraries that cannot work with PJS. And more.
Advantages/disadvantages: see above...

Yes, Processing relies on AWT for display. It hides some complexities, transforms Java to a kind of procedural language, hiding (in a first time) the complexity of object-oriented programming: in general, it hides objects, in favor of simple function calls.

Collision detection: that's not Flash, so it isn't built in, as there are no graphic objects. You have to manage these collisions yourself, algorithmically (perhaps with the help of a library). There are plenty of examples in the forums.

Top Reply