--- Ted Husted <[EMAIL PROTECTED]> wrote: > So first, we covered the "user" material and then we > covered the "developer" material, without creating > two content streams.
FWIW, I think two completely separate content streams is definitely a Bad Thing. I'd rather see a tutorial with sidebars containing more detailed information, links to more detailed information, or both. One thing that would help "clean up" the wiki guides is to format it more like a book: sidebars really work and are much less disruptive than a browser-width highlighted section. I don't know if that's possible with Confluence, but it sure could be handy. Another nice thing would be to have links to both wiki Guide sections and even JavaDocs throughout the pages (particularly the tutorial-level pages) for all the elements discussed on the page: configurations, annotations, classes, related tasks, etc. > Users do need to know that the framework is > extensible, even if they don't want to extend it > today. Figuring out where and *why* to extend things is critical... In S2 one great place to add functionality is in the interceptors, even if it's just configuring an existing one. The note on the wiki that says you probably won't need to do that is somewhat misleading, IMO. For example, yesterday I wanted a trivial way to add behavior to arbitrary methods on a per-Action basis without changing any Action code. So I wrote an interceptor that took as parameters "methodName: monitor1,monitor2" etc. That was great and worked until I discovered such an interceptor already existed, it just wasn't listed on the interceptor Guide page (MethodFilterInterceptor). Much lighter-weight than Spring AOP, and perfect for what I needed. For all I know there's a still-better way to implement it (wouldn't surprise me). Highlighting trivial extensibility goes a *long* way towards users a) not asking dorky questions (like me :) and b) really understanding the simplicity of the framework and utilizing its extensibility and cleanliness--my Action code is like 15 lines long but I can bolt on non-invasive functionality by writing a simple class and adding it to the list of "extra crap to do" items. My time is pretty limited these days, but I'm happy to help clean up, expand, notate, whatever the documentation (best way to learn!) as much as I can (and I even write real good sometimes :D and if I am pointed at something specific will take the time to do it up all purty-like. Dave ____________________________________________________________________________________ Finding fabulous fares is fun. Let Yahoo! FareChase search your favorite travel sites to find flight and hotel bargains. http://farechase.yahoo.com/promo-generic-14795097 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
