 |
Author |
Topic: PLEASE READ BEFORE POSTING (Read 2086 times) |
|
fry
|
PLEASE READ BEFORE POSTING
« on: Sep 23rd, 2003, 1:22am » |
|
(If you don't like to read, at least read through the bold parts)
Pardon the all-caps subject, we don't mean to shout.
Thank you for your help with Processing through your testing and reporting, we really appreciate it and couldn't get the thing off the ground without the collective input from everyone.
A few healthy tips regarding posts on this board:
check the known bugs list first
processing has plenty of them. so the known bugs for the most recent release are listed at:
http://processing.org/download/bugs.txt
this file is also included with all recent revisions of p5. it also includes notes about things that aren't actually bugs, just time-wasting headaches that come along with java/programming/working with computers/being indoors.
also check out the readme
readme.txt is included with each release of processing. it contains a lot of jibber-jabber about things, but every once in a while, the guy writing it says something useful, like how to get your serial port to work on the mac, or why something's broken.
search this bboard first
lots of bugs get reported more than once, so it might be up here already. you can even add to a previous discussion about a bug and say "yeah, this one cheeses me off!" so that we know that people are having trouble with it.
one bug per post
please post one (quantity: 1) bug per message. they may seem related, but keep em separate. as you'll notice in the release notes, it's how we keep track of bugs. it's tempting to pile on related notes about "oh, and this doesn't work either..." but i'm not smart enough to deal with more than one thing at a time.
use a subject that describes the problem
please use descriptive subject headings, they help me keep track of things:
descriptive: "single pixel lines are always red"
not descriptive: "rev 0060", or "oh no!", or "having a bad day"
this way, when others are having the same problem and searching the bboard the solution (i love those guys, see above), they'll find your helpful note about the same issue.
please no bugs by email
please post bugs here, rather than emailing us. that way lots of people can help out with your problem, and sometimes it's not actually a problem, so one of the helpful lads like ariel and toxi and the rest of the crew can have you on the road to recovery in no time.
let us know what platform/version of p5
the more details you can post, the better, because it helps us figure
out what's going on. when reporting this "bug" please include information about:
1. the revision number (i.e. 0060)
2. what operating system you're using, on what kind of hardware
3. a copy of your code: the smallest possible piece of code that will produce the error.
4. details of the error: check the last few lines from the files stdout.txt or stderr.txt from the 'lib' folder.
that's a weird one...
for stranger errors during compile time, you can also look inside the "build" folder inside "lib", which is an intermediate (translated into java) version of your code.
include the minimum amount of code
we want the minimum amount of code that will still replicate the bug. the worst that can happen is we get a report that says "problem!" along with a three page program. sure, everyone likes a puzzle, but simpler code will be a faster response.
hand over the sketch, boy
occasionally we may need you to pack up a copy of your sketchbook or something similar so that we can try and replicate the weirdness on our own machine. rest assured, we have no interest in messing with your fancy creations or stealing your ideas. the p5 team is a pair of straight-laced boys who hail from the midwestern united states who were brought up better than that. and as we often lack enough time to build our own projects, we have even less time to spend figuring out other peoples' projects to rip them off.
|
| « Last Edit: Feb 27th, 2004, 10:58pm by fry » |
|
|
|
|
|
