Hi,

My subject sums up my question. I'm about to create a new web system and it
will be accessed by clients using normal web browsers and mobile devices.
The normal browsers have varying screen resolutions with the lowest still at
800x600. When it comes to the mobile devices and their web browsers the
screen resolutions may be even smaller.

I suspect that serving different CSS files for different screen resolutions
will only get us part of the way. In the case of the mobile devices there
might also be a need to reduce the amount of markup that is being sent as
well as restructure it a bit.

I'm interested in hearing if you have dealt with similar requirements and
how you solved them?

And more specifically I'm interested in how I would go about solving this
using Wicket in a nice and structured manner?

Best regards, Kent

Reply via email to