"just to make sure that my message isn’t misunderstood: I am not blaming Igor for not having written a book about NativeBoost (yet), and I am very thankful that he wrote NativeBoost in the first place. I know how hard it is to maintain a piece of software over an extended period of time. You have to work on a full-time job, earn money, have some remainders of a life etc. It’s sometimes easier for academics as they may have some more freedom what they work on (but not necessarily so). If Chris Uppal had not written the excellent documentation of JNIPort for Dolphin before I took over maintenance, the JNIPort documentation would be in the same state as the NativeBoost docs. I simply don’t have enough spare time for it. "
good but I was not replying to you, I was replying to Stephan. "Excellent, thanks in advance! I can help in proof reading, but don’t expect too much - see above." I never expect anything from anyone, even when I complain about it ;). I am already porting PBE to Pharo 3 and doing video tutorials on Pharo 3 so my hands are full too. "If it were so easy… To write NativeBoost docs, you have to understand what you are writing about in the first place, and you have to have a plan - chapter structure, consistent examples, ideally everything explained in the context of a typical problem. The current tutorial in already very good in this respect. But that’s hard and takes time, and it can’t be split up easily among more than three people - which accidentally seems to be the approximate number of knowledgeable NativeBoost experts on this planet who actually could actually do it." yeah its not that easy, that's true, its easier, write a line a day, Your philosophy about well structured documentation is of course ideal but this comes down to Well Structure but little documentation vs loads but messy documentation. Which in that case I pick the second option with my eyes closed. Which you think most people will pick ? Plus most documentation is very messy anyway. I am a lawyer as professional and I deal with messy documentation from day to day basis, its not that I don't hate i, I do, but the alternative of no documentation is simply not an option to me. And if you think about it messy documentation still beats google search hands down. So never underestimate the immense value of messy documentation. The idea that Nativeboost itself is a tricky subject, well sure you need to understand how C works and be able to tolerate all the manual management mess, but I can't say beyond that is that hard. I suspect however that the problem is that not that many people use Nativeboost in the first place. On Fri, May 30, 2014 at 12:40 PM, Joachim Geidel < joachim.gei...@onlinehome.de> wrote: > Hi all, > > Am 30.05.2014 um 10:30 schrieb kilon alios <kilon.al...@gmail.com>: > > he has not provided documentation for Nativeboost that's true, but he > never left a question unanswered either ;) > > > just to make sure that my message isn’t misunderstood: I am not blaming > Igor for not having written a book about NativeBoost (yet), and I am very > thankful that he wrote NativeBoost in the first place. I know how hard it > is to maintain a piece of software over an extended period of time. You > have to work on a full-time job, earn money, have some remainders of a life > etc. It’s sometimes easier for academics as they may have some more freedom > what they work on (but not necessarily so). If Chris Uppal had not written > the excellent documentation of JNIPort for Dolphin before I took over > maintenance, the JNIPort documentation would be in the same state as the > NativeBoost docs. I simply don’t have enough spare time for it. > > > I think I will come around eventually to adding documentation to > Nativeboost. > > > Excellent, thanks in advance! I can help in proof reading, but don’t > expect too much - see above. > > Imagine every Pharoer adding 10 lines of documentation every day. Say 100 > people . That's 33 pages per day , 12167 pages per year. Thats 30 books of > the size of PBE per year. An insane amount of documentation. > > > If it were so easy… To write NativeBoost docs, you have to understand what > you are writing about in the first place, and you have to have a plan - > chapter structure, consistent examples, ideally everything explained in the > context of a typical problem. The current tutorial in already very good in > this respect. But that’s hard and takes time, and it can’t be split up > easily among more than three people - which accidentally seems to be the > approximate number of knowledgeable NativeBoost experts on this planet who > actually could actually do it. > > On Fri, May 30, 2014 at 10:57 AM, stepharo <steph...@free.fr> wrote: > >> Hi joachim >> >> could you spend some time and helping us to write a documentation on >> nativeboost? >> Else it will always stay the same. I cannot systematically try to write >> documentation on things I do not have expertise >> because it is killing me. >> > > Same for me, I am just a NativeBoost amateur, and unfortunately my time > budget is severely limited. I would prefer spending my time on enhancing > JNIPort (callbacks are currently too complicated). But I can help in > proofreading. > > Joachim > >
