Hi Thomas, thank you very much for your explanations. That's exactly what I was looking for.
Best regards, Alessandro On 2 Aug., 20:52, Thomas Dvornik <[email protected]> wrote: > Hey Alessandro, > > I'm not a GWT expert, but hopefully this will help. > > Your right about the look of the URL, and that would be one way to do > it. Your GWT entry-point (http://<base-url>/) would process the token, > which is everything after the #. So if you had #comp1;comp2;comp3; > then your entry-point class would instantiate whatever it needs to and > display the correct components. > > That should answer your second question as well, if I understood it > correctly. The entry-point class "listens" on the base URL, and can > call different servlets. Technically, you can have however many > servlets you want to process the Ajax request. > > There are some other options too. > > 1. A GWT app can have multiple entry points. So http://<baseurl>/comp1/ > and http://<baseurl>/comp2/ can be completely different entry points > in the same project. > > 2. You could have multiple GWT instances running. In other words, you > can have separate GWT projects for different components or apps. > > Tom > > On Aug 2, 3:02 am, "A.Augustini" <[email protected]> > wrote: > > > Really no brief suggestions to these basic topics here??? > > > I'd really appreciate any helping hints. > > > Best regards, > > Alessandro > > > On 30 Jul., 19:54, "A.Augustini" <[email protected]> > > wrote: > > > > @Sebastian: Thank you very much for the quick response. > > > > The link to the "Gears binding for GWT" was very helpful and just > > > what I was looking for. > > > > Concerning the issue with the bookmarkable URLs (traditional vs. > > > Ajax-ified URLs), I'm still not quite sure if I totally understood > > > the "History" mechanism for my scenario: > > > > Suppose the AdminConsole's main screen is a 'HorizontalSplitPanel" > > > showing a 'VerticalPanel" with multiple "available web sites" links > > > to the left and a corresp. "web site details" subpanel to the right. > > > Clicking one such 'Hyperlink' should kick off the download of the > > > corresp. site details and display them on the right subpanel. > > > > My intention is to have workable URLs as close as possible to > > > > * http://{base-url}/{site-name}/index.html (index.html suppressible) > > > * http://{base-url}/{site-name}/{page-name}.html (.html suppress.) > > > * http://{base-url}/{site-name}/{comp1}/{comp2}/.../{compN}.html > > > > where only {base-url} is a priori known (i.e. static). > > > > 1. Having N dynamically specified site names, what would the > > > Ajax-ified bookmarkable URLs of these 'Hyperlinks' look like? > > > > Perhaps something comparable to > > > "http://{base-url}.html#{site-name};{comp1};...;{compN};{sid}"; ?? > > > > 2. And, what Servlets would be listening to which URL(s) in this > > > scenario? > > > > Is it a 2-sevlets scenario: an "AppControllerServlet" listening > > > to "http://{base-url}"; and serving traditional requests, and a > > > "GWT-RPC-Servlet" for the Ajax-based requests, listening to > > > another (?) url pattern? > > > -- Or would just one servlet suffice? > > > > Thank you all very much for any constructive help in advance. > > > > Best regards, > > > Alessandro > > > > Following the examples, I guess sth. similar to: > > > > http://app-base-url/mysite-001.html#state1 > > > > On 30 Jul., 15:54, Sebastian Rothbucher > > > > <[email protected]> wrote: > > > > Hi Alessandro, > > > > > GWT features a history mechanism which could solve the first > > > > question:http://google-web-toolkit.googlecode.com/svn/javadoc/1.5/com/google/g... > > > > orhttp://code.google.com/intl/de-DE/webtoolkit/doc/latest/DevGuideCodin... > > > > provide info on that: rather than using a file path, you'd use #.... > > > > (an identifier after a hash). Many AJAX apps work that way to prevent > > > > reloads > > > > > GWT is quite powerful concerning internationalization using property > > > > files (you delcare an interface and provide a property file and bind > > > > it together using the GWT class) > > > > > Concerning in-place editing, there is surely a way; Google wave is > > > > implemented in GWT and also features rich editing features. > > > > > Finally, there is a gears binding for GWT (http://code.google.com/p/ > > > > gwt-google-apis/) which you can use for offline storage (modern > > > > browser or plugin required). > > > > > Hope this helps... > > > > Sebastian > > > > > On 30 Jul., 13:41, "A.Augustini" <[email protected]> > > > > wrote: > > > > > > [**Republished to get rid of ugly line-break cluttering**] > > > > > > Dear GWT Community members: > > > > > > As GWT newbie I'm currently evaluating GWT for some potential future > > > > > projects. After reading available introductory materials, I'm now > > > > > wondering if GWT is the appropriate candidate for my specific app > > > > > scenario. > > > > > > Obviously there are 2 basic GWT app dev styles: > > > > > (1) "desktop-app setup": > > > > > one GWT module on one almost empty "carrier" HTML page. > > > > > (2) "traditional-web setup": > > > > > several traditional HTML pages with some GWT widgets. > > > > > > Supposing this is correct: What would be the ideal GWT app > > > > > architecture for the following, "more hybrid" scenerio? > > > > > > Say we've to build a kind of "Mini Online Site Builder" with some > > > > > simple CMS functionality and basically consisting of 2 main > > > > > requirements for 2 available enduser roles: > > > > > > (A) 'SiteAdmins' have secured access to an 'AdminConsole' where they > > > > > dynamically *compose/edit*, *preview* and publish 'WebSites' > > > > > -- AdminConsole thus supporting "2 work modes": Edit & Preview! > > > > > > - 'WebSites' are all published under a common base URL plus > > > > > admin-specified relative site path. > > > > > - 'WebSites' consist of 'Pages', probably associated to a > > > > > default 'MasterPage' and default "Theme". > > > > > - 'Page' may have own 'MasterPage' and 'Theme'. > > > > > - 'MasterPage' is composed of typed 'PageRegions' > > > > > (e.g. Header-/FooterRegion, NavRegion, ContentRegion, ...) > > > > > - 'PageRegion' has list of 'Content' elements of some > > > > > 'ContentType' that is permissible with that region's type. > > > > > ContentTypes could be: TextParagraph, HTMLParagraph, > > > > > ImagedTextParagraph, Image, Table, Form/Survey, etc. > > > > > - SiteAdmins would have some advanced widgets to define complex > > > > > domain content elements, e.g. spreadsheets, price tables, .. > > > > > (=> good candiate for GWT) > > > > > > (B) 'Users' visit the resulting web sites through site-specific URL > > > > > and > > > > > - navigate back and forth and may submit some public or authen- > > > > > tication-requiring ordering/posting forms. > > > > > - User experience should be the traditional (!) web site UX > > > > > (=>good candidate for JSF instead of GWT(?)) > > > > > > Obviously, the AdminConsole impl is a good candidate for a pure GWT > > > > > module (see (1) above) whereas I rather would choose pattern (2) > > > > > for the web site renderings -- the above-mentioned "hybridity". > > > > > > Now, I need some experts' advice in the following topics: > > > > > > 1. Is GWT suitable for "mimicking" traditional web pages within a > > > > > GWT widget pane, i.e. where users can navigate through pages > > > > > via several seo-friendly URLs (or just one(?))? > > > > > > I guess *client-side* logic would download the site/page > > > > > representation via GWT-RPC and dynamically render it on the > > > > > client, BUT ... > > > > > > ...How can the *inter-page navigation* via bookmarkable URLs > > > > > be realized??? > > > > > => Could I still have bookmarkable URLs like > > > > > "www.acme.com/site1/about-us" working correctly in my > > > > > browser??? > > > > > > 2. Where would I place the page interpretation/rendering logic, and > > > > > what would be its output format? > > > > > > 3. How would I realize the *preview* and *edit* modes in the > > > > > AdminConsole? > > > > > > I suppose an "in-place edit strategy" would be optimal, where the > > > > > page preview is visible and only the active section panel gets > > > > > decorated with edit/save buttons -- thus avoiding separate > > > > > read-only and read-write views. > > > > > > 4. Is there a client-side storage mechanism to temporarily save > > > > > current WebSite definition entities? > > > > > If so, is there a size limitation for this storage? > > > > > > In my current situation, I would highly appreciate any realization > > > > > hints. Thank you very much in advance. > > > > > > Best regards, > > > > > Alessandro -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
