On Sat, 5 Jun 2010, Dan Wilcox wrote:
Fair enough. My point was more that the writers should not forget who
their intended audience is and should choose ease of writing over
readability. The easiest solution from a writer standpoint could be that
readers should refer to help in the source
I've come to think of the default as being no collaboration at all
i knew that and i'd rather this way :
http://dontevenreply.com
you're should be proud of your work in this 'community' hey?
to destroy it for your own very narrow minded purposes?
sevy
Le samedi 05 juin 2010 à 23:02 +0200, Dan Wilcox a écrit :
Here's my try for this case:
* problem: the help system is not consistent or effective in how
information is formatted and displayed
* possible requirements:
* help files as patches (more
It's nice to see the Pd community can agree upon such basic conventions.
On Jun 4, 2010, at 9:07 PM, Mathieu Bouchard wrote:
On Fri, 4 Jun 2010, Hans-Christoph Steiner wrote:
On Jun 4, 2010, at 2:50 PM, Mathieu Bouchard wrote:
Patches can also introduce bugs.
Right. Such as the first
On Sat, 5 Jun 2010, Dan Wilcox wrote:
It's nice to see the Pd community can agree upon such basic conventions.
what are you trying to say ?
_ _ __ ___ _ _ _ ...
| Mathieu Bouchard, Montréal, Québec. téléphone:
On Jun 5, 2010, at 6:54 PM, Mathieu Bouchard wrote:
On Sat, 5 Jun 2010, Dan Wilcox wrote:
Nothing personal ... just that I'm annoyed that these are even issues.
Then what can you say to help us ?
Use the tracker. That's what it's there for. Keeping changes to core
functionality only in
On Sat, 5 Jun 2010, Dan Wilcox wrote:
Use the tracker. That's what it's there for.
Alright.
Keeping changes to core functionality only in SVN logs works for
projects with a small group of contributors who are mainly developers.
When it comes to the pd/src folder, Pd is a project with a
I like the fact that you're not afraid to ask these questions and don't gloss
over the details. I have actually been spending some weeks at work looking into
these kinds of issues in how we as a creative community (at work) share
information and collaborate.
On Jun 5, 2010, at 9:29 PM,
