Re: Placement of boot script in body vs. head
Hi Thomas,
body
noscript
You must have JavaScript enabled blah blah blah
/noscript
script
document.write(div id='loading'Loading… + /div);
/script
script src=myapp/myapp.nocache.js/script
With the first thing you do in the onModuleLoad is
Document.get().getElementById('loading').removeFromParent();
The bootstrap script is as early as possible within the body yet not at
the very beginning.
Okay, so body placement is required in this case. OTOH if we don't
write to the document before the boot script, then I guess there's no
reason to avoid placing it in the head if that works (as it seems to),
despite what the guide recommends.
Michael
Thomas Broyer said:
On Thursday, November 8, 2012 3:50:47 AM UTC+1, Michael Allan wrote:
Hi Matthew,
My understanding is that when the browser sees a script tag, it
needs to block until the script resource is available before it can
resume parsing and displaying the rest of the page's contents.
Putting the script tag at the end helps avoid this so the page
renders faster.
I was thinking along the same lines at first. But then the guide
says, You want to put the GWT selection script as early as possible
within the body, so that it begins fetching the compiled script before
other scripts (because it won't block any other script requests).
https://developers.google.com/web-toolkit/doc/latest/DevGuideOrganizingProjects#DevGuideBootstrap
It really depends on your use case and the user experience you want to have
during loading.
For instance, a very easy way to have a Loading... text on the page:
body
noscript
You must have JavaScript enabled blah blah blah
/noscript
script
document.write(div id='loading'Loading… + /div);
/script
script src=myapp/myapp.nocache.js/script
With the first thing you do in the onModuleLoad is
Document.get().getElementById('loading').removeFromParent();
The bootstrap script is as early as possible within the body yet not at
the very beginning.
Now that HTML has the async script
attribute
http://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html#attr-script-async,
that would be another option if you want to keep your script tags in
the header. (Note that there's a semantics difference since scripts
might execute out of order depending on caching and network speeds.)
Also, it might only work with the xsiframe linker, as the others use
document.write() which IIRC could destroy the document when run async.
--
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.
Placement of boot script in body vs. head
Why place the boot script in the document body, instead of the head? https://developers.google.com/web-toolkit/doc/latest/DevGuideOrganizingProjects#DevGuideHostPage https://developers.google.com/web-toolkit/doc/latest/DevGuideOrganizingProjects#DevGuideBootstrap I've ignored the instructions and placed it in the head (std, xs and xsiframe linkers) with no apparent problems. What am I missing? -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ -- 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.
Re: Placement of boot script in body vs. head
Hi Matthew, My understanding is that when the browser sees a script tag, it needs to block until the script resource is available before it can resume parsing and displaying the rest of the page's contents. Putting the script tag at the end helps avoid this so the page renders faster. I was thinking along the same lines at first. But then the guide says, You want to put the GWT selection script as early as possible within the body, so that it begins fetching the compiled script before other scripts (because it won't block any other script requests). https://developers.google.com/web-toolkit/doc/latest/DevGuideOrganizingProjects#DevGuideBootstrap So best is top of body. But why not even earlier in the head? Michael Now that HTML has the async script attributehttp://www.whatwg.org/specs/web-apps/current-work/multipage/scripting-1.html#attr-script-async, that would be another option if you want to keep your script tags in the header. (Note that there's a semantics difference since scripts might execute out of order depending on caching and network speeds.) -- 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.
Re: Implementing Normal HTML Instead of GWT
Manuel said: . are you planning to send this to gwt? . to play with this code, do I have to download the entire kit or may I patch just some classes? . does it work with 2.5. I plan to merge 2.5 once it's released. I expect it'll work, though there might be trade offs. We absolutely need the BFCache for our app because it runs cross-page. So we'd override anything that was incompatible, if we had to. If you need to patch it across to the RC meantime, here are the diffs: http://zelea.com/var/db/repo/gwt/ If anyone else finds it useful, we can look at sending it upstream. -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ Manuel Carrasco Moñino said: On Mon, Oct 1, 2012 at 12:44 AM, Michael Allan m...@zelea.com wrote: Manuel Carrasco Moñino said: ... basically a gwt app is a javascript inside an html, ... so when you change to other html [page], your app is unloaded from memory and you have to load it in the new html [page]. If anyone needs to avoid page unloading, here's a branch of GWT with limited support for the BFCache (rapid back-and-forth navigation): http://zelea.com/project/gwt/ Michael, Interesting stuff, a couple of cuestions: . are you planning to send this to gwt? . to play with this code, do I have to download the entire kit or may I patch just some classes? . does it work with 2.5. - Manolo -- 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.
Re: Implementing Normal HTML Instead of GWT
Manuel Carrasco Moñino said: ... basically a gwt app is a javascript inside an html, ... so when you change to other html [page], your app is unloaded from memory and you have to load it in the new html [page]. If anyone needs to avoid page unloading, here's a branch of GWT with limited support for the BFCache (rapid back-and-forth navigation): http://zelea.com/project/gwt/ -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ -- 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.
Re: Cross Site Request
Padding the response with a function call - e.g. callback( ... ) - is
what makes it readable by pages from other domains. If that's what
you need and the source domain provides only JSON:
[{symbol: ABC,price: 87.86,change: -0.41}]
then one solution (I've heard) is to create a pipe that reads the
JSON from the original source and outputs it as JSONP:
callback( [{symbol: ABC,price: 87.86,change: -0.41}] );
Pages from any domain may direct their requests to the pipe.
--
Michael Allan
Toronto, +1 416-699-9528
http://zelea.com/
Muhammad Muaz said:
I am trying this tutorial
https://developers.google.com/web-toolkit/doc/2.0/tutorial/Xsite,it is
working fine if server specify the call back object, like if server prints
like this,
callback125([{symbol:DDD,price:10.610339195026,change:0.053085447454327}]);
But my requirements are like, server can only print in pure `JSON` form
like this
[{symbol: ABC,price: 87.86,change: -0.41}]
I tried to do so, json is retrieving but the callback method is not
invoking, Is there any solution that we dont need to specify callback
method ?
--
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.
Re: which EventBus
andrewsc said: I've seen SimpleEventBus ... being used in 2.4 apps, but I can't find any description of it, apart from JavaDoc mentining it is a wrap around legacy. Does anyone have more material about SimpleEventBus ? Up another level and there are some docs: http://google-web-toolkit.googlecode.com/svn/javadoc/2.4/com/google/web/bindery/event/shared/EventBus.html Note the duplication between these two packages: http://google-web-toolkit.googlecode.com/svn/javadoc/2.4/com/google/web/bindery/event/shared/package-summary.html http://google-web-toolkit.googlecode.com/svn/javadoc/2.4/com/google/gwt/event/shared/package-summary.html Myself, I use the 'bindery' one: http://google-web-toolkit.googlecode.com/svn/javadoc/2.4/com/google/web/bindery/event/shared/SimpleEventBus.html -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ -- 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.
Re: EventBus Vs HandlerManger
http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/event/shared/HandlerManager.html I've inferred that EventBus is for centralized dispatch, while HandlerManager is for widget-specific dispatch and backward compatibility with legacy code. (It looks like a half finished transition. We might be stuck with it till someone volunteers to clean it up.) -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ Adio said: Hi everyone. Can someone tell me what is the difference between EventBus and HandlerManager ? and when to use eachone of them ? To me they are do the same task ... ! Thank you a lot . -- 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.
Re: Couple CSS questions
Adolfo Panizo Touzon said:
... I think you have two options to solve this:
- One is adding* !important* (in order to overwrite the custom
css for the datePicker) to your css rules.
- The other one is create your custom * DatePickerStyle.css *and
add it to your DatePicker class*.*
Another option is to increase the specificity of your CSS selector, so
that it takes precedence over Google's built-in style rules. My own
notes on GWT styling are located here, in case you find them useful:
http://zelea.com/project/votorola/a/web/context/web/gwt.css
--
Michael Allan
Toronto, +1 416-699-9528
http://zelea.com/
2012/4/24 Mike Dee mdichiapp...@gmail.com
How is this for a strategy of tweaking the look of many of the GWT widgets
across an entire app? Copy standard.css into the project and name it
MyApp.css. Reference MyApp.css in the ClientBundle, like this:
public interface MyAppResources extends ClientBundle
{
...
@Source( com/myapp/client/resources/MyApp.css )
@CssResource.NotStrict
public MyAppStyles css();
...
}
And then just tweak the CSS in MyApp.css?
That leads to the second question. So far, this strategy seems to work
fine. However, I'm having trouble with the DateBox. I simply want the
input area associated with the DateBox to have a smaller font size. So I
change this:
.gwt-DateBox input {
width: 8em;
}
to this:
.gwt-DateBox input {
width: 8em;
font-size: 8pt;
}
Seems to have no effect (see attached screenshot). Looking at the CSS in
Chrome (inspect element), the input item is definitely tagged as
.gwt-DateBox. Any ideas?
--
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.
Re: permutation explosion
Joseph Lust said: I misread this as *Precambrian Explosion *at first. In the Call for Action thread, the concern is a Permian Extinction. Michael -- 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.
BFCache support, aka page cache or fast history navigation
I have an experimental branch of GWT 2.4 to share. This may be of interest to developers of embedded apps who expect a lot of navigation between pages. It offers BFCache support for faster back-and-forth navigation in browsers such as Firefox, Opera and Chrome. http://zelea.com/project/gwt/build/out/doc/javadoc/com/google/gwt/user/client/Window.html#isCloseHandlingEnabled() It also offers pagehide handlers as an alternative to GWT's window-close handlers, which are incompatible with the BFCache. http://zelea.com/project/gwt/build/out/doc/javadoc/com/google/gwt/user/client/Window.html#addPageHideHandler(com.google.gwt.user.client.PageHideHandler) For more information, please see: http://zelea.com/project/gwt/ -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ -- 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.
Re: How to get page state
Jens said: You don't have that many options if you have to reload your site: - store your state in the URL if possible (GWT's Place feature can help you do so, you don't have to use MVP/Activities) - store it using HTML 5 Web Storage (browser support: http://caniuse.com/#search=web storage) - store it in cookies (only if you want to support IE6/7 and you can't store the state in the URL). Here's an example of both Web Storage and cookies for persisting state: http://zelea.com/project/votorola/s/gwt/stage/Stage.java It's running here. The black linkbar at the top uses it: http://zelea.com/w/User:Frank-FlippityNet/Sys/p/sandbox -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ -- 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.
Re: GWT history handling library - give it a try
Page StateNavigator Not Found Kostya Kulagin said: Simple open source etc library for automatical handling of GWT components state in URL (browser history). Contains sample application which demonstrates its usage. Give it a try :) http://code.google.com/p/gwt-state-navigator/wiki/StateNavigator -- 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.
Re: Java's Write Once, Run Anywhere for Mobile with GWT is Here!
gwt.user wrote: Besides that take a closer look at those links of yours and you will see my real name in there I decided to follow your advice and take a closer look. I found one thread of yours particularly informative, as it concerns a feature of an Emitrom product that you were apparently unaware of: http://groups.google.com/group/google-web-toolkit/t/5724a1dee172cc8e Since you first became active on the Internet just over 3 months ago, every one of your posts has been a plug for an Emitrom product. http://groups.google.com/groups/profile?enc_user=WK90gxEAAADsCgaXI-fgOhh6AnhOxWv09H2X7Ff3dK7InhkhG5y-QQ Here is a quote from each: 05-17. this is just amazing !! 05-17. How did you implement the animation 05-18. everything works great 05-18. i came accross this project here gwt4air and i could not believe my eyes 05-19. Starting a fight ? What fight ? 05-23. By the way have you ever thought about selling this to Adobe? 05-26. If i could come up with only half of the ideas poeple like you have 05-31. How do i use RPC with the gwt4air Flex API? 06-04. I m trying to add a google maps in my application 06-08. How did you do that ? 06-14. We need to be able to access physical files system from GWT application. Does anyone have any suggestions? 06-15. Does anyone has any other recommendation? 06-15. Applet ? What s that ? :) Either you use HTML5 API (really limited) or flash(gwt4air) 06-24. Amazing component. I ve been looking for something like for a long time now 06-25. But i will put gwt4air in that list. 08-13. Great Job like alsways Alain 08-29. Alain I ve been following you work since gwt4air 1.0 and i really admire the stuff you are coming up with. Please do not take offense. I doubt that anyone can benefit further from these one-sided recommendations, least of all the folks at Emitrom. You may want to get a new alias. -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ gwt.user wrote: @Michael Since you have been searching about my posts then you must also have seen that i said we do a lot of flex/air development at my company. And we were looking for a way to do that with GWT. If you know another project that enables that please feel free to let me know.I ll be preaching that one also. Besides that take a closer look at those links of yours and you will see my real name in there Last but not least this here is about Gwt4Titanium Mobile. What about focusing on that ? If you guyz have nothing to say about it, that s your right. Like the Emitrom guyz said just ignore the post. P.S I beg your pardon, but these two facts make you an unreliable source of information in this particular thread.. Great. i m really impressed by your work as detective. -- 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.
Re: Extra Outer ScrollPanel in Firefox
Beginner's luck. leslie wrote: A beautiful thing happens. The extra scroll bars go away and the ListBox contains it's own vertical scroll bar which functions in the expected and desired way. Great stuff. Michael I thank you very much. This is a big help to me. -- 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.
Bindery package refactoring?
I've been wondering about the new bindery classes, as well. I found no explanation in the API. It looks like 2.3 may have been released in mid-transition. Ed wrote: The class LegacyHandlerWrapper is used to wrap the new HandlerRegistration. 2.3.0 does not have LegacyHandlerWrapper. I found I had to code my own. Here's my version, in case anyone prefers it. ;-) http://zelea.com/project/votorola/g/web/gwt/HandlerRegistrationCW.java -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ Ed wrote: I just upgraded from 2.1.1. to version 2.3.0 and not noticed the new bindery package. The Binery package contains a new HandlerRegistration class. When adding a handler you still receive the old HandlerRegistration (from the shared package). I also noticed that the Has**Handlers like the HasClickHandlers contains the old HandlerRegistration. The class LegacyHandlerWrapper is used to wrap the new HandlerRegistration. What is the plan/roadmap for these new classes like HandlerRegistration. Will the old ones b decprectaed in 3.0 ? and the Has*Handlers return the new HandlerRegistration ? -- 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.
Re: Bindery package refactoring?
Ed Bras wrote: 2.3.0 does not have LegacyHandlerWrapper. Mine does. In the gwt-user-2.3.0.jar I find: com.google.gwt.event.shared.LegacyHandlerWrapper I guess it's just missing from the API docs, then. M -- 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.
Re: Extra Outer ScrollPanel in Firefox
ListBox list = new ListBox(); ScrollPanel scrollpanel = new ScrollPanel( list ); VerticalPanel main = new VerticalPanel(); main.add( scrollpanel ); What happens if you drop the scroll panel, and just add the list box? -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ leslie wrote: Mac OS X 10.5 Java 6 GWT 2.3.0 I'm having difficulty with my application rendering in Firefox. I've created a ListBox that will contain names and I've placed it in a ScrollPanel. ListBox list = new ListBox(); ScrollPanel scrollpanel = new ScrollPanel( list ); VerticalPanel main = new VerticalPanel(); main.add( scrollpanel ); When the component appears in the Firefox browser, horizontal and the vertical scrollbars appear on some sort of outer component, as an extra ScrollPanel even before the list is populated with names. Moreover, when the listbox becomes populated, I see the proper Vertical scrollbar for the list box but the outer scrollbar remains. That is, I can see a properly configured ListBox within a ScrollPanel, within some form of unknown ScrollPanel. By contrast, In Safari I observe the desired behavior. That is, the scroll bars do not appear until the list is populated with names. At that time, the vertical bar appears and it functions in the desired way, scrolling the list so that the names become visible. There are no other scroll bars other than what are expected. I've come across a thread somewhere that suggested I must resize the ListBox because it is too wide. But too wide for what? What is causing the extra ScrollPanel to appear in Firefox and how can I remove it? Many thanks. -- 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.
Re: Java's Write Once, Run Anywhere for Mobile with GWT is Here!
gwt.user wrote: @Ivan Do i sence a litlle jealousy goin on ? Or do you just need some attention ? Ivan appears to have jumped to conclusions. Nobody knows your identity because you have chosen to hide it behind the alias gwt.u...@yahoo.fr. At the same time, you are busy advocating for gwt4air, and not doing much else besides: http://groups.google.com/groups/profile?enc_user=WK90gxEAAADsCgaXI-fgOhh6AnhOxWv09H2X7Ff3dK7InhkhG5y-QQ http://www.google.ca/search?q=gwt.user%40yahoo.fr; I beg your pardon, but these two facts make you an unreliable source of information in this particular thread. -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ gwt.user wrote: @Ivan Do i sence a litlle jealousy goin on ? Or do you just need some attention ? What about you building or even plagiarize anything usefull so someone can also talk about you ? Now let me sign with Alain again so you have something to talk about. (Because you cant think by yourself that this was a copy and paste mistake) Alain -- 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.
Re: GWT customization (CSS) by web designer
A simple approach is to pull the designer's style sheet into the GWT page, just as you would into a static page. Here's an example: http://zelea.com/project/votorola/a/web/base/xf/default.html See the link element. See also the caveat in this style sheet, which is imported into the main sheet: http://zelea.com/project/votorola/a/web/base/web/gwt.css -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ Otto Chrons wrote: We are trying out GWT 2.3 for the first time to develop a web application for professional users (not consumers). What is the best way to enable a web designer to work on customizing the UI, especially CSS, without having him work through the full GWT compile/package scheme? Ideally we would just compile the production version of the app, deploy it and the designer could then work with the static deployment and directly edit CSS files so that changes could be seen just by reloading the web page. - Otto -- 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.
Re: How to set the selection color of a CellList widget?
Hi Rod, I found I had to disable keyboard selection. http://zelea.com/project/votorola/a/count/resource/SacSelectionV.java sacListV.setKeyboardSelectionPolicy( HasKeyboardSelectionPolicy.KeyboardSelectionPolicy. // BOUND_TO_SELECTION ); causes odd coloured (yellow) background to appear on first click DISABLED ); Otherwise I had no problem with yellow. My selections are blue. Click on the ugly, maroon coloured button at top left. See the popup: http://zelea.com/y/vw/xf/#c=DVs=G!p!sandbox -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ Rod Trendy wrote: Hello everyone, I can't help it anymore. I am really stuck on the CellList. Creating and working with a CellList is quite simple, but I can't change the style of the CellList. I search the internet via Google but I couldn't find any results that 'really' helped me out. I just want to be able to change the background color of a selected cell, but whatever I try the color won't change from yellow to blue. All I've got so far is changing the whole background of the celllist into blue (including the cells which are not selected) but that's getting me nowhere. Please, can anyone help me out? I really would like to have a step by step guide for this problem. I am exhausted :( Regards, Rod -- 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.
Re: How to set the selection color of a CellList widget?
PS - I should have mentioned that we're not inheriting any theme module: http://zelea.com/project/votorola/a/xf/Entry.gwt.xml Rod Trendy wrote: I can't help it anymore. I am really stuck on the CellList. Creating and working with a CellList is quite simple, but I can't change the style of the CellList. ... -- 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.
Re: why does DockLayoutPanel care about the order of its elements?
Ivan Pulleyn wrote: DockLayoutPanel assumes that center is all the space that wasn't taken up by a component that was added to the north, east, etc. There's a built in assumption that when you call add() you have finished adding any components that will be docked to an edge. The add methods for the edges (west, north etc.) seem to mix two concerns that might better be kept separate: 1) specifying the size constraint for each edge, and 2) adding the edge child. (Maybe that's a bug in itself.) As a workaround: first add a panel to each of the edges you need. This sets the size of the edge. Later you can use the panels to add and remove the edge children, at any time. -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ On Wed, Aug 10, 2011 at 3:09 AM, frische andreasfris...@gmail.com wrote: Hi, why does DockLayoutPanel need its Center Element last? -- 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.
Re: About GWT opinion in thoughtworks technology radar july 2011
Emilio Bravo wrote: http://www.thoughtworks.com/articles/technology-radar-july-2011#Platforms First, in many ways, JavaScript is more powerful and expressive than Java, so we suspect that the generation is going in the wrong direction. more powerfull for that? This critique makes no sense, as the two languages are comparable in expressivity. Admittedly something is lost in translating from one to the other, and maybe that's what they want to say. Secondly, it is impossible to hide a complex abstraction difference like that from event-driven desktop to stateless-web without leaky abstraction headaches eventually popping up I can't comment, I do not know the compilation process. The JavaScript engines that GWT targets are not stateless. There is no such gross incompatibility between the source and target platforms. I wonder what they were thinking? Third, it suffers from the same shortcomings of many elaborate frameworks, where building simple, aligned applications is quick and easy, building more sophisticated but not supported functionality is possible but difficult, and building the level of sophistication required by any non-trivial application becomes either impossible or so difficult it isn’t reasonable. What is meant by functionality not supported?. Program non-trivial applications with GWT is easier than directly in javascript I have the opposite problem. I often want to do something that would be trivial in JavaScript or HTML, but I have to struggle a little to accomplish the same thing in GWT. Something as simple as wrapping a Widget in a div - just for a quick layout test - requires reading the API docs. I'm no a GWT expert yet, and I guess that's part of the problem. I'm more familiar with CSS, HTML and even JavaScript than I am with GWT. -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ -- 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.
Re: GWT GeoMap
Kady wrote: We want to add a simple geoMap to our application. Through the EntryPoint we add the created GeoMap instance to a div onto the page. Is there any script other than the generated GWT js that needs to be added to the application? ungarida wrote: http://code.google.com/p/gwt-google-apis/wiki/MapsGettingStarted Here's a running example (work in progress) that uses OpenLayers instead of just Google: http://zelea.com/var/deploy/xf/#c=DumG You can choose different map providers using the (+) control at top right. We also hooked the geomap panner and zoom controls into the browser history, so you can use the back/forward buttons. Source: http://zelea.com/project/votorola/a/web/base/xf/default.html http://zelea.com/project/votorola/a/xf/Entry.gwt.xml http://zelea.com/project/votorola/a/xf/geo/ -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ -- 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.
Re: my biggest problem with gwt
Dennis Haupt wrote: that helped most, thanks More on that here: http://code.google.com/webtoolkit/doc/latest/FAQ_DebuggingAndCompiling.html#Can_I_speed_up_the_GWT_compiler? The allowable values for user.agent are defined here: http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/UserAgent.gwt.xml Myself, I find that devmode (hosted mode) is fast enough. It's slow to launch in the first place (15 s), but it re-compiles quickly when I hit refresh (3 s). vinayak kulkarni wrote: This is because GWT compiles the javascript for all the browsers.. around 5 browsers - 10 permutations.. For the development mode, you can compile only for one browser. Ex: for IE, use the below property in *.gwt.xml file -- Michael Allan Toronto, +1 416-699-9528 http://zelea.com/ -- 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.
