On 08/07/2013 08:10 AM, Tomas Jelinek wrote:
Hey Roy,well, I'm not a fan of using the dictionary - it is an associative array and opens a door to mistakes which will not be handled by compiler like locales.get("naem") will not return me the name :) At least not for data we know how will look like (e.g. for the os info) We already embed some info into the host page and use it on the client using JavaScript Overlay Types [4]. You can have a look for example at GwtDynamicHostPageServlet: request.setAttribute(MD5Attributes.ATTR_USER_INFO.getKey(), getUserInfoObject(loggedInUser)); and on the FE side the overlay type is: AutoLoginData But I would be careful how much info do we want to embed into the host page - it can make it significantly big and influence the performance (for example we are using code splitting [5] to download only the parts of the app we actually need when we need them). To embed too much info which is not always needed is a step to the opposite direction. I don't say it is wrong, it just has to be considered. Tomas [4]: http://googlewebtoolkit.blogspot.cz/2008/08/getting-to-really-know-gwt-part-2.html [5]: http://www.gwtproject.org/doc/latest/DevGuideCodeSplitting.html
there is still the point of having multiple files, which seems like an easy win by merging to a single file, and if needed, using pre-compile to create the cloned files
_______________________________________________ Engine-devel mailing list Engine-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
