millerpuckette
commented
3 months ago I think this all makes sense - although perhaps how to build Pd should also be an appendix - most readers won't want to confront that at all.
And perhaps "theory of operation" should eventually be two sections, "using Pd" including editing patches, managing files, and an intro to the various kinds of objects; and another, real theory of operations that explains stuff like message passing, "$" expansions, DSP chain sorting, order of execution of messages, and all that...
cheers
Miller
On 7/4/24 9:38 PM, porres wrote:
I think Pd's manual is not well structured.
It starts with the inner workings of Pd, then it goes into installing and configuring, but configuration is still not quite complete. Then, a last chapter is about building it.
It makes sense to me that a manual starts with installation. It is also intuitive to me to add a how to build pd section after the download and install, as these are related. So we'd start with this chapter on installing/building, and then go to a chapter about opening and configuring it. And this configuration chapter could include all tabs and things that we still miss.
Then, finally, we can have the so called "theory of operation" as a final stage.
I see that installing externals can be an appendix that comes after that, followed by "current state/release notes". So, this is what it would look like
1- Introduction 2- Installing and building Pure Data 3- Configuring and running Pd 4- Theory of operation 5- Appendix I: Install Externals 6- Appendix II: Release Notes
— Reply to this email directly, view it on GitHub https://urldefense.com/v3/__https://github.com/pure-data/pddp/issues/225__;!!Mih3wA!FTA8p4NIMUHQ58dps6GDEatRpbl1QC0b_bxdsbV4x9Z0SDLoZkDc96EmwcyvCkJ2m17Uk3iWjsD10ktNhQGL$, or unsubscribe https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AARTRY2MXOU5KS2AON5SV7LZKWQFDAVCNFSM6AAAAABKMBDWG2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGM4TCMZYG4ZDMMQ__;!!Mih3wA!FTA8p4NIMUHQ58dps6GDEatRpbl1QC0b_bxdsbV4x9Z0SDLoZkDc96EmwcyvCkJ2m17Uk3iWjsD10iW3x664$. You are receiving this because you are subscribed to this thread.Message ID: @.***>
porres
I think Pd's manual is not well structured.
It starts with the inner workings of Pd, then it goes into installing and configuring, but configuration is still not quite complete. Then, a last chapter is about building it.
It makes sense to me that a manual starts with installation. It is also intuitive to me to add a how to build pd section after the download and install, as these are related. So we'd start with this chapter on installing/building, and then go to a chapter about opening and configuring it. And this configuration chapter could include all tabs and things that we still miss.
Then, finally, we can have the so called "theory of operation" as a final stage.
I see that installing externals can be an appendix that comes after that, followed by "current state/release notes". So, this is what it would look like
1- Introduction 2- Installing and building Pure Data 3- Configuring and running Pd 4- Theory of operation 5- Appendix I: Install Externals 6- Appendix II: Release Notes