We are about to switch to a new forum software. Until then we have removed the registration on this forum.
My name is Will Hartman and I'm a sophomore (soon to be junior) computer science student at Worcester Polytechnic Institute in Massachusetts. I've been writing Java code for around three years now and have been using Processing for about one year.
First off, I just want to say that Processing is a really cool project that I love doing work in even though I've mostly just used it for experiments and little prototypes. I feel that the simplicity and speed of writing interactive graphical applications is addictive and exciting, both for visual artists and for beginning programmers. I feel that Processing's biggest strength and most valuable trait is its simplicity.
I was introduced to Processing by my sister who is an art student who focuses on art and technology. A couple of weeks ago I went to a gallery show put on by seniors from her school where there were a number of digital pieces. A few of these pieces used video game controllers to allow the viewer to interact with them. Speaking to the artists, I learned that they found controllers to be valuable tools in communicating with the user, but I got the impression the artists found the controllers complicated to write code for.
I immediately identified with this, as I had struggled with lacking controller libraries in Java while working on various hobby projects. These libraries' problems are pretty major, like incomplete support for Xbox controllers on windows and the inability to properly handle controller connection or removal at runtime.
The existing controller libraries in processing are pretty hard to use and fail in the same places(due to the underlying deficiencies in Java controller libraries). I'm interesting in fixing this by modifying an already existing library to fix its issues and writing a API in Processing that will be simple to use. This would all be packaged in a Processing library.
I'm aiming to create a library where the user does not need to worry about library capabilities or making controller mappings. Using controllers should be as easy as accessing keyboard or mouse state.