Repository navigation
Task Tracker: Port examples from Java to Python #1
Description
The sub-issues below track the progress of the collaborative porting efforts. Check the README for more details.
For more info about libprocessing and mewnala, see the libprocessing README.
Expand the list below and see individual sub-issues for instructions.
See also this kanban board: Porting Processing Examples from Java → Python
Activity
Basics/Arrays#2Basics/Camera#6Basics/Color#10Basics/Control#19Basics/Data#25Basics/Form#32Basics/Image#41Basics/Input#49Basics/Lights#62Basics/Math#69Basics/Objects#90Basics/Shape#95Basics/Structure#102Basics/Transform#11312 remaining items
Topics/Image Processing#192Topics/Interaction#205Topics/Motion#213Topics/Shaders#224Topics/Simulate#240Topics/Textures#248Topics/Vectors#254Demos/Graphics#258Demos/Performance#274Demos/Tests#285SableRaf commentedon Jul 13, 2026
@catilac I just realized that the actual examples for Python mode are at https://github.com/jdf/processing.py/tree/master/mode/examples
That includes many of the original Java examples ported to Python, as well as some Python-specific example folders that you and @tychedelia may want to check out, like "Python Mode Differences" or "Contributed Libraries in Python".
Would it make sense to use these as the starting point instead of the Java examples? Not a huge diff but they are already closer to the target language some of them include more detailed comments than their Java counterpart. At least that was the case in this example I just ported #293 as well as a couple others I quickly looked at.
SableRaf commentedon Jul 14, 2026
I did a quick spike for research purposes using this script to do a naive translation of the Python examples to mewnala, and another script that does a static analysis of the ported examples to find keywords used by the examples that are not exported by mewnala 0.0.7. The scripts are not trying to be the most accurate so take this with a grain of salt but I think there's still value in the results.
The table below lists those potentially missing API elements, ordered by the number of examples that use them. It's a noisy signal, and examples may not representative of how ppl actually use Processing, but it could be useful as a reference point for discussing what parts of the API to prioritize. cc @catilac @tychedelia
A more detailed report, including the examples affected, can be found in this gist.
AI disclosure and other caveats can be found in the README.
Note: some of the reference links below may be broken (especially some of the constants which don't have a reference page):
P3DsincosrandomPIPVectorP2Dframe_rateradiansshapecreate_shapeTWO_PIload_shaderlightssmoothtextmillisconstrainshaderatan2distRGBnoisepixelsload_pixelsupdate_pixelscreate_graphicsload_shapetext_fonttext_aligntexturebegin_closed_shapecreate_fontHSBredxrangesqrtTAUno_smoothprintlnreset_shaderPGLcamerabegin_p_g_lsecondtext_sizeblueCODEDGROUPnoise_detailperspectiveQUADsphere_detailtexture_modeHALF_PIminuterandom_gaussianasinbrightnessDISABLE_DEPTH_MASKELLIPSEggreenhinthourload_stringsnfNORMALorthoPFontPImageprint_arrayRECTSPHEREdraw_lengthIntBufferproductionselfend_p_g_llerplerp_colornormsqthetaambientambient_lightARGBaxiomBOXceilcurve_tightnessDEG_TO_RADframegenerationsgetIMAGElight_specularlinkload_fontload_tablemagno_lightsnullOPENGLPShapepush_styleREPEATrequest_imageresetsavesave_tablespecularstart_lengthtantext_ascenttext_descenttext_widthtexture_wrapthisulgens commentedon Aug 10, 2026
@SableRaf
The link doesn't work 👀
SableRaf commentedon Aug 10, 2026
@ulgens Thanks for the heads up. It should be public now.
ulgens commentedon Aug 10, 2026
I can access it now, thank you.