- #LMMS MUSIC MAKER PDF HOW TO#
- #LMMS MUSIC MAKER PDF PDF#
- #LMMS MUSIC MAKER PDF INSTALL#
- #LMMS MUSIC MAKER PDF MANUAL#
#LMMS MUSIC MAKER PDF PDF#
Have menu items open to anchor points in the PDF.
#LMMS MUSIC MAKER PDF INSTALL#
Have the PDF accessible locally with install by default.on a train, cruise, plane) and these are the times when people may need access to documentation the most. This is because music is often done offline (e.g. I feel as a project we should still ship with documentation. MacPass just directs to a GitHub project page, not useful at all 🤣. Google's appears to be offline wherease Slack's appears to be online. Oddly, testing Google Chrome, MacPass and Slack, all "Help Centers" open in a browse window. I'm sure we could write a converter to do this but I'm not sure it's cross-platform. Previously, the standard way to offer help historically through Windows was to add a dedicated, searchable help window. I'm sure this is hard to do for all readers, but would allow use to somewhat integrate and avoid redundancies. What'd be nice is if we could add a " more info" link which jumps to an anchor point in a PDF. One way I've seen this done is with an option in the installer, but if that's not possible maybe we could modify the download page? (quick inspect element I don't think we need a separate downloads for docs, no need to modify the downloads page, we should simply include the docs, always. I definitely think we should continue to offer a docs-less download for those with poor internet, but at the same time it's good if we offer one with docs to make people aware of the possibility. I think it'd be ideal if merged features had documentation on GitBook even if they aren't in a release yet, so perhaps there can be a special section or separate book(?) for that? PR descriptions + discussion do a reasonably good job of documenting unmerged features, I think? I don't think we really "handle" this right now either, so changes going forward aren't likely to make things worse. " applies to the entire song editor timeline area and is super long. "Click an empty space to add a clip, double click to edit a clip, middle click to delete a clip, click and drag to move a clip, ctrl + drag to clone a clip. "Time taken for note to reach full volume" is short and relates specifically to the attack knob of the envelopes tab. I think shorter and more location-specific documentation is suited for hover text, everything else makes more sense on GitBook (probably with some overlap). I like the idea of making GitBook downloadable, but in combination with some in-software docs (as evidenced by me opening #5571).
Display hover-sensitive info in top right corner of toolbar #5571 - Display hover-sensitive info in top right corner of toolbarĬontinued from #5570 as per suggestion.Once we decide where everything belongs, what should be done with existing documentation that belongs somewhere else?.How should documentation be handled for changes that are as-yet unreleased or unstable?.Where should new documentation go - in the software itself, as with Xpressive, or on the website?.The following questions probably deserve answers: Making the GitBook documentation available for separate download.Bundling the GitBook documentation with the main software download.Providing built-in help within the software.It would be useful for users to be able to access help offline.
#LMMS MUSIC MAKER PDF MANUAL#
#LMMS MUSIC MAKER PDF HOW TO#
This issue is to discuss where documentation and help should be kept, and how to make it available to users.
0 kommentar(er)
