Here's my "Hi" Firstly - kudos for the UI concept and the rather minimal working environment - excellent. My laptop and screen have a resolution of 3840x2160, and non tools look VERY TINY there, Naturally, I'm interested in patching the UI to adopt to my display size, dpi & resolution so the system looks conveniently sized. N.B. If you guys have ideas how and maybe it's part done in someone's branch/fork of the code - I'd be happy to either work on that patch AND/OR test it) pointers would be nice on where the code handling widgets sizing resides, and possibly present refactoring ideas/branches/forks to look at to achieve the above - would be nice. Didn't go through the issues, but I've noticed the FLTK itself is a fork off FLTK, so I guess the only way to understand the fork would be to eat with it :)
My availability is an expected one from fully employed deployed family man, but If I start chewing on something - I'm usually finishing it, so it's sporadic, but when my kids wake me up at nights I don't go to sleep right away. Best regards all. On Thu, Oct 1, 2015 at 10:08 AM, John Rigg <[email protected]> wrote: > I might be interested in contributing to a manual, time allowing. Non has > been my main DAW for about 18 months now. Recent fixes to some editing > bugs have allowed me to remove the "emergency backup" copies of Ardour 2 > from my DAW systems so I'm now relying completely on Non. > > John > > On Thu, Oct 01, 2015 at 12:09:34AM +0200, Nicolò Balzarotti wrote: > > Hi guys! The non suite is becoming more and more stable those days. We > > talked about writing a super cool manual some time ago. I think we could > > use something like gitbook (writing in markdown, collaborating in git; i > > created an example on my github). > > > > Can those that are interested say "Hi" so that we can organize > > ourselves? (I don't even know how many active users are there. Let's > > wake up this little community ;D ) > > > > Thanks, Nicolò > > > -- Maxim Kovgan
