Greetings. I’ve noticed a number of 404 errors in the Processing online reference . As some these errors also exist in the Processing reference included with the downloadable application, I thought I’d bring them to your attention.
Error: "Not Found" (404) at link https://processing.org/reference/DoubleDict.html (from https://processing.org/reference/)
Error: "Not Found" (404) at link https://processing.org/reference/DoubleList.html (from https://processing.org/reference/)
Error: "Not Found" (404) at link https://processing.org/reference/LongDict.html (from https://processing.org/reference/)
Error: "Not Found" (404) at link https://processing.org/reference/LongList.html (from https://processing.org/reference/)
Error: "Not Found" (404) at link https://processing.org/images/processing-site.png (from https://processing.org/css/style.css)
Error: "Not Found" (404) at link https://processing.org/reference/libraries/sgeiger@shenkar.ac.il (from https://processing.org/reference/libraries/)
Error: "Not Found" (404) at link https://processing.org/reference/libraries/www.pierdr.com (from https://processing.org/reference/libraries/)
Error: "Not Found" (404) at link https://processing.org/reference/add.html (from https://processing.org/reference/multiply.html)
Error: "Not Found" (404) at link https://processing.org/reference/libraries/sound/libraries/sound/SoundFile.html (from https://processing.org/reference/libraries/sound/AudioSample.html)
Error: "Not Found" (404) at link https://processing.org/reference/libraries/sound/libraries/sound/SoundFile_duration_.html (from https://processing.org/reference/libraries/sound/SoundFile_frames_.html)
Error: "Not Found" (404) at link https://processing.org/reference/libraries/sound/libraries/sound/AudioSample_duration_.html (from https://processing.org/reference/libraries/sound/AudioSample_frames_.html)
@kfrajer, no offense intended but frankly I don’t see the need to open a Github account for the singular purpose of reporting a documentation problem. I would have no other use for it otherwise.
@kll, I reported it again here in the public forums as the original errors haven’t been addressed in the six month period since the bug report was originally reported on Github. There are now additional documentation errors and I thought bringing this back to the attention of others more involved in Processing would be beneficial. It appears I was correct in this assumption as kfrager has indeed added a comment to the original Github entry based on my forum post.
You do not need to open a GH account if you don’t want to. You just let us know your preference and somebody in the community will engage the post, including me. The concept is that this is a open source project and the project is improved by community efforts. The proper way to track bugs is by creating a ticket or updating a ticket if you find one related, as kill did. However, although it is nice that kill found the previous ticket for you, you don’t have to go for that extra effort if you don’t want to. You are doing a lot by raising the issue using the proper tool. Notice that github has tools to manage duplicate posts. Notice Processing developers will not check post in this forum for bugs unless the post is added in the description in the github ticket.
And I agree that this issue still persists, as I confirmed it myself few days ago. This should be engaged or at least, request for the current status of the ticket. Then again, I have heard that Processing developers tackle issues on priority bases. The more people that create tickets or work on current active tickets, the more weight the ticket will receive, so it is my thought. Please keep in mind this is how open projects should work. This does not reflect how Processing handles the cases and it is dependent on internal structure and leadership. I am not related to the Processing core but I am just a fellow and user.