I am quite interested in participating in writing documentation for Non
in the future.
Also, Markku's problem with the name being a bit too generic is quite
real and serious. I wouldn't say it's extremely important to change it
but if it will be changed it should be done as soon as possible.
On sun, feb 15, 2015 at 3:03 EH, Nicolò Balzarotti
<[email protected]> wrote:
I'd agree with you when you say that more detailed/updated manuals
would be useful. And I tought thas (as for qtractor) we all could
contribute writing a handy pdf. However, I think that non shoud
become more stable before this to happen.
About the name "non", yeah it's a bit tricky, but if you search for
("non timeline"|"non daw") etc works quite well.
2015-02-15 15:41 GMT+01:00 Markku Tavasti <[email protected]>:
On 02/14/2015 12:58 PM, [email protected] wrote:
The learning curve was steep at first - a lot of stuff isn't
documented in
the manual, but can usually be worked out from the menus (and if
not there
are a lot of informative posts in the mail list archive).
Yes, I agree steep learning curve. Examples on workflow/use cases,
in manuals or maybe youtube video would be helpfull.
And like I said in IRC, name is bit problematic. When trying to find
some help with google, 'non' is pretty common word, and getting lots
of hits from everything else than Non :-(
--
M. Tavasti / [email protected] / +358-40-5078254
