🚀 go-pugleaf

I've been thinking about the latest discussions of MacApp bugs, fixes, unfixes,
etc. Jeff's suggestion of collecting these in FrameWorks seems a good idea, but
I wonder if we can go one better.
 
If we devise a standard format for such items, MADA could collect them
electronically and publish them as Jeff suggested on the code disk. In additon
to the bug fixes, I would suggest that workarounds and tips be included. Anyone
could submit them, and MADA would have no responsibility other than collating
and publishing them. This seems like an application that really is appropriate
for HyperCard.
 
MADA could prepare an empty HyperCard stack which anyone can download and then
use for creating bug/tip reports. The fields should be:
    short description (e.g., Cells incorrectly broken in page breaks in
TGridView)
    MacApp method(s), object(s) affected
    lengthy description
    workaround/fix
    submitter's name, E-address, date
    keywords for searching
    MacApp version this is relevant to
 
This is what most people already put in an AppleLink message, and shouldn't
take much time to enter. MADA would explicitly not correct or edit this data.
There will be misspellings (although we'd hope that the names of the MacApp
methods would not be mangled), duplications, and contradictions. There will
even be some errors. Although I'm not a big fan of Hypercard, in a situation
like this it seems that the simple searching capabilities would work well, and
allow the ultimate user to poke around looking for alternate solutions and
workarounds for problems. No XCMDs, no fancy scripts, no nothing should be
added. By keeping it very simple for contributor, browser and MADA, it might
actually work.
 
Whatever mechanism MADA has to put together to do this (and it shouldn't be
much effort) could be reused for other platforms that come along in the future.
 
Jesse