[L2Ork-dev] Suggestions for PurrD GSoC 2018
João Pais
jmmmpais at gmail.com
Mon Mar 12 14:44:25 EDT 2018
> Thanks for the suggestions, João.
>
> > Data structures:
> > Implement new high-level objects to deal with elements: the current
> objects
> > are too basic, and programming is slow and repetitive, or impossible
> without
> > a gui (e.g. deleting scalars). Would it be possible to integrate the code
> > with Pd Vanilla afterwards?
>
> I'm not sure what you mean by "high-level" here. Could you explain a little
> more?
>
Since the objects are really basic, it's always necessary to start from
scratch to handle any data structures. I can later give a more complete
list of features (made one already years ago and sent it to Miller), but I
meant something that avoids repetitive tasks. E.g. "next 3" to jump to jump
3 scalars, or "index 10" to go to the 10th element, ... things like that,
that have to be programmed each time.
But regarding data structures in general, it would make more sense if these
could also go into Pd-Van (and with that libpd, etc.) - if not, then it's
better to just do some abstractions.
>
> >
> > Html5
> > If Pd is already html, would it be possible to have Purrd running
> > automatically in the background of a html5 page on a website? At a first
> > stage without gui, but afterwards with it?
>
> There's already a project idea for this: "API for HTML5 Web Apps"
>
> >
> > Dynamic object list "page"
> > An updated object list doesn't exist in Pd. Since many (all?) objects in
> > PurrD have documentation patches, it should be possible to create a
> dynamic
> > object reference page with columns such as name, library, explanation,
> > author, ... An example is at
> > http://puredata.info/Members/jmmmp/0.INTRO-100105.xls/at_download/file
>
> Are you talking about a patch here?
>
Could be a patch, but maybe easier would be a local html page which adapts
to any elements added to the extra folder, or even to Purr-D's path (would
also be easier to search). All that meta information in the libraries is
just sitting and not being used.
(again, would be good to be Pd-van compatible)
Regarding searching, I'm not aware of the latest state, but a couple more
details:
- seach window says how many elements were found ("x of y"). Maybe this was
in already.
- (also from max) when a variable is used in send/receive, clicking on that
object opens up the subpatch where the matching send/receive is. Fast to
find, and avoids repeating variables. Also for send~/receive~ +
throw~/catch~
>
> >
> > In/Out audio mappings
> > Another interesting feature in Max is a general in/out audio matrix that
> can
> > be changed on demand. This would allow to use different main
> inlets/outlets
> > without having to edit the patch.
>
> Sounds interesting.
>
> >
> > GenPd
> > With Gen, Max offers a possibility to develop DSP code in a dataflow
> > environment. Is something like that possible in Pd?
>
> This is something more low-level than expr~/fexpr~?
>
Not sure, because as I understood it, gen patches work on a block of size
1. So it's like writing C code. The number of classes is much smaller, of
course.
https://docs.cycling74.com/max7/vignettes/gen_overview
>
>
> > The only programming language I can program is Pd, so I can only offer
> > something related to that: testing patches, preparing documentation,
> > preparing examples, ... Also depending on the available time, of course.
>
> That would be extremely helpful.
>
> >
> > More ideas might come, but I wanted to leave something just from the top
> of
> > my head.
>
> Thanks!
>
If I get to do something more in Purr-d I could get more ideas to ask (I'm
trying to prepare some materials for the LAC, so it would be a chance for
it). But I have some issues, that either purr-d doesn't work on my desktop
(it just doesn't start), or some things I need don't work as good as in
pd-ext (data structures). If the workshops I'm proposing work out, I can
try to push them to purr-d
Joao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://disis.music.vt.edu/pipermail/l2ork-dev/attachments/20180312/5595f848/attachment.html>
More information about the L2Ork-dev
mailing list