Article or Demo. Which do you prefer?
As promised, here's the article explaining how to implement the dTree menu, that I talked about on Wednesday and demonstrated in this sample db.
Whether you choose to read the article or simply download the demo is, naturally, down to you. As a pair, the article and demo go hand in hand. You can't really have one without the other. The main reason to have both is that there are some people who prefer to have things explained to them. Personally, I prefer to rip apart a sample database and then resort to the explanation as a last resort. How do you guys prefer to learn?
Without the sample database the article would probably be twice as long as it would require full step-by-step instructions for every part of the forms and views. With the accompanying database I can skip the detail and cover the basics of the important features and let you lot work it all out for yourselves. Hope you enjoy....
Skip to the 
You can subscribe to an individual
Jake - for me the answer is "both". I like to see the logic behind the demo in the article and look at any gotchas which are usually mentioned in the article - that is tougher to do in code comments or on an about screen.
Normally i prefer to start with the explanations and the whole logic and then go to the application or demo. I think each one ( the explanations and the demo ) generate the 100% on the whole idea.
If I haven't got a clue I like to be led by the hand, as it were. However if I do have some clue I like to pick it apart and play with each little bit to see how it works and behaves.
I've asked this question myself... and the majority of the replies were "both". Of course! I replied - but then I got to thinking... "both" is the only logical answer.
Now, I don't want you to get a big(ger) head over this ;-), but you've got an excellent writing style. Me: I stink. Most of my articles have recently included an example of what I was talking about for this very reason.
In all seriousness Jake, there should be an example/demo reviewing the article's topic for a very simple reason: someone can go on and on about how something can be done, but it's another thing to have something staring right back at them saying "look - I'm doing it!".
Also, we're (IMHO) offering new development methodologies with these articles - not just a "look, this plugs right in" sort of approach with the development practices (or lack there of) of yesteryear. I made a comment the other day about example databases and how, while they focus on the topic at hand, they also really deliver many other "revolutionary" ideas in Domino development.
I'm babbling... let me sum it up - put the thing online if you've got the time and cycles. Remember, we're not exactly paying you for this... but you might as well do *something* with the database that you used while writing your article!
Usually, I'll do a quick skim through the explanation, then rip apart the application myself. If I get confused about any part of the app, I'll go back to the article in more depth to look for an answer.
Jake,
As Chris said, your writting style is really excellent. I have benefited the most from your articles by first downloading the sample db and have it opened in the notes client/designer. Then read the article and as you talk about each piece, go through the design and see what you mean.
Thanks for the wonderful job!!
Well, both, of course.