Tuesday, January 14, 2014

Best practice for rich contnent (pictures and text) presentation in (m)gwt

I developed an mgwt client and want to present rich content there. Today I have a HTML file in my src directory and on client-side the HTML-file is loaded via TextResource ClientBundle. This solution is resource saving and the resource is offline available (HTML5 manifest enabled) but has some disadvantages:
- The ClientResource is created on compile-time. If I want to change the HTML-content I have to make a recompile of my client. So quick changes are impossible and my customers always need to ask me for a recompile if they want to change something.
- I am not able to load pictures in the HTML content

An other solution would be to display the HTML file (content) in an gwt frame. This solution would have the advantage to display pictures in my HTML and store them offline (HTML5 maniest). My customers can change the HTML content without asking me for a recompile. But on mgwt, frames are not good supported (see https://groups.google.com/d/msg/mgwt/9P73HQc9fig/oDmy6vMjihoJ).
- I don't want scrollbars enabled in my mobile application (frame-height must be 100% of the HTML file to avoid scrollbars and this must be done dynamically)

Is there an easy (best practice) way to display and alter rich content (formatted text and pictures) in (m)gwt?

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment