I already started this in another thread, but i'll try to be more clear.
I was thinking about a script that could take a pd patch window screenshots, without have to open pd. With this, we could make automacally a pdf for example, with all graphic helps of pd externals, abstractions and native objects. I think it could help A lot with a wide vision of the actual state of development. It could be possible do this without have to hack the code ( with some bash shell command or python script for example)?
Hallo, glerm soares hat gesagt: // glerm soares wrote:
I already started this in another thread, but i'll try to be more clear.
I was thinking about a script that could take a pd patch window screenshots, without have to open pd. With this, we could make automacally a pdf for example, with all graphic helps of pd externals, abstractions and native objects. I think it could help A lot with a wide vision of the actual state of development. It could be possible do this without have to hack the code ( with some bash shell command or python script for example)?
I opened a feature request regarding this quite some time ago, it's number 1062122 or at this URL (one line): http://sourceforge.net/tracker/index.php?func=detail&aid=1062122&gro...
Here's the text:
[ 1062122 ] Let Pd print patches from command line
I would like to see a "-print" option to the pd executable which will then print the patch names following it into somehow configurable postscript files. This would have several uses: Especially it would allow users to create "screenshots" of a lot of Pd patches in a simple and fast way - like in bash:
$ for i in *.pd; do pd -print $i; done
And it would make printing patches for books or articles much easier.
Date Submitted: 2004-11-07 14:40
Ciao
I would like to see a "-print" option to the pd executable which will then print the patch names following it into somehow configurable postscript files. This would have several uses: Especially it would allow users to create "screenshots" of a lot of Pd patches in a simple and fast way - like in bash:
$ for i in *.pd; do pd -print $i; done
that's it! Wish I knew more about tk and pd graphics core... :/
seems a very useful feature...
any more clues?
cheers
glerm
On Jun 15, 2006, at 5:36 PM, glerm soares wrote:
I would like to see a "-print" option to the pd executable which will then print the patch names following it into somehow configurable postscript files. This would have several uses: Especially it would allow users to create "screenshots" of a lot of Pd patches in a simple and fast way - like in bash:
$ for i in *.pd; do pd -print $i; done
that's it! Wish I knew more about tk and pd graphics core... :/
seems a very useful feature...
any more clues?
cheers
glerm
Save some trees and use the patches interactively. You'll learn it better if you actually try the examples rather than just reading them.
just my two cents...
.hc
------------------------------------------------------------------------
If you are not part of the solution, you are part of the problem. - Eldridge Cleaver
Save some trees and use the patches interactively. You'll learn it better if you actually try the examples rather than just reading them.
Maybe. But I just feel like it's important to have some "global scope" view of the pd as a "system". I realized that pd has enough objects to be seriosly considered a "programming language"... maybe take a "panoramic" look of those patches could help to give some directions to build new aproaches of documentations and workshops. And mainly make a good choice of this "tree" to interact (because that is so many)...That's my point.
glerm.
just my two cents...
.hc
If you are not part of the solution, you are part of the problem. - Eldridge Cleaver
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Save some trees and use the patches interactively. You'll learn it better if you actually try the examples rather than just reading them.
While the patches are great, I learned as much or probably even more from reading books than from editing and playing with patches.
Ciao
On Jun 16, 2006, at 1:53 AM, Frank Barknecht wrote:
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
Save some trees and use the patches interactively. You'll learn it better if you actually try the examples rather than just reading them.
While the patches are great, I learned as much or probably even more from reading books than from editing and playing with patches.
You don't need paper to read books ;-P I like books, reading is essential. But reading images of patches designed to be used doesn't make a lot of sense to me.
.hc
------------------------------------------------------------------------
Using ReBirth is like trying to play an 808 with a long stick. - David Zicarelli
Hallo, Hans-Christoph Steiner hat gesagt: // Hans-Christoph Steiner wrote:
On Jun 16, 2006, at 1:53 AM, Frank Barknecht wrote:
While the patches are great, I learned as much or probably even more from reading books than from editing and playing with patches.
You don't need paper to read books ;-P I like books, reading is essential. But reading images of patches designed to be used doesn't make a lot of sense to me.
Well, of course one would not just use the printed patches alone, they would function as illustrations for an explaining text(book). For example Miller would have finished the illustrations for his book much faster, if he would have been able to just print a whole directory of patches with one command to ps-files to include in the LaTeX sources.
Also for articles in print magazines or on websites (like obiwannabe.co.uk) it would make things much easier to have a quick way to do several screenshots in one go. And articles make Pd popular among more people, so that's an important thing.
Ciao
But reading images of patches designed to be used doesn't make a lot of sense to me.
.hc
Well, of course it's more intuitive and interactive use the patches one by one in the computer. But just think about a way of having a faster method to take a look in all objects of a lib or even all pd objects just scrolling a home page or turning pages of a doc and making annotations, for choosing some patches to analyse in computer later, as someone that for example takes some programming language book especification, take some directions and then go code and play.
I'm sure that this make sense.
And I'm doing the screenshots this next weeks. All of then manually and generating a website with then. Hope this estimulate developers to code somethink like the pd -p (print) option and more newbies to understand what pd is. :)
cheers
glerm.
------------------------------------------------------------------------
Using ReBirth is like trying to play an 808 with a long stick. - David Zicarelli
PD-dev mailing list PD-dev@iem.at http://lists.puredata.info/listinfo/pd-dev
-
Frank Barknecht -
glerm soares -
Hans-Christoph Steiner