--- On Tue, 6/28/11, Hans-Christoph Steiner hans@at.or.at wrote:
From: Hans-Christoph Steiner hans@at.or.at Subject: Re: [PD-dev] packaging the pddp docs To: "Jonathan Wilkes" jancsika@yahoo.com Cc: pd-dev@iem.at Date: Tuesday, June 28, 2011, 7:20 PM
On Jun 28, 2011, at 1:10 PM, Jonathan Wilkes wrote:
I'm already kind of doing that with pd-l2ork.
I've revised Miller's
control/audio/ds tutorials. Pd-l2ork has
fixed
the crasher bug when
a patch closes itself, so I've got a
navigation
toolbar in those
tutorials that is currently incompatible with
pd-extended/vanilla.
I had no idea. Ico seems to work on his
own. It
would be great to have those bug fixes submitted to the patch
tracker.
The patch tracker is what Miller, IOhannes, Martin Peach, me
and
others use for keeping track of patches that are meant to go
into
pure-data core.
He's also working off 0.42 currently, so submitting to
the
tracker would be pointless. I think someone was
working
to port the changes forward to 0.43, but Ico is
currently
on vacation and I'm not sure where they are in the
process.
I merged in a couple things from l2ork, like Joe Sarlo's Magic Glass and inlet/outlet highlighting. More patches would be great to have.
As far as I understand there are a lot of changes in Pd-l2ork to core Pd, and if you accepted them into Pd-extended it would introduce more discrepancies between vanilla and extended. If that's a possibility you'd entertain to get the some of the functionality that pd-l2ork adds, then I can help with this process.
Its not a new project. I see it as a
better
representation
of what's currently happening. You
are doing
great
work with the PDDP docs, I think we can
make the
structure
of that project work better for you.
Having
it as a
distinct entity means you are less
encumbered by
others when
making decisions about what should happen
with
PDDP.
That distinct entity can be either a
folder in the
pure-data
SVN, a separate SourceForge project, or
whatever
we think is
easiest. I think one of the first
two
options would
work well.
I'm happy to do all of the Debian
packaging, that
part
would be easy for me.
So what is it you want me to do?
To start with, choose a repository to work out
of.
Shall we just reorganize the doc/pddp folder in pure-data
SVN? Then
make that the home of your PDDP work, and I'll package it for
Debian, and
make sure the new layout works in Pd-extended.
That works. Should it be merged with the current
pddp libdir?
No, the 'pddp' lib is a standard Pd library of objects meant to support documentation. The idea of this chunk is a collection of reference and tutorials. What if, for now, we make doc/pddp/tutorials and add 2.control.examples, 3.audio.examples and 4.data.structures there. Then keep reference patches in doc/pddp for now while we figure out the best place for them.
It might make sense, for example, to keep the reference patches in the 'vanilla' libdir in externals/vanilla. That's a library of all the vanilla core objects split out into a library. But its probably not quite yet time to do this, since that library is only vaguely defined now.
.hc
If nature has made any one thing less susceptible than all others of exclusive property, it is the action of the thinking power called an idea, which an individual may exclusively possess as long as he keeps it to himself; but the moment it is divulged, it forces itself into the possession of everyone, and the receiver cannot dispossess himself of it. - Thomas Jefferson