Hi Adam,
My thoughts:
- As HC mentioned, PDP is in Pd Extended already, although it doesn't
always run out of the box on OSX 2) Complete install instructions should include how to get it running on OSX (X11 must be installed, maybe some other things) 3) PiDiP could be more complicated, as it requires specific versions of Quicktime and perhaps some other libs, IIRC. Someone would need to check its dependencies on OSX before writing the install guide. And because this seems to change often, that person would need to stay on top of changes which would affect PiDiP's usability. I don't know if this has been taken account of in Pd-Extended, maybe HC can answer that. 4) Even if PDP is able to run on OSX, it runs very poorly in comparison to on x86 Linux. It also runs poorly on PPC Linux, dues to its code being highly optimized for the x86 architecture. This should be mentioned in the install instructions as well. 5) We'd still need someone to write some useful tutorials. I agree at need for documentation, as the help files and docs which come with PDP are some of the most cryptic I've ever seen! PiDiP docs make sense, OTOH, but some realworld application of some of this stuff would be nice.
---->side note to HC: is X11 a prerequisite for GEM on OSX Pd Extended now? I saw some people at my last workshop had some missing libs with newer Pd Extended installers...
D.
adam hyde wrote:
hey
I can document pdp/pidip installation. it contains the packages i have used the most so happy to help if you think its within the scope of the manual Derek.
It might be however, that we should focus first on the basics. One issue that might prevent this is if we get too ambitious for this first round and make the scope of the manual too broad.
so, while i'd love to see pdp/pidip included in the first full release, i think first we should bite of a chunk we know we can finish in 3 days...the rest can be included in another sprint
thoughts?
adam
On Sat, 2009-03-28 at 01:11 -0400, Hans-Christoph Steiner wrote:
For what its worth, PDP/PiDiP has been included in Mac OS X and GNU/ Linux Pd-extended since 0.39.3, so no compilation instructions
needed. We do still need someone to write the docs. I don't think I
know enough to write more than a paragraph. Same goes with Gridflow,
in my book..hc
On Mar 27, 2009, at 8:56 PM, Derek Holzer wrote:
My thoughts exactly...document what people actually use most, in a
way which helps them to use it. As I said, if someone wants to go
through all the trouble of making a separate install guide for PDP
or Gridflow, I'd consider including it.As it stands, however, both of these can change at any moment
depending on distros and dependencies.... on top of the fact that
they only run well on Linux + x86 architecture (PDP) or cannot be
compiled at all except on Linux (Gridflow). For me to accept them
into the FLOSS manual, the installation process must be completely
and reliably documented as well. No lazy "just compile it and cry to
the mailing list if it doesn't work" instructions which leave
newbies lost. Free software is only really free when you don't have
to be a computer programmer to get it working.As it stands, I want to focus on accessibility first off. So cross- platform + Pd Extended is the baseline for the FLOSS Manual, as it
has been from the beginning.D.
Hans-Christoph Steiner wrote:
I think it makes the most sense to focus on Gem since it is the
most widespread.-- ::: derek holzer ::: http://blog.myspace.com/macumbista ::: http://www.vimeo.com/macumbista ::: ---Oblique Strategy # 30: "Change specifics to ambiguities"
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
If you are not part of the solution, you are part of the problem.
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list