We are about to switch to a new forum software. Until then we have removed the registration on this forum.
I'm a sophomore Computer Science and Visual Arts and Technology double major at Stevens Institute. While generally I do lower level systems programming, I started learning Processing for an Art class this semester and fell in love instantly. While the programmer in me hates how abstracted Processing can be, and how easy it is to make bad code, the artist in me loves how quick and easy it is to make working applications.
I've seen two ideas so far that I'd be interested in submitting a proposal for. My first complaint with Processing was the PDE. While most my classmates don't really notice it, after working with Eclipse and Sublime Text the PDE seems really slow, clunky, and is missing lots of features. I see two possible solutions to this: Editing the PDE to create a smoother workflow with some easier to use features such as multiple window/viewport support, documentation support, better autocomplete, etc; OR fix the processing-java compiler to be much easier to use with many more features, examples, and documentation. Which would you guys prefer? What features would be best to add?
The other idea came from another proposer: a Game library. A lot of my programming skills are focused towards gaming. I've been taking classes and learning OpenGL and Game Engine Architecture, so this idea is right down my alley. We could either build a new library, or try and port pieces of libGDX which is built in Java. I think a lot of users of Processing are building games, and specific libraries for that would not only attract more users, but also help current users learn the intricacies of how large-scale video games work. What features should be focused on? Is this too complicated for Processing's scope of simplifying things?
I am really excited to work with you guys and really want to try and get a solid project going.