perhaps even WebOnSwing and POJO
>> Application Server come to mind.
>>
>> Cheers,
>> Erik
>>
>>
>> On Mon, Aug 3, 2009 at 1:33 AM, shetc wrote:
>>>
>>> I guess the name LazyBoy says
Ok, sorry, you guys have always been very helpful to me. Maybe we can
together with Barak and down a few beers :blush:
--
View this message in context:
http://www.nabble.com/Wicket-for-non-Web-AJAX-developers--tp24780111p24783661.html
Sent from the Wicket - User mailing list archive at
Cheers,
> Erik
>
>
> On Mon, Aug 3, 2009 at 1:33 AM, shetc wrote:
>>
>> I guess the name LazyBoy says it all.
>> --
>> View this message in context:
>> http://www.nabble.com/Wicket-for-non-Web-
g and POJO
Application Server come to mind.
Cheers,
Erik
On Mon, Aug 3, 2009 at 1:33 AM, shetc wrote:
>
> I guess the name LazyBoy says it all.
> --
> View this message in context:
> http://www.nabble.com/Wicket-for-non-Web-AJAX-developers--tp24780111p24783233.html
> Sent fr
I guess the name LazyBoy says it all.
--
View this message in context:
http://www.nabble.com/Wicket-for-non-Web-AJAX-developers--tp24780111p24783233.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To
On Sun, Aug 2, 2009 at 2:46 PM, Troy Cauble wrote:
> On Sun, Aug 2, 2009 at 4:46 PM, Igor Vaynberg wrote:
>
>> On Sun, Aug 2, 2009 at 10:40 AM, Troy Cauble wrote:
>> > Much of the class design & documentation assume knowledge of
>> > these things, especially when you get down to stuff like
>> > Aja
get the idea behind. And
it's less than 400 pages :-)
cheers,
Marcin
--
View this message in context:
http://www.nabble.com/Wicket-for-non-Web-AJAX-developers--tp24780111p24782743.html
Sent from the Wicket - User mail
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
On Sun, Aug 2, 2009 at 4:46 PM, Igor Vaynberg wrote:
> On Sun, Aug 2, 2009 at 10:40 AM, Troy Cauble 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 tha
; documentation assume knowledge of
> these things, especially when you get down to stuff like
> AjaxFormComponentUpdatingBehavior. WTF?
>
--
View this message in context:
http://www.nabble.com/Wicket-for-non-Web-AJAX-developers--tp24780111p24782326.html
Sent from the Wick
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.
-
On Sun, Aug 2, 2009 at 10:40 AM, Troy Cauble 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 t
> 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.
Duh... there is/was a bug on BUTTON at least on firefox (might have
affected only non-ajax buttons). You cannot distinguish which button
was pressed. So it is safer to use LINk
Are there any resources for Wicket that a non web or ajax developer
should be aware of?
Much of the class design & documentation assume knowledge of
these things, especially when you get down to stuff like
AjaxFormComponentUpdatingBehavior. WTF?
I know that this was a design choice and you can't
14 matches
Mail list logo
