I haven't seen any 'special' article of the kind you are looking for. However, I can just say for myself that when I started working with Wicket, all I new was basic HTML. I didn't even know exactly what was CSS. Slowly I became better in that area. Everyday I learned something new about webdev (as yo call it). I even 'stole' many example code. yes i did :) Which I believe is a very good way to learn. I can also tell you that I do feel sometimes the gap of not knowing really good JS and Ajax. For these special occasions we take an outside consultant. I usually look behind his shoulder and learn. or just read the svn difference when I update my project.
What I suggest is, read the Wicket wiki, google, check this user list and ask questions (I once asked how to write the JS for closing a window. And was answered really quick.), check the example and if you can, have a phone number of an ajax / js expert for the REALLY complex stuff. Eyal Golan egola...@gmail.com Visit: http://jvdrums.sourceforge.net/ LinkedIn: http://www.linkedin.com/in/egolan74 P Save a tree. Please don't print this e-mail unless it's really necessary On Sun, Aug 2, 2009 at 11:46 PM, Troy Cauble <troycau...@gmail.com> wrote: > On Sun, Aug 2, 2009 at 4:46 PM, Igor Vaynberg <igor.vaynb...@gmail.com > >wrote: > > > On Sun, Aug 2, 2009 at 10:40 AM, Troy Cauble<troycau...@gmail.com> > wrote: > > > Much of the class design & documentation assume knowledge of > > > these things, especially when you get down to stuff like > > > AjaxFormComponentUpdatingBehavior. WTF? > > > > what part of that name or javadoc is hard for you to understand? > > > I'm saying it's hard for someone without a prior web development > background. > > The javadoc says "A behavior that updates ... via ajax....", but I only > have > a > vague idea why or when I might need to do that. Also it takes a javascript > event string argument that is not explained. (I can google "javascript > events" > and guess or I can steal from example code.) > > Even more to the point, AttributeModifier require you to write javascript > and know the > likely form of what your modifying. Without googling examples of > confirmation > dialogs, I could have never guessed that "AttributeModifier" was the > relevant > class for that. > > This is not a criticism of Wicket or the docs. I know the target user is > someone > who's done traditional webdev first and came looking for something better. > > I was just curious if there happened to be any articles that filled in the > gaps > for those of us attempting to skip directly to Wicket. > > Thanks, > -troy >
