I've followed the pdpedia threads but perhaps not closely enough. I've always thought Pd lent itself well to documentation and self-exploration because of the interactive help patches. A wiki approach does not offer this. On the other hand it does offer an easy way to grow docs through collaborative editing, plus there's search capabilities for newbies to find what they want etc.
Any ideas about how these two things might be combined? Perhaps pddp already examined this?
-John
On Thu, Apr 2, 2009 at 10:51 AM, Alexandre Porres porres@gmail.com wrote:
yeah, well, I dont really have a clue on what is missing too, please check then, and we will start with the most needed.
cheers
On Thu, Apr 2, 2009 at 12:24 PM, Philip Potter philip.g.potter@gmail.comwrote:
2009/4/1 Alexandre Porres porres@gmail.com:
does this mean that you want to make a reference manual of Every
Object,
no matter whether it has been implemented or not?
well, we could skip the not implemented ones for now :)
I think in the interests of starting somewhere, and with the basics, I'm going to go through the pd help files in order and make sure everything there is covered by pdpedia. We can do more advanced stuff when pdpedia is a bit more developed, but for the moment, there isn't even an article on "message", so I'll go and write that.
but what keeps us from doing this right now? what has kept us from
doing
so in the past few years of pdpedia's existance? what shall we do to avoid becoming a honeypot?
hmm, sorry for not having followed the pdpedia since it has started, so
I
dont know actually about its history and everything. I just wish to collaborate, so please fill me in. what is honeypot? something not good I guess.
A honeypot is something attractive to spammers and hackers.
Philip
-- Alexandre Torres Porres cel. (11)8179-6226 Website: http://porres.googlepages.com/home http://www.myspace.com/alexandretorresporres
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list