> I agree for the most part, except that I think an overview should at
> least mention some of the major features (e.g., declarative exception
> handling, nested page flows, declarative form field validation, etc.),
> if only to whet the appetite. It might be a sentence or two that frames
> the feature set. To me, this seems to be part of the "why should I
> care?" aspect. Another set of docs could drill deeper into the
> features, and yet another could do a technical look behind the scenes.
Heh, this actually demonstrates my own lack of knowledge about some
of the features. This would be great to weave in to, as you said,
whet their appetite. Likewise, I think a page, possibly after
the 'how do I build an app' page, to dive into these more advanced
topics would be fantastic. I just need to learn about them myself.
Something along the lines of "so, you think what you saw is cool,
just wait until you take a look at *this*, and really get your
socks blown off..."
> Just want to make clear that I think what you're doing (overview) is
> extremely valuable... so much so that if it's not present, there will be
> a large set of people who will never even try the technology.
Thanks muchly. I'm coming at beehive with virgin eyes, hadn't
touched it until I met with Eddie/Kyle/Ken a few weeks ago. So
there's definite dark corners in my knowledge of what it can do.
But writing the docs basically for a new user like myself has shown
me how impressive Beehive truly is. I was wow'd also when dan
explained some of the nitty-gritty of Control authoring to me, and
I hope to do a suitable treatment on docs about controls also.
Was telling Garrett just today that while I probably wouldn't write
a native Struts app, I look forward to really using Beehive in a
real application in the near future. You guys have done a stellar
job with it all. Now, just to convince the world of that fact. :)
-bob
