We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Today I'm releasing the first alpha of what will hopefully become proscene2. For the impatient, download it and extract it to your sketchbook
libraries folder (automatic importing proscene from your PDE is only available for stable releases, currently v-1.2.0). Even though the library has almost been completely rewritten from the ground up, you will find most of the current examples with some minor changes, plus a whole bunch of new ones. There's also a new project home and its code is now kindly hosted at github. Read on for some more details.
Some years ago Proscene was firstly designed to ease interactivity of 3D Processing scenes through standard input devices: mouse and keyboard. Then at some point when we noticed that some of you guys were interacting within your sketches using "non-standard" Human Interface Devices (HIDs), we decided to add some basic support to them, but the code never really makes it to Proscene's core: the
iFrame class hierarchy. The reason for that being that
iFrames and (standard) input events were tightly coupled. Our first Proscene design also lacked providing means to interact using a touch device, mainly because back in 2010 when it was first released, there wasn't a Processing "android mode". On the other hand, as with any other Processing library, publishing a sketch online was a matter of exporting it as a java applet. However, this is no longer the case and, as most of you probably know, Java-Script (JS) has almost ended up replacing java applets in Processing2.
size(640, 360, P2D); scene = new Scene(this);). Yes, it's not part of the above motivation, but that would be cool ;)
and while it has been progress for the third challenge, this release only covers the first two of them.
scalingto be added to
iFrameswhich are now defined by their
scaling. As a result, moving the viewpoint around, picking and manipulating objects, adding keyframes to a camera path, etc., are all now possible in 2D too.
iFramemanipulations) supported by Proscene, by defining a set of virtual events (called
TerseEvents) which represents an interface between them. An important
TerseEventspecialization is a
MotionEventwhich is defined according to its degrees-of-freedom (DOFs), making it particularly suitable to applications requiring all sorts of kinematics computations, such as those involved in
iFramemanipulations. Adding an HID thus "only" requires reducing hardware input events to
MotionEvents, from which all Proscene actions are now implemented.
Expect more technical details regarding Proscene2 and its new package structure with the next pre-releases.
This release is mainly aimed at testers and enthusiasts that wanna try the new features from perfectly well undocumented examples ;)