DDevelopment & Design

GWT/GXT Unable to get value of property ‘user.agent’

If your app hangs in IE/IE8 during load and you have

Unable to get value of property ‘user.agent’ error under Development Mode, you should instruct your IE how to interpret application’s page. To do this, put

<metahttp-equiv="X-UA-Compatible"content="IE=8">

in your index.jsp or whatever you use to render the app. More information on

GWT wiki page.

— Previous article

GWT has bug in Dev mode for Chrome

Next article —

Numery masowo przenoszone do Play

You May Also Like
DDevelopment & Design

Wicket form submit not safe for redirecting to intercept page

The problem When you have a form, that anybody can see, but only logged on users can POST, you may want to redirect the user to the login page, and back to the form after login Using wicket 1.3/1.4, if you do that using redirectToInterceptPage(loginP...The problem When you have a form, that anybody can see, but only logged on users can POST, you may want to redirect the user to the login page, and back to the form after login Using wicket 1.3/1.4, if you do that using redirectToInterceptPage(loginP...
DDevelopment & Design

Context menu or Action buttons ?

Recently I was drawn into one of those UI "religious" disputes that has no easy answers and usually both sides are right. One of our web developers was trying out new web tech (with pretty rich widget library) and started to question himself about some basic usability decisions. The low level problem in this case is usually brought to "which widget should I use ?". I'm not fond of bringing the usability problems to questions: Should I use Tabs over Menu ? Or should I use Context menu instead of buttons panel ? But sometimes if time is crucial factor and other usability levels are by default not addressed at all - better developer that asks those basic questions than developer that do not question himself at all.