[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-4296":3},{"id":4,"name":5,"fullName":6,"owner":5,"repo":5,"description":7,"homepage":8,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":15,"stars30d":16,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":17,"rankGlobal":9,"rankLanguage":9,"license":18,"archived":19,"fork":19,"defaultBranch":20,"hasWiki":21,"hasPages":19,"topics":22,"createdAt":9,"pushedAt":9,"updatedAt":23,"readmeContent":24,"aiSummary":25,"trendingCount":15,"starSnapshotCount":15,"syncStatus":16,"lastSyncTime":26,"discoverSource":27},4296,"processing","processing\u002Fprocessing","⚠️ Processing moved to processing\u002Fprocessing4 ⚠️","http:\u002F\u002Fprocessing.org",null,"Java",6489,1475,412,472,0,2,40.51,"Other",false,"master",true,[],"2026-06-12 02:01:01","\n\n>[!WARNING]\n> # Development has moved to [a new repository](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing4\u002F). \n\nSince the release of Processing 3.5.4 in January 2020, development has continued in a new repository: [processing\u002Fprocessing4](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing4\u002F).\n\nWe chose to move to a new repository so that we could clean out old files accumulated over the last 20 years.\n\nTo report bugs or request features, please open a [new issue](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing4\u002Fissues\u002Fnew\u002Fchoose) on the Processing 4 repository.\n\n\u003C!-- Is there not a better way to do a callout box? -->\n\u003C!-- Yes there is! -->\n\n~~Processing~~\n==========\n\n~~This is the official source code for the [Processing](http:\u002F\u002Fprocessing.org) Development Environment (PDE),\nthe “core” and the libraries that are included with the [download](http:\u002F\u002Fprocessing.org\u002Fdownload).~~\n\n~~__I've found a bug!__~~\n~~Let us know [here](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing\u002Fissues) (after first checking if someone has already posted a similar problem).\nIf it's a reference, web site, or examples issue, take that up with folks [here](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing-docs\u002Fissues).\nThere are also separate locations for [Android Mode](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing-android\u002Fissues), or the [Video](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing-video\u002Fissues) and [Sound](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing-sound\u002Fissues) libraries.\nThe [processing.js](http:\u002F\u002Fprocessingjs.org) project is not affiliated with us, but you can find their issue tracker [here](https:\u002F\u002Fgithub.com\u002Fprocessing-js\u002Fprocessing-js\u002Fissues).~~\n\n~~__Locked Issues__\nWhere possible, I've started locking issues once resolved. This helps reduce the amount of noise from folks adding to an issue that's been closed for years. Because this project has existed for a long time and we have thousands of closed issues, lots of them may sound similar to an issue you're having. But if there's a new problem, it'll be missed if it's lost in a comment added to an already closed issue. I don't like to lock issues because it cuts off conversation, but it's better than legitimate problems being missed. Once an issue has been resolved for 30 days, it will automatically lock.~~\n\n~~__That [processing-bugs](https:\u002F\u002Fgithub.com\u002Fprocessing-bugs) fella is suspicious.__\nThe issues list has been imported from Google Code, so there are many spurious references\namongst them since the numbering changed. Basically, any time you see references to\nchanges made by [processing-bugs](https:\u002F\u002Fgithub.com\u002Fprocessing-bugs), it may be somewhat suspect.\nOver time this will clean itself up as bugs are fixed and new issues are added from within GitHub.\nHelp speed this process along by helping us!~~\n\n~~__Please help.__\nThe instructions for building the source [are here](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing\u002Fwiki\u002FBuild-Instructions).\nPlease help us fix problems, and if you're submitting code, following the [style guidelines](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing\u002Fwiki\u002FStyle-Guidelines) helps save me a lot of time.~~\n\n~~__And finally...__\nSomeday we'll also fix all these bugs, throw together hundreds of unit tests, and get rich off all this stuff that we're giving away for free. But not today.~~\n\n~~So in the meantime, I ask for your patience,\n[participation](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing\u002Fwiki\u002FProject-List),\nand [patches](https:\u002F\u002Fgithub.com\u002Fprocessing\u002Fprocessing\u002Fpulls).~~\n\n~~Ben Fry, 20 January 2019~~\n","Processing 是一个基于 Java 的编程语言和开发环境，专为电子艺术、视觉设计和交互式媒体创作而设计。它提供了简洁的语法和丰富的图形处理功能，使得用户能够快速创建出复杂的视觉效果和互动作品。Processing 支持多种平台，并且拥有庞大的社区支持与丰富的第三方库资源，便于扩展其功能。该工具非常适合艺术家、设计师以及对编程感兴趣的初学者用来学习基础概念或进行创意项目开发。尽管官方已经将主要开发工作转移到了 Processing 4 上，但 Processing 仍然是一个强大且易于上手的选择。","2026-06-11 02:59:29","top_language"]