hi, i am preparing a wicket architecture document for a project and i need a preliminary diagram asap. what is the result, is the diagram presented here by Subbu already corrected (ended) and presented somewhere? it's very important for this document. thanks
jWeekend wrote: > > Jeremy, > > Yes, if you believe showing "model" on such a high level architectural > diagram meant to depict how the major components hang together, then you > should show IModel instead of LDM for sure. And it's true that newcomers > need to understand models and can find this concept hard to grasp if they > have not seen this sort of pattern before, but you don't need to show > everything in the one diagram. > > Another comment about the diagram(s) I feel would be most useful (ones I > would have benefited from when I first luckily stumbled upon Wicket) is > that there should be a clear distinction between static and dynamic > features of the framework, for consistency and to avoid confusion for the > reader. > > I think this is a good start and you can also see some of the Wiki entries > syl put on the Wiki even before he was working with us, like > http://cwiki.apache.org/WICKET/request-cycle-and-request-cycle-processor.html > this one . > > Regards - Cemal > http://jWeekend.com jWeekend > > > > > > Jeremy Thomerson-5 wrote: >> >> While I agree that you could take out LDM specifically, I really think >> that >> you should replace it with IModel - I think it is critical to show that >> IModel is the abstraction between a component and where it gets it's >> data. >> This is the number one misundertstood thing that I find among those I >> teach. >> >> -- >> Jeremy Thomerson >> http://www.wickettraining.com >> >> >> >> On Thu, Mar 26, 2009 at 6:44 AM, jWeekend >> <[email protected]>wrote: >> >>> >>> Subbu, >>> >>> Thank you! >>> I have a quick minute now, so I thought you'd appreciate a few crumbs of >>> feedback before I can take a better look, hopefully late this evening. >>> >>> 0 - this is a great start! >>> 1 - take out the LDM - this stretches the scope of the diagram beyond >>> what >>> it needs to show. >>> 2 - if the level of abstraction is at a level which includes >>> validators/converters etc (possibly form processing is better elaborated >>> in >>> a child diagram) ... I think we need to mention FormComponent >>> explicitly. >>> >>> More soon, and I hope this will draw some comments from core devs and >>> application developers. >>> >>> Regards - Cemal >>> http://jWeekend.com jWeekend >>> >>> >>> >>> subbu_tce wrote: >>> > >>> > Based on my understanding, i just prepared a diagram. >>> > Wicket Contributors.. Please review and let me know your valuable >>> > feedback. >>> > http://www.nabble.com/file/p22717793/wicket%2Barchitecture.jpg >>> > >>> > >>> > Thanks, >>> > Subbu. >>> > >>> > >>> > jWeekend wrote: >>> >> >>> >> Jeremy, >>> >> >>> >> It's one of the first things I looked for when I first stumbled upon >>> >> Wicket 2 years ago, and it is a common request from many architects >>> and >>> >> even some project managers evaluating Wicket. >>> >> >>> >> If the core devs come up with some rough (but correct) sketch they're >>> all >>> >> agreed on, even if it's just a first iteration, I'll get someone here >>> to >>> >> create a professional (maybe even glossy) version from that. >>> >> >>> >> Regards - Cemal >>> >> http://jWeekend.com jWeekend >>> >> >>> >> >>> >> Jeremy Thomerson-5 wrote: >>> >>> >>> >>> Has anyone done a nice Wicket architecture diagram? I know about >>> the >>> >>> architecture chapter in WiA, but someone I know is looking for >>> something >>> >>> more along the lines of: >>> >>> >>> >>> >>> http://www.icesoft.com/developer_guides/icefaces/htmlguide/devguide/sys_architecture.html >>> >>> http://www.ociweb.com/jnb/jsfArchitecture.jpg >>> >>> >>> >>> Unfortunately, I'm no artist - so I can't help him much. I was >>> hoping >>> >>> someone had already done something similar as part of a presentation >>> >>> somewhere. >>> >>> >>> >>> -- >>> >>> Jeremy Thomerson >>> >>> http://www.wickettraining.com >>> >>> >>> >>> >>> >> >>> >> >>> > >>> > >>> >>> -- >>> View this message in context: >>> http://www.nabble.com/Wicket-architecture-diagram--tp22683704p22720354.html >>> Sent from the Wicket - User mailing list archive at Nabble.com. >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> > > -- View this message in context: http://www.nabble.com/Wicket-architecture-diagram--tp22683704p23572347.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
