Okay, I think I'm starting to see the different options. I can ask the same question more specific now. Formerly, I was used to working like this: I wrote PHP and added all the elements I needed (forms for example) in HTML. Someone else could take control of laying out these elements in any way he liked. He could alter the HTML of the page apart from my PHP and as long as the elements kept their names, everything kept working. This way, I could fix my attention on the program and others could fix their attention at the lay-out.
In GWT it's possible to create a lay-out by positioning different widgets in Java code. It's also possible to give these widgets style names which let CSS take control of their layout. But is it also possible of laying out the elements without entering the Java code? I can see how to seperate lay-out with program code but the lay-out would still be specified in Java, no? Maarten On 29 jul, 20:21, Ian Bambury <ianbamb...@gmail.com> wrote: > You have html in your index file. You have code in your java files. How you > split everything up is your decision. > > In your html host page, you could have 2 divs, defining the layout for page1 > and page 2. In your GWT code, yo make one or other visible as you need them. > > It might get a little unmanageable for 100 pages, so you could have html > files on the server and go and pick them up as required. > > You can do both at the same time: have a basic menuing framework and pick up > html from server-side pages and slot them into part of your app's display > area. That's what my examples site does, mostly to keep all the text out of > the initial download. It also means you can easily arrange to get spidered > by search engines. > > Ian > > http://examples.roughian.com > > 2009/7/29 maarten.de...@gmail.com <maarten.de...@gmail.com> > > > > > Hi, > > > I've been trying out GWT for a couple of weeks now and stumbled upon a > > beginner's question relating multiple pages. > > > For example, let's suppose an application with users where you have an > > application page, a login page and a register page. Using GWT for the > > application page speaks for itself, but what about the other pages? > > > I've read the other topics about this problem in the group. It seems > > the proper GWT solution is to clear window and load another GUI there. > > This would actually wrap all the pages within the application. I can > > see how this solution would work, but then you lack a lot of usefull > > HTML pages that lay out the login and register forms. This way, making > > the lay-out of the page cannot be seperated from coding the > > application, at least not in HTML vs GWT/Java. > > > Is there another way of working for this? One that does permit to > > seperate page lay-out and coding? > > > Greets, > > > Maarten Decat --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
