overview

[equilet]

Some history:

Campion: "we need to find a solution for our depot web pages in terms of what is actually now in the depot. Right now, we don’t include on that page he mu29 or other tutorials which are really key components of the package. Can we find a way to post what is in these folders with the script method? I think it needs to be organized in some way that makes sense. Further, I still like the “overview” patch in Depot. I would like to see that maintained, upgraded. I wonder what you think at this point and if I should try and hire a grad student to do this."

Lubow:

"I think a php/python-based solution is the way to go here. We can interrogate the folders on disk, then utilize a script to upload the generated html content and link to that content in the body of a drupal node (with a php include()). This would be way better than what we have currently, which is both out of date and a hassle to rerun. The php portion is already done, and I could work on adding information for the depot pieces to allow for publishing to an overview.

The way that odot does this is that every object contains a ‘doc’ message that spits out some helper information about the object’s functionality and status in a summarized format. I’d like to adopt this model, but do it in the help patches so that if you want to leave that out of the process for patching you can. I feel that this would be more desirable for the larger world of Max users."

Lubow: "finish bringing the new tools of RV into the MMJD world, then have RV approve"

[adrianfreed]

I don't like some aspects of the "doc" message and it may be dropped from odot.

I don't expect the CNMAT server will be available to run python and php scripts of the sort you have built very much longer. Without a staff to support those scripts or a platform to run them it would seem wise to find an alternative method.

[equilet]

Scripts can run locally on a machine, and they'll be as simple to employ as a new commit to the repository. I will most likely provide instructions on how to run it locally if people would like new files to be included. Aside from the history (mentioned in the first comment), we have since moved on to ditching the doc message, and I'm working on clearly separating the content in the way that the overview is built.

[equilet]

@EdmundCampion - Please enumerate the high priority patches in which a badge/banner is needed. I hope to cover all patches ASAP, but obviously that will take a little time.

[EdmundCampion]

patches that need banner in order to appear in MMJD overview include:

APPLICATIONS * audition and decide * probability pitch * add my name to SoundCheck patch * sfinterp

EXTRAS * _Music29_Lab_tools.maxpat

PATCHERS

• (TBD)

[EdmundCampion]

PATCHERS Sampler_guide.maxpat

[equilet]

report_filepath.js patcher_locked.js

[equilet]

sampler area needs some major cleanup

[equilet]

@EdmundCampion - check out the current overview. This represents a large overhaul of the PHP scanner and some manipulation of the directory structure. Moving forward, we may want to move help files into a /help dir to conform to C74 package guidelines, but keep in mind that help files work either way.

[equilet]

Spectral Tutorials mz.toys overview