marius schebella wrote:
I think the whole help browser stuff is very messy. there is "1.manual" versus "manuals" "media" vs "sound" and "7.stuff" versus "examples" some of the stuff is pd patches, some are textfiles, some are html docs.
that is interesting, i just have: 1.manual 2.control.examples 3.audio.examples 4.data.structures 5.reference 6.externs 7.stuff sound
which is not that badly organized :-)
I think all html or text manuals should be in a separate section of the help menu, not in the browser (in pd-extended there already is a html menu-entry) 2.-4.and 6.(although, I am not sure about 6.) should be in a tutorials submenu. 5. reference should be called "help-patches"
what makes "help-patch" better than "reference"?
most of pd's help patches are really "references", especially if you browse it via the menu (a help-patch is the thing you open via right mouseclick; a reference is the thing you browse)
sound should be a part of media. then you get HELP: --- HTML --- --- Pd --- --- Gem --- --- (other manuals) --- BROWSER --- --- Tutorials --- --- --- (control examples) --- --- --- (audio examples) --- --- --- (data structures) --- --- --- (external tutorials??) --- --- Examples --- --- --- soundfile tools --- --- --- synths ... --- --- --- (tidied up content of 7.stuff) --- --- --- (tidied up content of examples) --- --- Help Patches --- --- Media --- --- --- images and video --- --- --- sounds --- --- --- obj., mtl. ...
for me (if i understand your proposal correctly), this only makes sense if objects would be grouped by function rather than by library. this seems to have been unfeasible to do in the last year.
i think we should take practice into account.
fmgas.dr IOhannes