How to include an Iframe within a Vaadin App? - gwt

I would like to include an Iframe within my Vaadin App, how do I proceed implementing this? My initial idea was to wrap the GWT Frame widget, using the approach as described in the Book of Vaadin. Is this at all possible, or is there a better way?

I guess I didn't read the manual (Book of Vaadin) good enough. I found the answer to my question in section 5.15.3 Browser Frames. Ups.

Related

Which is best for built a web tool in gwt

I am new to GWT. can anyone help me to understand which one is best to built a web tool. Fluid Layout or Fixed layout...?
help me in this...
Thanks,,
This depends on the application you want to create.
I would always go for the flexible layout, if there a no contrary requirements.

Page Navigation in GWT Application

I want to navigate to another page in my application. I don't want the page to reload(i.e.. application should be a single URL application).
I know only one way to accomplish this by changing the proper div attached in the RootPanel by whatever data I want to display. But I fell that might get cumbersome if there are many navigations(I haven't tried it though :P).
Is there any other way to accomplish this or make the above said approach better?
Thanks in advance.
I guess you need GWT Development with Activities and Places
Well ,its time to have a look on MVP
With that you can do
History.newItem(tokenOfYourPresenterScreen);
A nice single EntryPoint demo app is here : (BrowserHistoryExample.java)
http://www.gwtproject.org/doc/latest/DevGuideCodingBasicsHistory.html
I added the below to the example to demonstrate links.
vertPanel.add(new Label("Access history via Hyperlinks"));
vertPanel.add(new Hyperlink("External Page 0","page0"));
vertPanel.add(new Hyperlink("External Page 1","page1"));
vertPanel.add(new Hyperlink("External Page 2","page2"));

Best practices for designing GUI in GWT

I have recently started studying Google Web Toolkit. I have went through some walkthroughs, and I think I understand the basics and the idea. However, I have some questions on the overall architecture and design of the applications.
Let's start with the GUI. I want to build a "common" web application, where the user first sees a login page. After successful login, the user is redirected to some kind of index page and a menu is added. I created a new LoginComposite for the login page, and tried to design a nice looking HTML table using the GWT Designer. However, I find that really hard to do, as you cannot set any individual properties on the individual cells (TDs)? There's no way to specify colspan or rowspan, and I can't set any padding or margin on the cells themselves. In short, I know exactly how I would have written the HTML code, but I can't translate that to the designer. Is that just me?
Also, I am wondering about the best practice for code layout and design. I went through the StockWatcher tutorial, but that's really not a very realistic web application. For example, I would like to know how I should design different forms (should each be in a own class inheriting the Composite-class)? How should I switch between forms (for example, first a list view, then a form for editing a chosen item from the list, then a totally different page)? If I have one Composite for each page, and instantiate them when needed in my EntryPoint, would that mean that the client will download all the JavaScript for all those Composites at page load? Should I stick with only one HTML page, or should I have many?
These are questions not really covered by any GWT tutorial. If anyone know a good example of a "real" web application built using GWT, I would love to see it.
Thanks for your input!
There are a whole bunch of resources in Google IO talks. For example:
http://www.google.com/events/io/2011/sessions/high-performance-gwt-best-practices-for-writing-smaller-faster-apps.html
http://www.google.com/events/io/2011/sessions/highly-productive-gwt-rapid-development-with-app-engine-objectify-requestfactory-and-gwt-platform.html
http://www.google.com/events/io/2010/sessions/architecting-production-gwt.html
http://www.google.com/events/io/2010/sessions/architecting-performance-gwt.html
http://www.google.com/events/io/2010/sessions/gwt-ui-overhaul.html
http://www.google.com/events/io/2009/sessions/EffectiveGwt.html
Also, don't expect to be able to edit absolutely everything if you are using the GUI to build your GWT app. Good luck!

Tab UI in Android

I am an Android newbie and I really require your help.
I'd like to develop an app , which its UI is persisted of three Tabs, and the first one a WebView.
since I am not familiar with all the required building blocks, can anyone give me a sample? a guide how to do so?
thanks a lot!
The Android API Demos include several (Tabs1 to Tabs2 sample files) examples. Install, try and have a look at them.
Regarding specifying the content of Tabs you have the possibilities to use Views or Activities. If you check some "Tab" related discussion here you will find that established users prefer to use Views (e.g. here). I took the 'Activity' way so far and feel quite comfortable - but did not go to deep into pros and cons. My current point of view is that you have to decide on each special case and can't give a general recommendation.
there is some tutorials on this page : http://developer.android.com/resources/tutorials/views/index.html

Is it ok to use the web view to render non web content web developing for iOS4

I'm just learning the iPhone SDK and about drawing with CG and UIKit and whilst I can see the usefulness for building interfaces as a web developer I can't help but think it would be a hell of a lot easy if I could layout content (ie heading, paragraphs, lists, images) with html and css
presumably this is possible using the web view and injecting custom html and css into it
is there any reason this is a bad idea?
Yes. It's not only ok, it's pretty common. I recommend having a good reason to do so before using this method. "Because it's easier than using the UIKit framework" is not a good reason.
Go for it. It's one of the tools at your disposal, so don't be shy about using it.