GSOC 2018 - Enhancing p5py's Documentation and Features

Visualizer

Hello all!

My name is Nida, a third year undergraduate in Electronics and Communication. I am a graphics enthusiast, who continues to look for ways to render them in the simplest manner possible, through code.

Ever since I have read the documentation of p5py, a Python library for Processing, I have been looking for ways to use it to enhance Python's NumPy and SciPy modules, along with porting PDE sketches to Python.

Two of the issues listed on p5py's GitHub page caught my eye - porting smooth() and stroke_weight() to Python, and correcting the erroneous negative values generated by mouse_x and mouse_y - the very same issues I have been facing the past three weeks.

I would like to help out with these issues, along with adding a few more Python examples. Can you please advise me on how I may go about it?

shiffman

I should note that while we love and value work on documentation (it is just as important, if not more so, than the code itself!) Google Summer of Code does not permit solely documentation in a project. Writing examples, however, would count as code development!

Manindra29

I would like to help out with these issues, along with adding a few more Python examples. Can you please advise me on how I may go about it?

Can you be more specific? p5py is an open source python library. Fixing an issue would be the same process as debugging any other python code. You can find p5py source here: https://github.com/p5py/p5

theabhikpal

Two of the issues listed on p5py's GitHub page caught my eye - porting smooth() and stroke_weight() to Python,

This could be interesting, actually. Given it happens as a part of a larger effort to overhaul + refactor the internal OpenGL.

... correcting the erroneous negative values generated by mouse_x and mouse_y - the very same issues I have been facing the past three weeks.

Are you talking about Issue #16 https://github.com/p5py/p5/issues/16? I think it already has a fix at https://github.com/p5py/p5/pull/17. I've merged it to the develop branch already and it will be fixed in the next release.

Visualizer

Can you be more specific?

@Manindra29 here is an example - a Processing sketch of mine, which I recently attempted to port to Python (pardon the bugs!): https://github.com/the-visualizer/bike_roller

This could be interesting, actually. Given it happens as a part of a larger effort to overhaul + refactor the internal OpenGL.

@theabhikpal this might pose a problem for me. You see, I have very little knowledge about programming with OpenGL. However, I am willing to learn it, if the project requires me to use OpenGL.

Are you talking about Issue #16 https://github.com/p5py/p5/issues/16? I think it already has a fix at https://github.com/p5py/p5/pull/17. I've merged it to the develop branch already and it will be fixed in the next release.

I see. Looking forward to this fix in the next release, then!