ps, you might want to look into wingS or echo frameworks. i think their level of abstraction is higher and might be what you are looking for. of course, the higher the level of abstraction the less control you have over the final product, keep that in mind and find a good balance for your needs.
-igor On Sun, Aug 2, 2009 at 1: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 know that this was a design choice and you can't teach everybody >> everything. I'm just asking if this info exists somewhere. > > not really sure. > >> And OTOH, Wicket is trying to hide the web model. > > totally and completely wrong. wicket abstracts away the nastiest part > of writng webapps - the stateless nature of http, not the fact that > you are writing a web app. > >> For example, given that I can make a Link look like a button, when >> should I use a Link vs a Button? I have no idea. > > it solely depends on your UI requirements (what markup you want to > use). we make it easy to work with either an anchor tag or a > button/input type=submit tag. > > -igor > >> >> Thanks, >> -troy >> > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
