Maybe that’s what we can all contribute. Get assigned a section of the guide and rewrite it. Submit, revise and add to the guide.
And rewrite a better built in guide viewer. One that is searchable at the very least. And doesn’t take an age to load each section. Sean Cole Pi Digital > On 21 Oct 2020, at 16:45, Pi Digital <s...@pidigital.co.uk> wrote: > > I’m going to chime in, not to discredit anyone else or their comments, only > to voice a reason I personally feel is far more needed and worthwhile. > > Before any of what has been suggested being carried out, as lovely as it all > would be, getting the dictionary and the guide usable and accurate/up-to-date > would be of greater importance. Especially for the modern and recent > modifications. But even simple stuff that has been altered in tiny ways has > not been touched in the guide for an age. > > My point is, there is no point in introducing and inviting new users to a > product that becomes difficult to use because documentation is out of date > and not matching in appearance or fiction to what is described. Sure a > community can advise those ones of workarounds and correct usage. But that’s > just pathetic and should be unnecessary. And you all know my opinions on > workarounds. > > My ethos, fix what we have, don’t introduce more problems. > > Sean Cole > Pi Digital > > >>> On 21 Oct 2020, at 14:31, David Bovill via use-livecode >>> <use-livecode@lists.runrev.com> wrote: >>> >> Does anyone have a stack that plays audio podcasts? >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
