Re: Direct call a RemoteServiceServlet
Hi Gregor, I would like to thank you for your reply. I understood your answers regarding changing of presentation layer concepts. But my client asked me to replace only presentation (Web Tier) and I suggested GWT. I wanted to confirm the possibility of doing it. I am doing research on that. In order to code GWT RPC , I followed the steps mentioned at http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5s=google-web-toolkit-doc-1-5t=DevGuideCreatingServices, it is working fins as said in the example. Here one of stpes mentioed was creating of Asynchronous Interfaces, which is not required my requirment. if i not followed this step then getting error stating cient proxy not found.. Would you please creply though I not require the asynchronous behaviour still, Do I need to create it? Thanks Arul --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWTShell and facelet.
Hmm no, I have a script/script tag. I'm still digging :-) O. 2008/12/9 Sumit Chandel [EMAIL PROTECTED] Hi Olivier, Can you double-check to make sure that you're not using an empty script tag to reference your GWT bootstrap script? I..e, script src=com.google.app.MyModule.nocache.js / versus script src=com.google.app.MyModule.nocache.js/script? The empty script tag has been known to cause issues in hosted mode, and is also known to cause problems in IE 6/7 if I remember correctly. Hope that helps, -Sumit Chandel On Fri, Dec 5, 2008 at 3:05 AM, olivier [EMAIL PROTECTED] wrote: Hi, I'm facing a strange issue. I'm using GWT within a facelet page. This means that I have the following URL http://myserver:8080/MyApp/conf/test.faces test.faces is resolved to test.xtml by the servlet. Compiled mode works fine. But in hosted mode, the module is not loaded. No errors, no traces, nothing. However, the static HTML is displayed ! I tried the verbose mode, but it didn't help. Any clue ? :-) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoying issue, integrating with Hibernate
you should take a look at: http://noon.gilead.free.fr/gilead (formerly known as hibernate4gwt) On Dec 7, 10:54 am, LoneWolf [EMAIL PROTECTED] wrote: Hey, Our application is using Hibernate 3 as the persistence mechanism, and of course we have one-to-many relationship. The problem is when trying to pass a domain object that has a list of lazy initialized objects back to the browser, I got this exception: Caused by: com.google.gwt.user.client.rpc.SerializationException: Type 'org.hibernate.collection.PersistentSet' was not included in the set of types which can be serialized by this SerializationPolicy or its Class object could not be loaded. For security purposes, this type will not be serialized. Yes, I understand this exception but to overcome this issue? 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Toggle text color in timer
Hi All, Thanks for the support for solving this problem... I've created my own Label to make it blink... Thought it might help, I have shared it... http://www.arundhaj.com/2008/12/gwt-blinking-label.html Regards ArunDhaJ --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Error executing RPC call after updating to GWT 1.5.3
I've experienced the same problem. Be sure to use the 1.5.3 version of
the gwt-servlet.jar in your Tomcat deployment. This fixed the problem
for me.
Danny
a_martinez schreef:
Hi,
I developed an application with several services. After updating from
GWT 1.5.2 to 1.5.3 the RPC calls to the server doesn't work anymore. I
got an error message on server side:
java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
at java.util.ArrayList.RangeCheck(ArrayList.java:547)
at java.util.ArrayList.get(ArrayList.java:322)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.extract
(ServerSerializationStreamReader.java:617)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.readInt
(ServerSerializationStreamReader.java:432)
at
com.google.gwt.user.client.rpc.impl.AbstractSerializationStreamReader.prepareToRead
(AbstractSerializationStreamReader.java:38)
at
com.google.gwt.user.server.rpc.impl.ServerSerializationStreamReader.prepareToRead
(ServerSerializationStreamReader.java:383)
at com.google.gwt.user.server.rpc.RPC.decodeRequest(RPC.java:234)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall
(RemoteServiceServlet.java:163)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.doPost
(RemoteServiceServlet.java:86)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:252)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:173)
at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter
(ReplyHeaderFilter.java:96)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter
(ApplicationFilterChain.java:202)
at org.apache.catalina.core.ApplicationFilterChain.doFilter
(ApplicationFilterChain.java:173)
at org.apache.catalina.core.StandardWrapperValve.invoke
(StandardWrapperValve.java:213)
at org.apache.catalina.core.StandardContextValve.invoke
(StandardContextValve.java:178)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke
(SecurityAssociationValve.java:175)
at org.jboss.web.tomcat.security.JaccContextValve.invoke
(JaccContextValve.java:74)
at org.apache.catalina.core.StandardHostValve.invoke
(StandardHostValve.java:126)
at org.apache.catalina.valves.ErrorReportValve.invoke
(ErrorReportValve.java:105)
at org.jboss.web.tomcat.tc5.jca.CachedConnectionValve.invoke
(CachedConnectionValve.java:156)
at org.apache.catalina.core.StandardEngineValve.invoke
(StandardEngineValve.java:107)
at org.apache.catalina.connector.CoyoteAdapter.service
(CoyoteAdapter.java:148)
at org.apache.coyote.http11.Http11Processor.process
(Http11Processor.java:869)
at org.apache.coyote.http11.Http11BaseProtocol
$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:
664)
at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket
(PoolTcpEndpoint.java:527)
at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run
(MasterSlaveWorkerThread.java:112)
at java.lang.Thread.run(Thread.java:619)
This is how I call the service:
diversePanel.add(new Button(Pseudo Login, new ClickListener() {
public void onClick(Widget sender) {
RemoteTypeDefServiceAsync typeDefService =
(RemoteTypeDefServiceAsync) GWT.create(RemoteTypeDefService.class);
ServiceDefTarget target = (ServiceDefTarget)
typeDefService;
String serviceEntryPoint = GWT.getModuleBaseURL()
+TypeDefService;
target.setServiceEntryPoint(serviceEntryPoint);
AsyncCallback callback = new AsyncCallback(){
public void onFailure(Throwable caught){
Window.alert(Login failed.);
}
public void onSuccess(Object result){
Window.alert(Login ok.);
}
};
typeDefService.pseudoLogin(callback);
}
}));
Can someone tell me what is wrong now?
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---
GWT compiler bug - javascript != java when method exists both on interface and superclass
Hi
I have been hunting a bug that only showed itself when my app was
running in the browser.
The problem was that the GWT 1.5.2 compiler produced javascript code
that didnt match the java code.
My situation was the following:
I have the class structure showed below:
interface I {
void init();
}
class A {
public A() {
init();
}
private init() {}
}
class B extends A implements I {
public B() {}
public void init() {}
}
When instantiating B the javascript wrongly calls B.init() which
resultet in an nullpointer in my app.
Notice that A.init() is private and therefore should not be overloaded
in B.
If I inline the A.init() into the constructor of A thus removing the
method - theres no problem..
My guess is that the I interface is the the key to the problem..?
Is there a bug report on this?
If you cant recreate the scenario - ill be happy to try and make some
real example code.
Kind regards
Simon Vogensen
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---
Re: How to share work between Java developers and HTML/CSS designers?
We are in the process of buying a couple of Instantiations GWT Designer licenses. The WYSIWYG capability in their tool is not very flexible, though. We were not able to create any useful screens using the WYSIWYG feature alone. Had to do a lot of manual tweaking. On Dec 5, 9:16 am, rakesh wagh [EMAIL PROTECTED] wrote: Here are few things to consider: - Check the Instantiation Designer tool. Personally never used it beyond evaluation... but you and your team might have some luck with it. - Let the HTML team design the layout. Let the GWT team design the application and place the components as per the layout. Gwt team uses the default widget css. Then let the HTML team work only with the css provided by the gwt team and modify it to meet the new look and feel. - GWT team takes both the layout and the CSS from html team, and include the CSS element as the project progresses. Finally this is what we did: - We created our own widget library with common components for tables, hyperlinks, menus etc. We(developers) spared some time designing the common components as per the graphics design. Finally for most of the part it was only the matter of following the layout. good luck! Rakesh Wagh On Dec 2, 11:36 pm,Nizam[EMAIL PROTECTED] wrote: Are there any best practices in bringing together a multi-disciplinary team of Java developers and HTML/CSS designers in developing a commercial GWT application? Our Java guys cannot do CSS and our HTML/ CSS guys prefer working in DreamWeaver. I haven't seen any material that talks about the team collaboration aspect. Any thoughts? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: How to share work between Java developers and HTML/CSS designers?
After I started this thread, a new article has come up on the GWT blog which talks about how the folks at studyblue.com approached the styling issue. Here is the link to the post: http://googlewebtoolkit.blogspot.com/2008/12/gwt-no-need-to-shortchange-your-style.html On Dec 6, 10:02 am, Chii [EMAIL PROTECTED] wrote: I think the underlying issue here is that the paradym of gwt programming is not the same as the traditional web-app development, where the coder hands to the designer a bunch of variables to which the designer inserts into a template (velocity, freemarker, jsp, you name it). GWT brings to the table the developer as a UI creator. The designer no longer makes the product, but actually designs the blue-print, and that blue print is followed by the developer. I.e., the developer now needs to know about DOM, CSS and HTML (though not to the extend that a designer might). GWT tries to abstract html from making a web UI. Thats my 2 cents anyway. On Dec 3, 4:36 pm,Nizam[EMAIL PROTECTED] wrote: Are there any best practices in bringing together a multi-disciplinary team of Java developers and HTML/CSS designers in developing a commercial GWT application? Our Java guys cannot do CSS and our HTML/ CSS guys prefer working in DreamWeaver. I haven't seen any material that talks about the team collaboration aspect. Any thoughts? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Left or Right arrow Key press doesn't work for Textbox inside a TreeItem in GWT 1.5
Fixed it with the following:-
public void onKeyDown(Widget sender, char keyCode, int arg2) {
if ((keyCode == KEY_LEFT || keyCode == KEY_RIGHT ) (sender
instanceof TextBox)) {
DOM.eventCancelBubble(DOM.eventGetCurrentEvent(), true);
}
}
On Dec 8, 5:25 pm, Ravi [EMAIL PROTECTED] wrote:
Hi,
I have tree with some tree items each of which hosts atextboxwidget.
Everytime i press a left or right arrow key (KEY_LEFT / KEY_RIGHT)
inside thetextboxwithin atreeitem, instead of the cursor moving to
the right or left of the current cursor position, the parent tree node
gets selected in case of left arrow key press while nothing happens
for right key press event.
So, i would like to know if there is any such limitations for the
textboxes added intotreeitem.
Can someone please provide help on this.
Thanks,
ravi
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---
TestBox inside CheckBox's text
I want to use a TextBox inside the CheckBox- label. For example: *[X]* Save in *TextBox* minutes I can do it by using the toString()- method on TextBox, but it is behaving incorrectly: - Firefox (un)checks the CheckBox by clicking into the TextBox - The TextBox- Object is not the TextBox which is displayed - no changes in the original TextBox. Is there a possible way to realize. Except i have to split the components... --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: dao and GWT
You'll be better off asking on the GXT mailing list. This mailing list is specific to GWT. GWT is very different from GXT. -- Arthur Kalmenson On Sun, Dec 7, 2008 at 9:45 PM, rizla [EMAIL PROTECTED] wrote: up :( On 3 Dic, 13:46, rizla [EMAIL PROTECTED] wrote: many thanks for the response to my question, in my gwt project I've used the gxt library. I've implementd the server call in this way: for example in a class of the view I've have the Utility.getFromServer () Metod that call the static getFromServer metod in the class Utility..the Utility class is linked whit the Async Class and then we've the servlet class with the query inside :) (I've the model package whit the bean in my project) this is the patterr that I've adopted...I think that is such to pattern adpoted in gtx example...do you think?! Thanks to all :) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Disabling lazy loading
You're going to have to provide a little bit more detail then that if you would like your question answered. What widgets are you using? How are you using them? -- Arthur Kalmenson On Mon, Dec 8, 2008 at 12:51 AM, sarav [EMAIL PROTECTED] wrote: How can I disable lazy loading and force components creation? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Standard/Simple GWT CSS?
Hello David and tomato,
I highly recommend you stay as far away from Ext-GWT, SmartGWT and
GWT-ext as you can. Gregor said it best, while they might look shiny,
they are as slow as molasses and a huge PITA to work with. Once you
start using them, you fall into their overly complex and inconsistent
event models, you completely forgo most of GWT since these libraries
can't work with GWT widgets, and give up the simplicity and high
quality you come to expect from GWT. I say this from experience.
--
Arthur Kalmenson
On Mon, Dec 8, 2008 at 9:38 AM, Miles T. [EMAIL PROTECTED] wrote:
Hi David and tomato,
We also didn't (and still don't) want to write HTML or CSS for our
application (it aims to be an internal application, not a public
website). Consider using Ext GWT, SmartGWT or GWT-Ext, I guess this is
what you're looking for. These libraries provide a set of widgets and
look and feels and let you define your own. They also allow you to
devlop in a Swing-style by using standard layouts (BorderLayout,
CenterLayout,...).
We choose Ext GWT because it is a full GWT library (others are
wrapping a JS library), it provides a simple MVC layer and has more
documentation.
Regards
On 8 déc, 14:34, David Hoffer [EMAIL PROTECTED] wrote:
Hi Gregor,
Thanks for the detailed response I will give this a try today.
As I read this I thought of a couple questions.
1. Does my CSS file have to have a particular name? You say it goes
next to the HTML file. Do I just name it the same but with css
extension and it will be found or do I have to reference it somehow in
my HTML/XML?
2. You mentioned to look at the showcase examples to get CSS to use.
I looked at all these yesterday and found that most do not show the
CSS used (I think most of the widgets did but most containers did
not). I then looked at the source code for showcase given in the GWT
examples and it seems they are using annotations to bring in styling
information. What's up with this? It seems there is more than one
way to apply CSS in GWT. This makes it harder to learn how one is to
do this.
As an example of what currently looks really bad...DialogBox and
VerticalSplitPanel. The former has no border so it doesn't even look
remotely like a DialogBox and VerticalSplitPanel only has a splitter
bar...no border. So unless you really know there is a split panel you
have no idea what you are looking at. For these examples the showcase
shows no CSS so apparently it is using annotations to bring in
styling. BTW, for these cases I am using the standard theme.
Thanks much, I will look at your example.
-Dave
On Sun, Dec 7, 2008 at 7:57 PM, gregor [EMAIL PROTECTED] wrote:
Hi Dave,
1) I think this might have something to do with debugging client
javascript at run time using Firebug or something - I've never used it
to be honest.
2) I happen to have a simple CSS example to hand, so this might help -
apologies if its too simplistic
Your module will have its own CSS file next to its HTML file in the
public folder.
If you check the standard theme GWT CSS for DisclosurePanel it looks
like this:
.gwt-DisclosurePanel {
}
.gwt-DisclosurePanel-open {
}
.gwt-DisclosurePanel-closed {
}
.gwt-DisclosurePanel .header,
.gwt-DisclosurePanel .header a,
.gwt-DisclosurePanel .header td {
text-decoration: none; /* Remove underline from header */
color: black;
cursor: pointer;
cursor: hand;
}
.gwt-DisclosurePanel .content {
border-left: 3px solid #e8eef7;
padding: 4px 0px 4px 8px;
margin-left: 6px;
}
Notice that it starts with gwt-DisclosurePanel - this is the primary
style name given to this widget. In the DisclosurePanel source
somewhere you will find setStylePrimaryStyleName(gwt-
DisclosurePanel). Elsewhere in the code you will find they assign the
various sub-styles to individual components of DisplosurePanel using
add/removeStyleName(styleName) or add/removeStyleDependentName
(styleSuffix) corresponding to e.g.gwt-DisclosurePanel-open and e.g.
gwt-DisclosurePanel .header respectively (or is it the other way
round, it's late). So the java code switches between the -open and -
closed styles in response to user clicks etc, but the primary style is
always the same.
(This is how to go about using CSS when you design your own composite
widgets - follow what they do)
Now you have two choices how to proceed to start with.
1) don't use a standard theme, but keep a copy of one of them (i.e.
the CSS files) handy so you can cut and paste the CSS format for each
widget into your own module CSS file where you can edit it how you
like - you just need to do each one as you need it.
2) Put inherits name='com.google.gwt.user.theme.standard.Standard'/
(or chrome/dark) in your module gwt.xml file which will activate the
theme. Now however you are stuck with what they give you - well, no,
you are not..
Notice that the
Re: Standard/Simple GWT CSS?
Hi Arther,
Your comments are well taken. Since I have heard this before we have
used pure GWT.
However, at this point however, I do think GWT missed it a bit here
because most Java programmers do not know CSS, at least not well, and
you cannot use GWT without knowing CSS. This fact, I think drives
some to these other frameworks.
I think an ideal situation would be for GWT (or someone) to create a
mechanism to get a standard LF with GWT without knowing CSS; sort of
like what you can do with Swing. Although just like Swing you should
be able to customized this LF via some mechanism and in the case of
GWT CSS is fine. It seems GWT did start to go in this direction with
the GWT themes but they aren't extensive enough.
-Dave
On Tue, Dec 9, 2008 at 7:31 AM, Arthur Kalmenson [EMAIL PROTECTED] wrote:
Hello David and tomato,
I highly recommend you stay as far away from Ext-GWT, SmartGWT and
GWT-ext as you can. Gregor said it best, while they might look shiny,
they are as slow as molasses and a huge PITA to work with. Once you
start using them, you fall into their overly complex and inconsistent
event models, you completely forgo most of GWT since these libraries
can't work with GWT widgets, and give up the simplicity and high
quality you come to expect from GWT. I say this from experience.
--
Arthur Kalmenson
On Mon, Dec 8, 2008 at 9:38 AM, Miles T. [EMAIL PROTECTED] wrote:
Hi David and tomato,
We also didn't (and still don't) want to write HTML or CSS for our
application (it aims to be an internal application, not a public
website). Consider using Ext GWT, SmartGWT or GWT-Ext, I guess this is
what you're looking for. These libraries provide a set of widgets and
look and feels and let you define your own. They also allow you to
devlop in a Swing-style by using standard layouts (BorderLayout,
CenterLayout,...).
We choose Ext GWT because it is a full GWT library (others are
wrapping a JS library), it provides a simple MVC layer and has more
documentation.
Regards
On 8 déc, 14:34, David Hoffer [EMAIL PROTECTED] wrote:
Hi Gregor,
Thanks for the detailed response I will give this a try today.
As I read this I thought of a couple questions.
1. Does my CSS file have to have a particular name? You say it goes
next to the HTML file. Do I just name it the same but with css
extension and it will be found or do I have to reference it somehow in
my HTML/XML?
2. You mentioned to look at the showcase examples to get CSS to use.
I looked at all these yesterday and found that most do not show the
CSS used (I think most of the widgets did but most containers did
not). I then looked at the source code for showcase given in the GWT
examples and it seems they are using annotations to bring in styling
information. What's up with this? It seems there is more than one
way to apply CSS in GWT. This makes it harder to learn how one is to
do this.
As an example of what currently looks really bad...DialogBox and
VerticalSplitPanel. The former has no border so it doesn't even look
remotely like a DialogBox and VerticalSplitPanel only has a splitter
bar...no border. So unless you really know there is a split panel you
have no idea what you are looking at. For these examples the showcase
shows no CSS so apparently it is using annotations to bring in
styling. BTW, for these cases I am using the standard theme.
Thanks much, I will look at your example.
-Dave
On Sun, Dec 7, 2008 at 7:57 PM, gregor [EMAIL PROTECTED] wrote:
Hi Dave,
1) I think this might have something to do with debugging client
javascript at run time using Firebug or something - I've never used it
to be honest.
2) I happen to have a simple CSS example to hand, so this might help -
apologies if its too simplistic
Your module will have its own CSS file next to its HTML file in the
public folder.
If you check the standard theme GWT CSS for DisclosurePanel it looks
like this:
.gwt-DisclosurePanel {
}
.gwt-DisclosurePanel-open {
}
.gwt-DisclosurePanel-closed {
}
.gwt-DisclosurePanel .header,
.gwt-DisclosurePanel .header a,
.gwt-DisclosurePanel .header td {
text-decoration: none; /* Remove underline from header */
color: black;
cursor: pointer;
cursor: hand;
}
.gwt-DisclosurePanel .content {
border-left: 3px solid #e8eef7;
padding: 4px 0px 4px 8px;
margin-left: 6px;
}
Notice that it starts with gwt-DisclosurePanel - this is the primary
style name given to this widget. In the DisclosurePanel source
somewhere you will find setStylePrimaryStyleName(gwt-
DisclosurePanel). Elsewhere in the code you will find they assign the
various sub-styles to individual components of DisplosurePanel using
add/removeStyleName(styleName) or add/removeStyleDependentName
(styleSuffix) corresponding to e.g.gwt-DisclosurePanel-open and e.g.
gwt-DisclosurePanel .header respectively (or is it the other way
round, it's late). So the
Re: How to share work between Java developers and HTML/CSS designers?
I fully agree with this way of working. We've been able to work with web designer with a very similar way of working. Our GWT components are very simple, and all the style is managed by CSS. I think that it's really important to keep in mind that GWT is not a Swing API in disguise :-) 2008/12/9 Nizam [EMAIL PROTECTED] After I started this thread, a new article has come up on the GWT blog which talks about how the folks at studyblue.com approached the styling issue. Here is the link to the post: http://googlewebtoolkit.blogspot.com/2008/12/gwt-no-need-to-shortchange-your-style.html On Dec 6, 10:02 am, Chii [EMAIL PROTECTED] wrote: I think the underlying issue here is that the paradym of gwt programming is not the same as the traditional web-app development, where the coder hands to the designer a bunch of variables to which the designer inserts into a template (velocity, freemarker, jsp, you name it). GWT brings to the table the developer as a UI creator. The designer no longer makes the product, but actually designs the blue-print, and that blue print is followed by the developer. I.e., the developer now needs to know about DOM, CSS and HTML (though not to the extend that a designer might). GWT tries to abstract html from making a web UI. Thats my 2 cents anyway. On Dec 3, 4:36 pm,Nizam[EMAIL PROTECTED] wrote: Are there any best practices in bringing together a multi-disciplinary team of Java developers and HTML/CSS designers in developing a commercial GWT application? Our Java guys cannot do CSS and our HTML/ CSS guys prefer working in DreamWeaver. I haven't seen any material that talks about the team collaboration aspect. Any thoughts? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Sizing
Hi,
have a problem with my CSS sizing of my GWT Elements. A Very Short
Example:
*CSS*
.codingArea{
width:100%;
height:100%;
background-color:red;
}
now i have a DialogBox with a fix Size, where i add 2 Widgets,
(ListBox and Textarea) now the Textarea should use all Space:
*GWT*
DialogBox dialog=new DialogBox();
VerticalPanel boxPanel=new VerticalPanel();
boxPanel.setSize(800px, 600px);
ListBox lbCategory=new ListBox();
TextArea taCode=new TextArea();
taCode.setStyleName(codingArea);
boxPanel.add(lbCategory);
boxPanel.add(taCode);
dialog.setWidget(boxPanel);
dialog.show();
The wanted Effect should be clear: DialogBox with 800x600px, on top a
ListBox (Space using as needed), followed by a textarea which using
all space. But in fact the Textarea using just ~70%. I have analyzed
the generated HTML Code and think i have found the Problem but no
pretty solution. The above Code ends up in a table:
tr
td align=left style=vertical-align: top;
select class=gwt-ListBox tabindex=0 title=Category
/select
/td
/tr
tr
td align=left style=vertical-align: top;
textarea class=codingArea tabindex=0 title=Code Area/
/td
/tr
here is my CSS Class bound to the textarea, and THAT is the problem,
the Textarea uses 100% of his space, but the parent Node (the TD
Element) restricted him to uses the expected Space, editing the TD
Element of the Textarea such as:
td align=left style=vertical-align: top; style=width:100%;height:
100%
textarea tabindex=0 title=Code Area class=codingArea/
/td
has the effect as expected.
Now the Question ( :) ):
How can i realize this Sizing of my Components over CSS only as i
exptect?
My hack isn't very usefull in a huge project:
Setting the Parent Cell of the Element a own Size:
boxPanel.setCellHeight(taCode, 100%);
boxPanel.setCellWidth(taCode, 100%);
Ends up in a maximzed Textarea as needed, but isnt't very pretty i
think...
thx for any idea!
D
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---
Re: Charting capabilities under GWT
Hi Joe, Wow! AmCharts looks awesome, I'll take a deep look to these Flash controls. Is it easy to integrate them under GWT application? Thanks and regards. -- Miguel Blog: http://lonifasiko.blogspot.com On 5 dic, 12:16, Joe Cole [EMAIL PROTECTED] wrote: Hi Miguel, We have successfully integrated amcharts.com into our application. It was very easy, I even think there are some examples posted in a similar thread a while ago. We tried a couple of other methods (jfreechart - image), xmlswf, openflash, gwtchart but found amcharts the best combination of interaction and look. Joe On Dec 5, 10:07 pm, Lonifasiko [EMAIL PROTECTED] wrote: Before taking the final decision of using GWT for our new web application, I wanted to know which options I have in order to generate graphs and charts inside a GWT application. In fact, these charting cappabilities are the most important part of the application for our customer, thus, it's a requisite that GWT application lets us integrate and generate good graphs. Data for these graphs would be retrieved from a MySQL database, using servlets and GWT-RPC to bypass data from server to client. The more advanced the graphs are, the better, no matter if opensource or commercial. For us would be awesome to let users somehow interact with charts at client-side, you know, effects and actions Flash graphs already do for example. Any advice around charting possibilities under GWT will be greatly appreciated. Thanks very much in advance. -- Miguel Blog:http://lonifasiko.blogspot.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Annoying issue, integrating with Hibernate
Sorry for the inaccurate info about Hibernate4Gwt, it's been a while
since I looked at it.
I would agree that depending on how you use Hibernate, the quick
solution may or may not work for you. While my objects are not always
fully populated on the server, the serialization process forces them
to populate. Also, when saving on the client side I always send back
a full graph of objects to the server. So any additions made to my
collections do show up on the server and get persisted. I admit that
deletes from a collection do not work using this approach. To get
deletes working, objects need to be marked for delete on the client
and then removed from the collection on the server after reattaching
to the session. But I think this is a common problem when working in
a detached state.
-Greg
On Dec 9, 5:29 am, noon [EMAIL PROTECTED] wrote:
Just a precision : Hibernate4Gwt/Gilead *does not* lazy load any
association from client side (it would lead to very poor
performances !!!).
It just take care of lazy but not loaded associations and persistent
collections during serialization and deserialisation process.
Another thing to know is that almost all of the above quick
solutions does not work in all cases : just try to send a partially
loaded entity on client side (= Serialization Exception) or modify a
collection in GWT code (exception or no effect on server-side)...
Regards
Bruno
On 8 déc, 23:15, Greg [EMAIL PROTECTED] wrote:
I do the same exact trick, but I convert a PersistentBag to an
ArrayList.
The tricky part is figuring out where to put your copy code so that
it doesn't get in the way or complicate your existing code. I use a
custom field serializer, which is an undocumented feature of GWT.
If you have an object, say Foo, you can customize the GWT RPC
serialization for Foo by creating a class in the same package as Foo,
called Foo_CustomFieldSerializer. Then you add two static methods to
the class as follows:
public static void serialize(SerializationStreamWriter writer, Foo
instance) throws SerializationException {
}
public static void deserialize(SerializationStreamReader reader, Foo
instance) throws SerializationException {
}
Then for every field, you call the appropriate methods in the writer
or reader to serialize or deserialize. Here's the cool part. When
you encounter a collection managed by Hibernate, you can simply swap
out the collection for a GWT safe implementation. So if Foo has a one
to many collection called bars (say it's a List), you can safely
serialize it with the following code:
public static void serialize(SerializationStreamWriter writer, Foo
instance) throws SerializationException {
...
writer.writeObject(new ArrayList(instance.getBars()));
...
}
and the deserialization is just as easy
public static void deserialize(SerializationStreamReader reader, Foo
instance) throws SerializationException {
...
instance.setBars((List)reader.readObject());
...
}
The best part about using a custom field serializer is that your
original object does not get modified. I tried an approach where I
swapped out the collection just prior to returning from my RPC
method. This caused two problems. First it complicated the code.
Second, Hibernate detected a change to my object and persisted it.
This wasn't a huge problem, but it did cause an unnecessary write to
the database.
I also looked into Hibernate4GWT. But I found that if you don't need
to do lazy loading of persistent collections on the client side, then
Hibernate4GWT is overkill.
-Greg
On Dec 8, 2:55 pm, Arthur Kalmenson [EMAIL PROTECTED] wrote:
It's also possible to force it to use a HashSet by copying the
contents of the PersistentSet to a new HashSet. That worked for us.
--
Arthur Kalmenson
On Sun, Dec 7, 2008 at 7:05 AM, gregor [EMAIL PROTECTED] wrote:
Hi,
PersistentSet is one of Hibernate's magic collections. Like the
proxies that Hibernate also uses for lazy loading, domain objects so
adorned are incompatible with the GWT Emulation library and AFAIK
there is no direct way around it at the moment. You have to copy them
to DTO representations for transfer and copy them back on return.
Hibernate4gwt does this for you - have you had a look at it?
regards
gregor
On Dec 7, 9:54 am, LoneWolf [EMAIL PROTECTED] wrote:
Hey,
Our application is using Hibernate 3 as the persistence mechanism, and
of course we have one-to-many relationship.
The problem is when trying to pass a domain object that has a list of
lazy initialized objects back to the browser, I got this exception:
Caused by: com.google.gwt.user.client.rpc.SerializationException: Type
'org.hibernate.collection.PersistentSet' was not included in the set
of types which can be serialized by this SerializationPolicy or its
Class object could
How to change tab widget in TabPanel?
How can I modify the tab widget in a TabPanel? I don't see any set methods for Widgets or tab Widgets. Do I have to remove the existing Widget just to re-add the same Widget with a different tab widget? What kind of screen flash/update will this cause? This seems like a major oversight in the TabPanel API. -Dave --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: How to change tab widget in TabPanel?
It looks like I might be able to change the tab via setTabHTML on the TabBar. There is no way to get and modify the same component that was placed in the tab bar but I might be able to set its HTML to the same effect. -Dave On Tue, Dec 9, 2008 at 8:44 AM, dhoffer [EMAIL PROTECTED] wrote: How can I modify the tab widget in a TabPanel? I don't see any set methods for Widgets or tab Widgets. Do I have to remove the existing Widget just to re-add the same Widget with a different tab widget? What kind of screen flash/update will this cause? This seems like a major oversight in the TabPanel API. -Dave --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Charting capabilities under GWT
I suggest to take a look at Google charts api. It is very fast simple and no flash plugin required . GWT integration is very easy.( Set the chart url to the Image object). http://code.google.com/apis/chart/ Regards, Srini On Dec 9, 9:34 am, Lonifasiko [EMAIL PROTECTED] wrote: Hi Joe, Wow! AmCharts looks awesome, I'll take a deep look to these Flash controls. Is it easy to integrate them under GWT application? Thanks and regards. -- Miguel Blog:http://lonifasiko.blogspot.com On 5 dic, 12:16, Joe Cole [EMAIL PROTECTED] wrote: Hi Miguel, We have successfully integrated amcharts.com into our application. It was very easy, I even think there are some examples posted in a similar thread a while ago. We tried a couple of other methods (jfreechart - image), xmlswf, openflash, gwtchart but found amcharts the best combination of interaction and look. Joe On Dec 5, 10:07 pm, Lonifasiko [EMAIL PROTECTED] wrote: Before taking the final decision of using GWT for our new web application, I wanted to know which options I have in order to generate graphs and charts inside a GWT application. In fact, these charting cappabilities are the most important part of the application for our customer, thus, it's a requisite that GWT application lets us integrate and generate good graphs. Data for these graphs would be retrieved from a MySQL database, using servlets and GWT-RPC to bypass data from server to client. The more advanced the graphs are, the better, no matter if opensource or commercial. For us would be awesome to let users somehow interact with charts at client-side, you know, effects and actions Flash graphs already do for example. Any advice around charting possibilities under GWT will be greatly appreciated. Thanks very much in advance. -- Miguel Blog:http://lonifasiko.blogspot.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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Server Side Byte Code Obfuscation
Hi, We are distributing an application. We want to obfuscate the server side code to the client so that they should not reverse engineer the code. Is it works fine? What will happend to servlets? Whether they work fine? Regards, Allahbaksh --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Server Side Byte Code Obfuscation
This is an issue for your obfuscation vendor, not GWT. My guess is it will probably work, the existing Java obfuscators I have seen usually do the right thing. But Java is so dynamic with annotations and reflection it can be really hard to obfuscate it and still have something that actually runs. Give it a try with your obfuscation vendor's tool, if it doesn't work, its probably an issue with their tool configuration. The GWT server side is just a Java servlet, nothing magical. Reflection usage is pretty typical; most tools should have switches you can use to ensure method names in your remote interfaces aren't obfuscated so the GWT RPCs can still complete normally. On Tue, Dec 9, 2008 at 08:17, Allahbaksh [EMAIL PROTECTED] wrote: Hi, We are distributing an application. We want to obfuscate the server side code to the client so that they should not reverse engineer the code. Is it works fine? What will happend to servlets? Whether they work fine? Regards, Allahbaksh --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Server Side Byte Code Obfuscation
On Tue, Dec 9, 2008 at 5:17 PM, Allahbaksh [EMAIL PROTECTED] wrote: Hi, We are distributing an application. We want to obfuscate the server side code to the client so that they should not reverse engineer the code. Is it works fine? What will happend to servlets? Whether they work fine? Regards, Allahbaksh Hi Allahbaksh, Obfuscating code is not going to stop any determined person from reverse engineering your code, it might make it slightly more difficult but that is about it. The code should still work otherwise the obfuscation failed and you simply broke your own code. In the end any and all code you write can be reversed engineered regardless of obfuscation or any other technique used to make it harder to do so. So in that respect you will have to look at the cost you make obfuscating your code as opposed to the risk you run with someone actually taking the trouble of reverse engineering your code. How much will you loose if someone reverse engineers your code in a week and how much will you loose if it takes them a month... you might very well find that the cost of hiding you code is not worth the money. Regards, Rob --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: TestBox inside CheckBox's text
Create a Composite widget with a checkbox and textbox inside it. On Dec 9, 5:45 am, Danny Schimke [EMAIL PROTECTED] wrote: I want to use a TextBox inside the CheckBox- label. For example: *[X]* Save in *TextBox* minutes I can do it by using the toString()- method on TextBox, but it is behaving incorrectly: - Firefox (un)checks the CheckBox by clicking into the TextBox - The TextBox- Object is not the TextBox which is displayed - no changes in the original TextBox. Is there a possible way to realize. Except i have to split the components... --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Capabilities of GWT interfacing with Java applets
Hello All, I'm interested in using GWT for a project, but I have some questions. I'm working on a proof of concept to try to answer them on my own, but I thought it couldn't hurt to ask the group as well. The client-side requirements for this project include two Java applets. These applets need to communicate to the UI (which will hopefully be generated by GWT). The one applet needs to receive unsolicited messages. The second applet needs to be able receive unsolicited messages AND send messages to the client/UI. From what I understand, the applets can communicate with the browser through JavaScript methods. My question then becomes, can GWT engage in two-way communications with this JavaScript method (which will in turn talk to the applet)? Where would this/these JavaScript method(s) live in the project-space? It might be helpful to know that I have used GWT on another project already, so I know a fair amount going into this one. (I'm also going to try and leverage GWT-Ext for their data grids). Thanks, ~Alfred --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Servlet autostart / load-on-startup
Hi all, I've added a basic HttpServlet in my GWT application. No problem with that, except that I want that servlet to start on the application start-up. So I've added the load-on-startup1/load-on-startup to my servlet declaration in web.xml but it has no effect in hosted mode. However, it works when I deploy the application to my WAS. Is there any way to make it work in hosted mode ? (please don't tell me to run with no-server option :) ) Thank you, Pierre --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: How to have a layered panel?
The component in the incubator is called a GlassPanel and it works
really well. Though I did have some issues with the blur event in IE,
but I could easily fix it by catching and ignoring the onBlur() call.
Suri wrote:
Hi Rakesh, Isaac Litty
Thanks for the replies. Since I'm currently already using the
incubator jar for a table, I'll first attempt Isaac's suggestion which
seems least effort-consuming at the moment. If i do need to create my
own panel, I'll try both of your suggestions and update everyone on
the results.
Thanks a bunch all. You guys are really great help in this forum.
On Dec 8, 3:11 pm, rakesh wagh [EMAIL PROTECTED] wrote:
Correction to my earlier post:
Use PopupPanel, not AbsolutePanel.
I just tried this code in a class that extends DialogBox:
@Override
public void show() {
mask.setPixelSize(Window.getClientWidth(),
Window.getClientHeight
());
mask.setPopupPosition(0, 0);
mask.setWidget(new Label(test));
mask.setStyleName(trans-bg);
mask.show();
super.hide();
super.show();
}
@Override
public void hide() {
mask.hide();
super.hide();
}
.trans-bg{
background-color: black;
filter: alpha(opacity=50);
-moz-opacity: .5;
}
And I am able to show a translucent background to any of my dialog
box!
Rakesh Wagh
On Dec 8, 9:37 am, rakesh wagh [EMAIL PROTECTED] wrote:
if you are trying to do this on your own, you will probably need a
absolute panel that is placed on the screen based on the screen size
(0, 0, max clientx, max clienty). Select a proper style: color and
transparency. Now just put your widget or popup on top of this panel.
This way the z index of your translucent panel will be between the
main screen and your visible widget.
You might also have to put a screen resize handler to resize the size
of your panel.
I think the gwt incubator has a ready to use widget.
Rakesh Wagh
On Dec 6, 11:04 pm, Suri [EMAIL PROTECTED] wrote:
Hey all,
In GWT how would we create a layered panel/widget that basically acts
like a semi-opaque screen for the stuff below it. Sort of looking like
the screen is in a disabled mode. Thanks for any ideas.
Suri
--
Petrus Pelser
Software Developer, CTO
Codewave (http://www.codewave.co.za)
mailto:[EMAIL PROTECTED]
Cell: +27 79 522 6463
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---
ScrollTable and DockPanel: ScrollTable expands CENTER panel to hide SOUTH
Hi all, I am trying to do something relatively simple: I want to create a simple, three-pane email-like item browser interface. For that I'm using a DockPanel to host the components, namely queries, result list and single item viewer. The queries go in the WEST panel, the result list goes in the CENTRE panel, and the single item viewer goes in the SOUTH panel. When I use a simple Grid wrapped in a ScrollPanel for test, this works as expected. The result list fills up about half of the height of the screen and grows a scrollbar. However, when I replace the Grid/ ScrollPanel combination with a ScrollTable from the Incubator projects, the ScrollTable fills up the entire height of the screen, rather than confining itself to about half the screen like the Grid/ ScrollPanel did. Any ideas? Sincerely, Anders S. Johansen, ange.dk --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
PopupPanel over pdf bug in Firefox
I have a PopupPanel that is supposed to appear above a Frame (e.g. iframe). It normally works, but if the iframe contains a pdf (or presumably, anything the uses a plugin...flash, java, etc) then the PopupPanel gets buried. I can fix it in DHTML by using an iframe shim, but it is turning out to be a bit difficult in GWT because the shim must be absolutely positioned. How can I work around this? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Can't solve warnings
Hi, first of all sorry for my English and sorry if I wrote this post in wrong place. I have a problem. I wrote this code: ... Vector vector = new Vector(); HashMap map = new HashMap(); ... This code has these warnings: Vector is a raw type. References to generic type VectorE should be parameterized HashMap is a raw type. References to generic type HashMapK,V should be parameterized If I declare parametrized type: ... VectorString vector = new VectorString(); or VectorObject vector = new VectorObject(); I get runtime errors: The type Vector is not generic; it cannot be parameterized with arguments String GWT does not yet support the Java 5.0 language enhancements; only 1.4 compatible source may be used I'm using jdk 1.5 and gwt 1.4.6 Can anybody help me to solve these warnings? Thank you --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Servlet autostart / load-on-startup
Hi Pierre,
Funnily enough I've just met a similar problem - a start up serlvet
that fires up a number of server resources, but I cannot start it in
hosted mode because you can't doctor the embedded Tomcat web.xml. I
hacked around this by sticking an init() in one of my early call
servlets that checks if things have been set up (which they will have
been if deployed) and if not kicks off the start up procedures.
Having thought about it a more satisfactory approach might be to use
an if (!GWT.isScript()) {}; statement at the head of onModuleLoad()
that called a simple RPC service that booted the start up procedures
for hosted mode, but would be ignored in production.
regards
gregor
On Dec 9, 5:06 pm, Pierre Lavignotte [EMAIL PROTECTED]
wrote:
Hi all,
I've added a basic HttpServlet in my GWT application.
No problem with that, except that I want that servlet to start on the
application start-up.
So I've added the load-on-startup1/load-on-startup to my servlet
declaration in web.xml but it has no effect in hosted mode.
However, it works when I deploy the application to my WAS.
Is there any way to make it work in hosted mode ?
(please don't tell me to run with no-server option :) )
Thank you,
Pierre
--~--~-~--~~~---~--~~
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 [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~--~~~~--~~--~--~---
Re: Suggestions with code design
Everyone, Thank you very much for the inputs. On Mon, Dec 8, 2008 at 3:42 PM, Thomas Broyer [EMAIL PROTECTED] wrote: On 7 déc, 05:54, Rohan Redkar [EMAIL PROTECTED] wrote: Hi everyone, My application requires the user to select a bunch of images from his system. Then I need to do modifications on these images(example aline them horizontally into a single image). I need some design suggestions on how I can achieve this? Yahoo! BrowserPlus? (or Flash, or a Java applet, or Sliverlight) I guess, AWT cannot be directly used at the client side code. So if I am transfering these images to the server to do these operations, can I use rpc or will I run into Serialization issues? Is upload via the normal multipart request the only option in this case? Yes (or a Flash/etc. helper, eventually, but definitely not GWT-RPC) -- Rohan Redkar MSCS, New York University Email: [EMAIL PROTECTED] --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Java Developer Opportunity in Atlanta using GWT!
Hi Everyone! Thanks for taking the time to read this post! A cutting-edge technology company in the hospitality industry is searching for a Java developer who has experience with Google Web Toolkit. Please see more information below. If you or someone you know if interested in this opportunity, please send a Word copy of your resume to [EMAIL PROTECTED] I look forward to hearing from you! ~Janna Tucker Technical Recruiter Synergis 770-346-7226 Title: Java Developer Location: Atlanta, GA (Dunwoody/Perimeter area) Type: Six month contract This individual will be part of a team that is creating trend-setting applications for a well recognized company based in Atlanta. Requirements: -3-5 years of Java/J2EE development experience -Experience with Java server side development and Google Web Tool Kit customization. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWTShell and facelet.
Hi Olivier, The hosted mode embedded Tomcat server isn't configured with a JSF servlet out of the box, and hence wouldn't be able to handle the *.faces mapping. Are you using hosted mode with the embedded Tomcat server, or with your own server using the -noserver option? If it's the former, you should run hosted mode with the -noserver option and use the same server that you use when you work in web mode. Here's an FAQ on how to setup hosted mode with the -noserver option: http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5s=google-web-toolkit-doc-1-5t=FAQ_HostedModeNoServer -alex On Dec 9, 3:25 am, olivier FRESSE [EMAIL PROTECTED] wrote: Hmm no, I have a script/script tag. I'm still digging :-) O. 2008/12/9 Sumit Chandel [EMAIL PROTECTED] Hi Olivier, Can you double-check to make sure that you're not using an empty script tag to reference your GWT bootstrap script? I..e, script src=com.google.app.MyModule.nocache.js / versus script src=com.google.app.MyModule.nocache.js/script? The empty script tag has been known to cause issues in hosted mode, and is also known to cause problems in IE 6/7 if I remember correctly. Hope that helps, -Sumit Chandel On Fri, Dec 5, 2008 at 3:05 AM, olivier [EMAIL PROTECTED] wrote: Hi, I'm facing a strange issue. I'm using GWT within a facelet page. This means that I have the following URL http://myserver:8080/MyApp/conf/test.faces test.faces is resolved to test.xtml by the servlet. Compiled mode works fine. But in hosted mode, the module is not loaded. No errors, no traces, nothing. However, the static HTML is displayed ! I tried the verbose mode, but it didn't help. Any clue ? :-) --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Standard/Simple GWT CSS?
Hi Jeremy, I can't speak for Arthur, but I also interject occasionally on the Ext issue (usually with the rider that I tried MyGWT for only a short while and walked away from it after I realized what was going on). The reason is simply this: many people just post links on this group to Ext family demos, and for the unwary one look at those beautifully designed desktop emulation widgets will turn their heads before they have an inclination of what the consequences are, or the alternatives approaches. So the issue is one of balance. No one argues Ext widgets don't look very pretty or that you don't get this look out of the box lickerty spit compared with straight GWT - the point is there is a price to pay (and I don't mean license $'s), and people need to know about that. For some the price maybe worth worth paying, for others maybe not, but everyone should understand the nature of the trade off so they can make informed decisions for their own situations. I certainly don't want to criticize you for choosing to use Ext, I only have one bugbear with you post: the use of the word rich. What do you mean by rich and highly dynamic widgets? Are you suggesting, for example, that there is something you can do with the Ext family's data grid that you cannot do with PagingScrollTable? regards gregor On Dec 9, 5:10 pm, Jeremy Cohen [EMAIL PROTECTED] wrote: Arthur,I see that you jump into all threads involving third party libraries and tell users how bad they are. I'm not even sure you've used them enough to make an informed decision. There is after all a learning curve involved in learning any third party library and their API's. You do realize that these third party libraries provide rich any highly dynamic widgets that are required by many real world applications. With increased functionality comes increased size. Are you saying that your application only uses the widgets available in GWT core and the incubator project? If so, I doubt it will come anywhere close to the functionality delivered to users by any of these third party libraries. Remember, what ultimately counts functionality delivered to the end user and not whether the developer of the application used only widgets in GWT, or third party libraries. Or whether they use Spring / ORM library, or core JDK / JDBC API's. Does your application provide a rich grid widget? Or are you building inhouse custom components? (if so, please do share). From an end users perspective what makes it any better than the ones already available. I'm sure you're a real smart guy, but it would be great if you put your money where your mouth is and allow users to see the application you have been working on, the complexity of the application, along with detail on number of developers, and duration of project. We can then draw a comparison between the two approaches. Cheers, -Jeremy On Tue, Dec 9, 2008 at 9:31 AM, Arthur Kalmenson [EMAIL PROTECTED]wrote: Hello David and tomato, I highly recommend you stay as far away from Ext-GWT, SmartGWT and GWT-ext as you can. Gregor said it best, while they might look shiny, they are as slow as molasses and a huge PITA to work with. Once you start using them, you fall into their overly complex and inconsistent event models, you completely forgo most of GWT since these libraries can't work with GWT widgets, and give up the simplicity and high quality you come to expect from GWT. I say this from experience. -- Arthur Kalmenson On Mon, Dec 8, 2008 at 9:38 AM, Miles T. [EMAIL PROTECTED] wrote: Hi David and tomato, We also didn't (and still don't) want to write HTML or CSS for our application (it aims to be an internal application, not a public website). Consider using Ext GWT, SmartGWT or GWT-Ext, I guess this is what you're looking for. These libraries provide a set of widgets and look and feels and let you define your own. They also allow you to devlop in a Swing-style by using standard layouts (BorderLayout, CenterLayout,...). We choose Ext GWT because it is a full GWT library (others are wrapping a JS library), it provides a simple MVC layer and has more documentation. Regards On 8 déc, 14:34, David Hoffer [EMAIL PROTECTED] wrote: Hi Gregor, Thanks for the detailed response I will give this a try today. As I read this I thought of a couple questions. 1. Does my CSS file have to have a particular name? You say it goes next to the HTML file. Do I just name it the same but with css extension and it will be found or do I have to reference it somehow in my HTML/XML? 2. You mentioned to look at the showcase examples to get CSS to use. I looked at all these yesterday and found that most do not show the CSS used (I think most of the widgets did but most containers did not). I then looked at the source code for showcase given in the GWT examples and it seems they are using annotations to bring in
Re: Can't solve warnings
Either upgrade to GWT 1.5 (which does support Java 1.5 syntax) or downgrade to Java 1.4. On Tue, Dec 9, 2008 at 6:59 AM, MMM [EMAIL PROTECTED] wrote: Hi, first of all sorry for my English and sorry if I wrote this post in wrong place. I have a problem. I wrote this code: ... Vector vector = new Vector(); HashMap map = new HashMap(); ... This code has these warnings: Vector is a raw type. References to generic type VectorE should be parameterized HashMap is a raw type. References to generic type HashMapK,V should be parameterized If I declare parametrized type: ... VectorString vector = new VectorString(); or VectorObject vector = new VectorObject(); I get runtime errors: The type Vector is not generic; it cannot be parameterized with arguments String GWT does not yet support the Java 5.0 language enhancements; only 1.4 compatible source may be used I'm using jdk 1.5 and gwt 1.4.6 Can anybody help me to solve these warnings? Thank you --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: How to change tab widget in TabPanel?
Hi David, You cannot easily get at the widget you used for a tab header. TabBar.getTabHTML() doesn't work if you loaded a widget into a tab header. I am not sure why this is, i.e. why this is so difficult in the case of TabPanel. A solution is to accept that if you need more than CSS to drive your tab header behaviour, then you probably need to extend TabPanel. If you need to go to that trouble then you can also easily keep a Map of the widgets you load into the TabBar headers and manipulate (or replace) them as required as tabs are selected (via the event system). regards gregor On Dec 9, 3:59 pm, David Hoffer [EMAIL PROTECTED] wrote: It looks like I might be able to change the tab via setTabHTML on the TabBar. There is no way to get and modify the same component that was placed in the tab bar but I might be able to set its HTML to the same effect. -Dave On Tue, Dec 9, 2008 at 8:44 AM, dhoffer [EMAIL PROTECTED] wrote: How can I modify the tab widget in a TabPanel? I don't see any set methods for Widgets or tab Widgets. Do I have to remove the existing Widget just to re-add the same Widget with a different tab widget? What kind of screen flash/update will this cause? This seems like a major oversight in the TabPanel API. -Dave --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Standard/Simple GWT CSS?
Hi gregor,I agree with your post and we have also stopped use of the extJS family of products. Fortunately it was still a proof-of-concept phase. We had to make a different technology choice due to timelines and various technical and strategic reasons. However I really like GWT and the fact that programming is in Java. As you mention users should understand the consequences and alternatives. Dismissing third party libraries categorically and making it sound like stying is a breeze and the current GWT widgets are all that a user might need is also not quite right. For some users having polished and feature rich widgets without extra styling effort might be more important than the extra initial download time since size is not of much consequence in an intranet application. It would be an interesting stat to see what percentage of users are building GWT applications for intranet vs. internet applications. We pretty much hear about most GWT internet based sites from ongwt or gwtsite but based on the GWT userbase I would imagine that a majority of GWT applications are intranet applications. I'm not going to try to sell any third party library, but some do provide rich capabilities like grouping, custom formatting like expandable rows that are not simple to accomplish out-of-the-box with GWT. (at least when I last looked) . Cheers, -Jeremy On Tue, Dec 9, 2008 at 3:07 PM, gregor [EMAIL PROTECTED] wrote: Hi Jeremy, I can't speak for Arthur, but I also interject occasionally on the Ext issue (usually with the rider that I tried MyGWT for only a short while and walked away from it after I realized what was going on). The reason is simply this: many people just post links on this group to Ext family demos, and for the unwary one look at those beautifully designed desktop emulation widgets will turn their heads before they have an inclination of what the consequences are, or the alternatives approaches. So the issue is one of balance. No one argues Ext widgets don't look very pretty or that you don't get this look out of the box lickerty spit compared with straight GWT - the point is there is a price to pay (and I don't mean license $'s), and people need to know about that. For some the price maybe worth worth paying, for others maybe not, but everyone should understand the nature of the trade off so they can make informed decisions for their own situations. I certainly don't want to criticize you for choosing to use Ext, I only have one bugbear with you post: the use of the word rich. What do you mean by rich and highly dynamic widgets? Are you suggesting, for example, that there is something you can do with the Ext family's data grid that you cannot do with PagingScrollTable? regards gregor On Dec 9, 5:10 pm, Jeremy Cohen [EMAIL PROTECTED] wrote: Arthur,I see that you jump into all threads involving third party libraries and tell users how bad they are. I'm not even sure you've used them enough to make an informed decision. There is after all a learning curve involved in learning any third party library and their API's. You do realize that these third party libraries provide rich any highly dynamic widgets that are required by many real world applications. With increased functionality comes increased size. Are you saying that your application only uses the widgets available in GWT core and the incubator project? If so, I doubt it will come anywhere close to the functionality delivered to users by any of these third party libraries. Remember, what ultimately counts functionality delivered to the end user and not whether the developer of the application used only widgets in GWT, or third party libraries. Or whether they use Spring / ORM library, or core JDK / JDBC API's. Does your application provide a rich grid widget? Or are you building inhouse custom components? (if so, please do share). From an end users perspective what makes it any better than the ones already available. I'm sure you're a real smart guy, but it would be great if you put your money where your mouth is and allow users to see the application you have been working on, the complexity of the application, along with detail on number of developers, and duration of project. We can then draw a comparison between the two approaches. Cheers, -Jeremy On Tue, Dec 9, 2008 at 9:31 AM, Arthur Kalmenson [EMAIL PROTECTED] wrote: Hello David and tomato, I highly recommend you stay as far away from Ext-GWT, SmartGWT and GWT-ext as you can. Gregor said it best, while they might look shiny, they are as slow as molasses and a huge PITA to work with. Once you start using them, you fall into their overly complex and inconsistent event models, you completely forgo most of GWT since these libraries can't work with GWT widgets, and give up the simplicity and high quality you come to expect from GWT. I say this from experience. --
GWT 1.5.3 with Eclipse
Hi, After a session at Devoxx, Antwerp, i got interested in GWT. I'm using Eclipse-IDE for java and web programming, so i'm searching for an eclipse-plug-in to test GWT with this current IDE. Who can give my a link for such? Any good starting points? Manuals / turorials? 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
why DOM.eventGetCurrentEvent().getButton() always returns 1 during MouseMove on FireFox?
Hello, Does anybody know why DOM.eventGetCurrentEvent().getButton() always returns 1 during MouseMove on FireFox. Works fine on IE. Regards Vitaliy --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: PagingScrollTable + how to sort locally
On Dec 5, 8:38 am, Suri [EMAIL PROTECTED] wrote: Hi Pohl, Thanks for the idea. I figured there could be a way around it maybe, but from what I read about the gen2PagingScrollTablefrom the incubator's synopsis, it seemed like they mentioned the sorting can be done locally as well Actually, everything that I suggested was an effort to figure out how to sort locally. I assume that locally means on the client side, which is where your TableModel lives. The more I think about it, the more it seems like this is exactly what the incubator synopsis means by sorting locally. I believe they expect you to interrogate the ColumnSortList and sort it differently for each case. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Capabilities of GWT interfacing with Java applets
The information looks to be all there! I was able to successfully experiment a bit with it. Thanks! ~Alfred On Dec 9, 12:45 pm, Shawn Pearce [EMAIL PROTECTED] wrote: To answer your question, yes. Look at JSNI and JavaScriptObject in the GWT documentation: http://code.google.com/docreader/#p=google-web-toolkit-doc-1-5s=goog... On Tue, Dec 9, 2008 at 09:37, Alfred S [EMAIL PROTECTED] wrote: Hello All, I'm interested in using GWT for a project, but I have some questions. I'm working on a proof of concept to try to answer them on my own, but I thought it couldn't hurt to ask the group as well. The client-side requirements for this project include two Java applets. These applets need to communicate to the UI (which will hopefully be generated by GWT). The one applet needs to receive unsolicited messages. The second applet needs to be able receive unsolicited messages AND send messages to the client/UI. From what I understand, the applets can communicate with the browser through JavaScript methods. My question then becomes, can GWT engage in two-way communications with this JavaScript method (which will in turn talk to the applet)? Where would this/these JavaScript method(s) live in the project-space? It might be helpful to know that I have used GWT on another project already, so I know a fair amount going into this one. (I'm also going to try and leverage GWT-Ext for their data grids). Thanks, ~Alfred --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: How to change tab widget in TabPanel?
Yeah, extending TabPanel seems like a good way to go as I have dynamic tab content. -Dave On Tue, Dec 9, 2008 at 1:43 PM, gregor [EMAIL PROTECTED] wrote: Hi David, You cannot easily get at the widget you used for a tab header. TabBar.getTabHTML() doesn't work if you loaded a widget into a tab header. I am not sure why this is, i.e. why this is so difficult in the case of TabPanel. A solution is to accept that if you need more than CSS to drive your tab header behaviour, then you probably need to extend TabPanel. If you need to go to that trouble then you can also easily keep a Map of the widgets you load into the TabBar headers and manipulate (or replace) them as required as tabs are selected (via the event system). regards gregor On Dec 9, 3:59 pm, David Hoffer [EMAIL PROTECTED] wrote: It looks like I might be able to change the tab via setTabHTML on the TabBar. There is no way to get and modify the same component that was placed in the tab bar but I might be able to set its HTML to the same effect. -Dave On Tue, Dec 9, 2008 at 8:44 AM, dhoffer [EMAIL PROTECTED] wrote: How can I modify the tab widget in a TabPanel? I don't see any set methods for Widgets or tab Widgets. Do I have to remove the existing Widget just to re-add the same Widget with a different tab widget? What kind of screen flash/update will this cause? This seems like a major oversight in the TabPanel API. -Dave --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.5.3 with Eclipse
You don't really need a plugin. The getting started guide (it's right there on the main GWT website) shows how to run the projectCreator/applicationCreator scripts. These already generate the .project file that eclipse needs (make sure you follow the 'I have eclipse' part of the getting started guide). What would you envision a plugin to even do? On Dec 9, 10:01 pm, Patrick Goovaerts [EMAIL PROTECTED] wrote: BTW, i am using Eclipse v3.2.2 2008/12/9 pgoovaerts [EMAIL PROTECTED] Hi, After a session at Devoxx, Antwerp, i got interested in GWT. I'm using Eclipse-IDE for java and web programming, so i'm searching for an eclipse-plug-in to test GWT with this current IDE. Who can give my a link for such? Any good starting points? Manuals / turorials? 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.5.3 with Eclipse
Check out Instantiations GWT Designer www.instantiations.com An excellent product and a great value. If $60USD is too much, check out http://code.google.com/p/cypal-studio/ Cypal Studio does a lot of work for you, but is missing the visual development tools that GWT Designer has. For tutorials: http://code.google.com/webtoolkit/ http://examples.roughian.com/#Home For books: http://www.amazon.com/s/ref=nb_ss_gw?url=search-alias%3Dapsfield-keywords=gwt All of these books are terrific, I own them all. Later, Shaffer On Dec 9, 2:01 pm, Patrick Goovaerts [EMAIL PROTECTED] wrote: BTW, i am using Eclipse v3.2.2 2008/12/9 pgoovaerts [EMAIL PROTECTED] Hi, After a session at Devoxx, Antwerp, i got interested in GWT. I'm using Eclipse-IDE for java and web programming, so i'm searching for an eclipse-plug-in to test GWT with this current IDE. Who can give my a link for such? Any good starting points? Manuals / turorials? thanks.- Hide quoted text - - Show quoted text - --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: XML and SOP
Thanks for the clear explanation and the direction. I have started
implementing the situation in the manner you described (I think), but
am running into another problem. The procedure below is the server
side of a GWT RPC. The line
Method method = RequestBuilder.GET;
raises the following Error:
ERROR: GWT.create() is only usable in client code! It cannot be
called, for example, from server code. If you are running a unit
test, check that your test case extends GWTTestCase and that GWT.create
() is not called from within an initializer or constructor.
Any further assistance anyone could give me would be greatly
appreciated.
Thanks, Ryan
public WeatherReport getWeatherReport(Integer zipCode) throws
Exception {
String url = http://www.google.com/ig/api?weather=; +
zipCode.toString();
try {
Method method = RequestBuilder.GET;
RequestBuilder builder = new RequestBuilder(method,
URL.encode
(url));
try {
builder.sendRequest(null, new RequestCallback(){
public void onError(Request request,
Throwable exception) {
//handle error
}
public void onResponseReceived(Request
request, Response
response) {
//handle response
}
});
} catch (RequestException e){
String msg = e.getMessage();
//handle Exception
}
} catch (Throwable t){
String msg = t.getMessage();
//handle Throwable
}
return new WeatherReport();
}
On Dec 8, 11:23 pm, Adam T [EMAIL PROTECTED] wrote:
This technique only works for JSON that is returned as a valid
JavaScript function, it will not work for XML. It relies on the fact
that the returned JavaScript expression is evaluated by the browser
and thus your handle function is called. Without that, your handle
function can never be called with a JavaScriptObject that contains
data.
Normally you can get Google APIs as JSON by adding alt=json as a
parameter to the call, but it doesn't seem to work for the weather.
To handle only XML you will have to go through a proxy server, i.e.
your application makes a call to your server, your server makes a call
to weather service and the returned data is fed back to your
application by your server.
For completeness, you get null because that is exactly what your
code is telling it to send. As you are not getting a valid JSON
string wraped in JavaScript function then the browser never gets to
call your handle function with data, and you will always execute the
code in the timeout section. That code in the timeout section always
make this call:
[EMAIL PROTECTED]::handleXmlResponse
(Lcom/google/gwt/core/client/JavaScriptObject;Lfarmapp/client/weather/
WeatherReportCallback;)(null, reportCallback);
where the first parameter is null, and hence your handle function is
always trying to handle null.
Hope that goes someway to helping/explaining!
//Adam
9 Dec, 05:55, Ryan [EMAIL PROTECTED] wrote:
Hello,
I am trying to access an XML feed via a URL request of an external
server, but of course am restricted by the browser SOP. So I tried to
follow the example given in the Getting Started guide for getting
around SOP on a JSON request, Get JSON via HTTP, hoping to adapt it
for XML. But it's not working. The JSNI procedure getXml will return
to handleXmlResponse, as it is supposed to, but the JavaScriptObject
param xml is always null. It seems as though the request is timing
out, as increasing the timeout delay in the JSNI procedure seems to
have an effect. I have increased it all the way to 30 seconds hoping
for a response, but it's just not coming.
Obviously the procedure for XML is different enough that I need
further modifications. Can anyone help me out? Thanks!
Ryan
**
packagefarmapp.client.weather;
import com.google.gwt.core.client.JavaScriptObject;
import com.google.gwt.http.client.URL;
import com.google.gwt.user.client.Window;
import com.google.gwt.xml.client.Document;
import com.google.gwt.xml.client.XMLParser;
public class WeatherService {
private int xmlRequestId = 0;
public void getReport(final Integer zipCode, final
WeatherReportCallback reportCallback){
String url =
URL.encode(http://www.google.com/ig/api?weather=;) +
zipCode.toString() + callback=;
getXml(xmlRequestId++, url, this, reportCallback);
}
public
Advise for reimplementing a Struts JSP application in GWT
Hello, I have dabbled with GWT and understand how to build UIs and use the Ajax features and RPC mechanism. I seek advise from you about the following How should I go about if I were to reimplement an existing Struts, JSP and handwritten Ajax web application in GWT? The current application has 1) many screens, 2) user role based privileges that decide if a page is visible, if buttons can be clicked, if a menu option is available, etc. 3) uses Hibernate and some Spring (for logging) on the server side. 4) uses struts tiles for layout. I understand that the layout will have to be a complete rewrite using the GWT methodology of creating widgets and pages. Before I can embark on creating a prototype for evaluating if its the right thing to do by adopting GWT, I wanted your advise and inputs. Thanks, Sunit --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: XML and SOP
Nevermind - I discovered that I can make the request the
java.net.HttpURLConnection class...
Thanks again for the help...
On Dec 9, 4:09 pm, Ryan [EMAIL PROTECTED] wrote:
Thanks for the clear explanation and the direction. I have started
implementing the situation in the manner you described (I think), but
am running into another problem. The procedure below is the server
side of a GWT RPC. The line
Method method = RequestBuilder.GET;
raises the following Error:
ERROR: GWT.create() is only usable in client code! It cannot be
called, for example, from server code. If you are running a unit
test, check that your test case extends GWTTestCase and that GWT.create
() is not called from within an initializer or constructor.
Any further assistance anyone could give me would be greatly
appreciated.
Thanks, Ryan
public WeatherReport getWeatherReport(Integer zipCode) throws
Exception {
String url = http://www.google.com/ig/api?weather=; +
zipCode.toString();
try {
Method method = RequestBuilder.GET;
RequestBuilder builder = new RequestBuilder(method,
URL.encode
(url));
try {
builder.sendRequest(null, new
RequestCallback(){
public void onError(Request request,
Throwable exception) {
//handle error
}
public void
onResponseReceived(Request request, Response
response) {
//handle response
}
});
} catch (RequestException e){
String msg = e.getMessage();
//handle Exception
}
} catch (Throwable t){
String msg = t.getMessage();
//handle Throwable
}
return new WeatherReport();
}
On Dec 8, 11:23 pm, Adam T [EMAIL PROTECTED] wrote:
This technique only works for JSON that is returned as a valid
JavaScript function, it will not work for XML. It relies on the fact
that the returned JavaScript expression is evaluated by the browser
and thus your handle function is called. Without that, your handle
function can never be called with a JavaScriptObject that contains
data.
Normally you can get Google APIs as JSON by adding alt=json as a
parameter to the call, but it doesn't seem to work for the weather.
To handle only XML you will have to go through a proxy server, i.e.
your application makes a call to your server, your server makes a call
to weather service and the returned data is fed back to your
application by your server.
For completeness, you get null because that is exactly what your
code is telling it to send. As you are not getting a valid JSON
string wraped in JavaScript function then the browser never gets to
call your handle function with data, and you will always execute the
code in the timeout section. That code in the timeout section always
make this call:
[EMAIL PROTECTED]::handleXmlResponse
(Lcom/google/gwt/core/client/JavaScriptObject;Lfarmapp/client/weather/
WeatherReportCallback;)(null, reportCallback);
where the first parameter is null, and hence your handle function is
always trying to handle null.
Hope that goes someway to helping/explaining!
//Adam
9 Dec, 05:55, Ryan [EMAIL PROTECTED] wrote:
Hello,
I am trying to access an XML feed via a URL request of an external
server, but of course am restricted by the browser SOP. So I tried to
follow the example given in the Getting Started guide for getting
around SOP on a JSON request, Get JSON via HTTP, hoping to adapt it
for XML. But it's not working. The JSNI procedure getXml will return
to handleXmlResponse, as it is supposed to, but the JavaScriptObject
param xml is always null. It seems as though the request is timing
out, as increasing the timeout delay in the JSNI procedure seems to
have an effect. I have increased it all the way to 30 seconds hoping
for a response, but it's just not coming.
Obviously the procedure for XML is different enough that I need
further modifications. Can anyone help me out? Thanks!
Ryan
**
packagefarmapp.client.weather;
import com.google.gwt.core.client.JavaScriptObject;
import com.google.gwt.http.client.URL;
import com.google.gwt.user.client.Window;
import com.google.gwt.xml.client.Document;
import com.google.gwt.xml.client.XMLParser;
public class WeatherService {
private int xmlRequestId = 0;
public void getReport(final Integer zipCode,
Re: PopupPanel over pdf bug in Firefox
Hi, i've had the same problem with another toolkit. After some research i got to the conclusion that this was due to how the browser (adobe plugin) renders the pdf. Changing the z-index does not work. One way to work around this is simply to let add a listener to the pdf containing element, and hiding it when you open the menu. For example: (not done with gwt tho) http://nsm.raunvis.hi.is/~olympic/Trainer/train.html Good luck, although i googled alot on this when i had this problem and found no other solution. NB: if you use flash plugin, it's not the same problem because then you can control the rendering of the plugin with the wmode attribute. (if i remember correctly) best regards, Eiríkur On Dec 9, 5:29 pm, ka1n [EMAIL PROTECTED] wrote: I have a PopupPanel that is supposed to appear above a Frame (e.g. iframe). It normally works, but if the iframe contains a pdf (or presumably, anything the uses a plugin...flash, java, etc) then the PopupPanel gets buried. I can fix it in DHTML by using an iframe shim, but it is turning out to be a bit difficult in GWT because the shim must be absolutely positioned. How can I work around this? --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
How to put focus on a cell of an editable grid if a particular even occurs
I have an editable grid. I want to put focus on it if an even occurs. Please suggest something. --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: GWT 1.5.3 with Eclipse
with the maven archetype you can import a project in two steps... = http://gwt-maven.googlecode.com/svn/docs/maven-googlewebtoolkit2-plugin/archetype.html = mvn archetype:create -DarchetypeGroupId=com.totsp.gwt \ -DarchetypeArtifactId=maven-googlewebtoolkit2-archetype \ -DarchetypeVersion=1.0.3 \ -DremoteRepositories=http://gwt-maven.googlecode.com/svn/trunk/mavenrepo \ -DgroupId=myGroupId \ -DartifactId=myArtifactId = ./projectCreator -eclipse myArtifactId -out myArtifactId = i'm using eclipse 3.4.1 with maven integration for my builds and dependency management, any ant projects are just wrapped... cheers paul On 12/09/2008 03:47 PM, pgoovaerts wrote: Hi, After a session at Devoxx, Antwerp, i got interested in GWT. I'm using Eclipse-IDE for java and web programming, so i'm searching for an eclipse-plug-in to test GWT with this current IDE. Who can give my a link for such? Any good starting points? Manuals / turorials? 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Native GWT Compiler
Does anyone know the answer to this question asked by Dobes: I checked out the trunk and I'm running thecompilerfrom it, but I'm not seeing any performance boost and only one CPU core is being used. Is there a command-line switch to turn on multiple threads? That's why I was reluctant spending at least an hour trying this myself - I didn't believe it would actually be enabled by default. On Nov 24, 7:29 am, Dobes [EMAIL PROTECTED] wrote: I checked out the trunk and I'm running thecompilerfrom it, but I'm not seeing any performance boost and only one CPU core is being used. Is there a command-line switch to turn on multiple threads? On Nov 12, 10:56 am, Alex Epshteyn [EMAIL PROTECTED] wrote: Hi Sumit, This multithreadedcompilersounds intriguing. Could you provide some guidance about how to get it and use it? Thanks, Alex On Oct 13, 1:08 pm, Sumit Chandel [EMAIL PROTECTED] wrote: Hi Rauf, There are currently no plans to rewrite the GWTcompileras a native compiler. There are plans to speedup compilation time with the current GWT compiler, however, and the team is in the know about long compilation times that some developers have been experiencing when moving their projects form 1.4.x to 1.5. The new multi-threadedcompileris available in trunk if you're interested in checking it out to see if it helps speed up your application compile time. From benchmarks we've run and what some developers have been reporting, the new multi-threaded compilation has been showing significant improvements in compilation speed, so you should be getting faster results for your own project as well. Hope that helps, -Sumit Chandel On Wed, Oct 8, 2008 at 2:36 PM, Rauf Issa [EMAIL PROTECTED] wrote: Any plans to write a native GWTCompilerlike jikes for java? I know there are plans to improve GWTcompilerperformance in the upcoming 1.6 release of GWT by multi-threading but I am not sure that will make enough difference. A nativecompilerlike jikes would be better and much faster. Our product, JobServer (job scheduling engine) uses GWT for its GUI SDK and we compile GWT components on the fly the first time the GWT is used. This frees the developer from doing the GWTcompilerif they do not want to. This works very well but the initial GWT compiling of the GWT UI components can take minutes sometimes and is annoying. I would really like this to be more like compiling JSP pages for example. Anyway I can only hope that GWT compiling gets faster (right now it is getting slower with all the advanced optimizations done in GWT 1.5 :) Rauf Issa http://www.grandlogic.com JobServer - The Most Comprehensive Java Job Scheduling Platform --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
Re: Multithreaded GWT Compiler
(Just changing the title of this thread to match actual discussion subject). On Dec 10, 2:50 am, Alex Epshteyn [EMAIL PROTECTED] wrote: Does anyone know the answer to this question asked by Dobes: I checked out the trunk and I'm running thecompilerfrom it, but I'm not seeing any performance boost and only one CPU core is being used. Is there a command-line switch to turn on multiple threads? That's why I was reluctant spending at least an hour trying this myself - I didn't believe it would actually be enabled by default. On Nov 24, 7:29 am, Dobes [EMAIL PROTECTED] wrote: I checked out the trunk and I'm running thecompilerfrom it, but I'm not seeing any performance boost and only one CPU core is being used. Is there a command-line switch to turn on multiple threads? On Nov 12, 10:56 am, Alex Epshteyn [EMAIL PROTECTED] wrote: Hi Sumit, This multithreadedcompilersounds intriguing. Could you provide some guidance about how to get it and use it? Thanks, Alex On Oct 13, 1:08 pm, Sumit Chandel [EMAIL PROTECTED] wrote: Hi Rauf, There are currently no plans to rewrite the GWTcompileras a native compiler. There are plans to speedup compilation time with the current GWT compiler, however, and the team is in the know about long compilation times that some developers have been experiencing when moving their projects form 1.4.x to 1.5. The new multi-threadedcompileris available in trunk if you're interested in checking it out to see if it helps speed up your application compile time. From benchmarks we've run and what some developers have been reporting, the new multi-threaded compilation has been showing significant improvements in compilation speed, so you should be getting faster results for your own project as well. Hope that helps, -Sumit Chandel On Wed, Oct 8, 2008 at 2:36 PM, Rauf Issa [EMAIL PROTECTED] wrote: Any plans to write a native GWTCompilerlike jikes for java? I know there are plans to improve GWTcompilerperformance in the upcoming 1.6 release of GWT by multi-threading but I am not sure that will make enough difference. A nativecompilerlike jikes would be better and much faster. Our product, JobServer (job scheduling engine) uses GWT for its GUI SDK and we compile GWT components on the fly the first time the GWT is used. This frees the developer from doing the GWTcompilerif they do not want to. This works very well but the initial GWT compiling of the GWT UI components can take minutes sometimes and is annoying. I would really like this to be more like compiling JSP pages for example. Anyway I can only hope that GWT compiling gets faster (right now it is getting slower with all the advanced optimizations done in GWT 1.5 :) Rauf Issa http://www.grandlogic.com JobServer - The Most Comprehensive Java Job Scheduling Platform --~--~-~--~~~---~--~~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~--~~~~--~~--~--~---
[gwt-contrib] Re: getAbsoluteLeft/Top() returns incorrect value in IE when zoomed in
How about using the screen.deviceXDPI and related properties?
See:
-
http://msdn.microsoft.com/en-us/library/cc849094(VS.85).aspx#DetectViaJava
- http://msdn.microsoft.com/en-us/library/ms537625(VS.85).aspx
- http://msdn.microsoft.com/en-us/library/ms533721(VS.85).aspx
Something like (untested!):
@Override
public native int getAbsoluteLeft(Element elem) /*-{
return (elem.getBoundingClientRect().left /
($wnd.screen.deviceXDPI / $wnd.screen.logicalXDPI)) +
@com.google.gwt.user.client.impl.DocumentRootImpl::documentRoot.scrollLeft;
}-*/;
@Override
public native int getAbsoluteTop(Element elem) /*-{
return (elem.getBoundingClientRect().top /
($wnd.screen.deviceYDPI / $wnd.screen.logicalYDPI)) +
@com.google.gwt.user.client.impl.DocumentRootImpl::documentRoot.scrollTop;
}-*/;
IMO, people will soon ask for support for documents using the 'zoom' CSS
property (on document.body –easy to deal with– or some other elements!
–much more complex–)
http://msdn.microsoft.com/en-us/library/ms535169(VS.85).aspx
http://gwt-code-reviews.appspot.com/807
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] Re: Why is Timer#schedule(0) bad?
On 9 déc, 07:16, Kelly Norton [EMAIL PROTECTED] wrote: Chrome: 4ms (fairly recent change) Safari (mac): 10ms Safari (win): 15ms Firefox: 15ms (or 10ms if flash is running) IE: 15ms Opera: I have no clue. So, that's just a really long way of saying that there is no danger in allowing 0 and technically it is a perfectly legal value ... it's just not very useful. I'd add FWIW that HTML5 (pending a split into a distinct spec) defines setTimeout and setInterval as to asynchronously wait timeout milliseconds and then queue a task [...] http://www.whatwg.org/specs/web-apps/current-work/multipage/no.html#timers --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: getAbsoluteLeft/Top() returns incorrect value in IE when zoomed in
On 8 déc, 21:58, [EMAIL PROTECTED] wrote: The DOCTYPE actually makes a difference. The following DOCTYPE (default in AppHtml.htmlsrc) works fine: !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN However, adding the loose.dtd makes body.parentElement return the same size as body.element. The following DOCTYPE was used in the code-museum, so I changed it back to the DOCTYPE from AppHtml.htmlsrc. !DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN BTW, could we speak in terms of quirks mode and standards mode (and eventually almost standards mode)? What you're saying here is that the fix works in quirks mode but not in almost standards mode (IE has no real standards mode, maybe IE8's standards mode will be a real standards mode?) See: http://hsivonen.iki.fi/doctype/ for details on which doctype triggers which mode in browsers. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: getAbsoluteLeft/Top() returns incorrect value in IE when zoomed in
On Tue, Dec 9, 2008 at 12:42 AM, John LaBanca [EMAIL PROTECTED] wrote: Internet Explorer now works the same as Firefox. That is, with real zoom, absolute positions do not change even though the widget appears further from the left or top. I was going to put that info in the review request, but I didn't want to confuse anyone. Also, can you check what happens when you use your patched getAbsoluteLeft + getAbsoluteTop to calculate the distance between two widgets? For example Do we really need to test this? I verified that getAbsoluteLeft() returns the correct value now and is consistent between FF and IE, and I verified it against the MenuBar and SuggestBox. The fact that SuggestBoxPopup opens directly below the TextBox and MenuBarPopup opens directly below the MenuBar implicitly verified that getAbsoluteTop() + getOffsetHeight() already works. offsetHeight/Width didn't seem to be affected by this issue at all. The consistency is probably the most important thing, so if they are consistent, that is probably good enough. My worry was that setHeight/setWidth would be using different units thet getAbsoluteTop/left in the zoomed in state, and that therefore, calculations that worked normally in GWT 1.5 would start failing with GWT 1.6. However, if firefox natively already uses the zoomed in coordinate system, then those programs would already be failing, therefore it cannot be a problem. In otherwords, LGTM then. Cheers, Emily Thanks, John LaBanca [EMAIL PROTECTED] On Mon, Dec 8, 2008 at 6:29 PM, [EMAIL PROTECTED] wrote: Have you checked to see what values getAbsoluteLeft/Top give in your demo with Firefox3 and Opera? It seems like we want all the real zooming browsers to handle this the same way. Also, can you check what happens when you use your patched getAbsoluteLeft + getAbsoluteTop to calculate the distance between two widgets? For example Widget a (absolutely positioned at (100,100) 50 px tall. Widget b flows naturally after widget a. There are no styles on any widget to confuse this poor example. Widget c's height is calculated to be getAbsoluteTop(a) - getAbsoluteTop(b) is Widget c's height the same as widget a's? http://gwt-code-reviews.appspot.com/807 -- There are only 10 types of people in the world: Those who understand binary, and those who don't --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: Tweaks to API checker
Committed as 4274. On Mon, Dec 8, 2008 at 8:25 PM, Amit Manjhi [EMAIL PROTECTED] wrote: LGTM On Mon, Dec 8, 2008 at 6:40 PM, [EMAIL PROTECTED] wrote: Reviewers: amitmanjhi, Description: Amit, This patch changes the gwt build.xml file to use value rather then location when defining the apicheck.oldroot ant property + adds the removal the old setImageBase method. Please review this at http://gwt-code-reviews.appspot.com/602 Affected files: build.xml tools/api-checker/config/gwt15_16userApi.conf Index: build.xml === --- build.xml (revision 4269) +++ build.xml (working copy) @@ -9,7 +9,7 @@ property name=gwt.apicheck.config location=tools/api-checker/config/gwt15_16userApi.conf/ property name=gwt.apicheck.oldroot -location=../gwt-1.5/ +value=../gwt-1.5/ target name=dist depends=dev, user, servlet, tools, jni, doc, samples description=Run the distributions gwt.ant dir=distro-source / Index: tools/api-checker/config/gwt15_16userApi.conf === --- tools/api-checker/config/gwt15_16userApi.conf (revision 4269) +++ tools/api-checker/config/gwt15_16userApi.conf (working copy) @@ -30,3 +30,4 @@ java.lang.StringBuilder::append(Ljava/lang/StringBuffer;) OVERRIDABLE_METHOD_ARGUMENT_TYPE_CHANGE com.google.gwt.user.client.ui.Button::Button(Ljava/lang/String;Lcom/google/gwt/user/client/ui/ClickListener;) OVERLOADED_METHOD_CALL com.google.gwt.user.client.ui.ToggleButton::ToggleButton(Lcom/google/gwt/user/client/ui/Image;Lcom/google/gwt/user/client/ui/Image;Lcom/google/gwt/user/client/ui/ClickListener;) OVERLOADED_METHOD_CALL +com.google.gwt.user.client.ui.Tree::setImageBase(Ljava/lang/String;) MISSING \ No newline at end of file -- There are only 10 types of people in the world: Those who understand binary, and those who don't --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4275 - in releases/1.6/user: src/com/google/gwt/user/client/ui test/com/google/gwt/user/client/ui
Author: [EMAIL PROTECTED]
Date: Tue Dec 9 06:31:36 2008
New Revision: 4275
Modified:
releases/1.6/user/src/com/google/gwt/user/client/ui/Tree.java
releases/1.6/user/test/com/google/gwt/user/client/ui/TreeTest.java
Log:
Removing deprecated setImageBase method from tree.
Modified: releases/1.6/user/src/com/google/gwt/user/client/ui/Tree.java
==
--- releases/1.6/user/src/com/google/gwt/user/client/ui/Tree.java
(original)
+++ releases/1.6/user/src/com/google/gwt/user/client/ui/Tree.java Tue Dec
9 06:31:36 2008
@@ -638,22 +638,6 @@
}
/**
- * Sets the base URL under which this tree will find its default images.
These
- * images must be named tree_white.gif, tree_open.gif, and
- * tree_closed.gif.
- *
- * @param baseUrl
- * @deprecated Use [EMAIL PROTECTED] #Tree(TreeImages)} as it provides a
more
efficent
- * and manageable way to supply a set of images to be used
within
- * a tree.
- */
- @Deprecated
- public void setImageBase(String baseUrl) {
-images = new ImagesFromImageBase(baseUrl);
-root.updateStateRecursive();
- }
-
- /**
* Selects a specified item.
*
* @param item the item to be selected, or codenull/code to deselect
all
Modified: releases/1.6/user/test/com/google/gwt/user/client/ui/TreeTest.java
==
--- releases/1.6/user/test/com/google/gwt/user/client/ui/TreeTest.java
(original)
+++ releases/1.6/user/test/com/google/gwt/user/client/ui/TreeTest.java Tue
Dec 9 06:31:36 2008
@@ -280,12 +280,7 @@
parent.addItem(child);
t.addItem(parent);
RootPanel.get().add(t);
-
-// This was throwing UnsupportedOperationException at one point (just
-// before the 1.5 release), because of additions to ImagePrototype. If
-// that were to creep back in, we'd see an exception.
-t.setImageBase();
-
+
// Make sure the parent open/close image actually got created (there's
// no actual public image file to back this up, but it won't matter
from
// the standpoint of this test).
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] Re: getAbsoluteLeft/Top() returns incorrect value in IE when zoomed in
committed as r4276 $wnd.screen.deviceXDPI / $wnd.screen.logicalXDPI didn't seem to work (they returned the same value even when zoomed in). Reading through the MSDN docs, it looks deviceXDPI changes when you change your screen resolution, not when you zoom in. http://gwt-code-reviews.appspot.com/807 --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] review: build.xml fix on my r4271
Another patch-review for you, sorry: I'm actually a bit surprised that the
prior built, which it did, but I just got a local build error complaining
about tarfileset occurring inside a zip for the windows build... dangers
of too much cut-n-paste.
Patch in-line, as it's so short:
Index: distro-source/windows/build.xml
===
--- distro-source/windows/build.xml (revision 4279)
+++ distro-source/windows/build.xml (working copy)
@@ -13,7 +13,7 @@
zipfileset file=${gwt.build.lib}/gwt-user.jar
prefix=${project.distname} /
zipfileset file=${gwt.build.lib}/gwt-servlet.jar
prefix=${project.distname} /
zipfileset file=${gwt.build.lib}/gwt-benchmark-viewer.jar
prefix=${project.distname} /
- tarfileset file=${gwt.build.lib}/gwt-soyc-vis.jar
prefix=${project.distname} /
+ zipfileset file=${gwt.build.lib}/gwt-soyc-vis.jar
prefix=${project.distname} /
!-- jni libs--
zipfileset dir=${gwt.build.jni}/${dist.platform}
prefix=${project.distname} /
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] Fix for listenerwrapper, remove listener
Reviewers: jlabanca, Description: John, Could you review this fix for the assertion error that happens in some circumstances when you remove Window listeners? Also included are two new test cases to ensure we don't have a regression on this issue. As a side note, I think this situation is a good argument for putting helper classes in a shared impl package rather then cloning them once helper classes are needed by more then one package, as this bug was fixed in one implementation but not the other. Please review this at http://gwt-code-reviews.appspot.com/603 Affected files: user/src/com/google/gwt/user/client/ListenerWrapper.java user/src/com/google/gwt/user/client/Window.java user/src/com/google/gwt/user/client/ui/ListenerWrapper.java user/test/com/google/gwt/user/client/WindowTest.java user/test/com/google/gwt/user/client/ui/CheckBoxTest.java --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4274 - in releases/1.6: . tools/api-checker/config
Author: [EMAIL PROTECTED] Date: Tue Dec 9 06:27:26 2008 New Revision: 4274 Modified: releases/1.6/build.xml releases/1.6/tools/api-checker/config/gwt15_16userApi.conf Log: Updating api-checker config. Modified: releases/1.6/build.xml == --- releases/1.6/build.xml (original) +++ releases/1.6/build.xml Tue Dec 9 06:27:26 2008 @@ -9,7 +9,7 @@ property name=gwt.apicheck.config location=tools/api-checker/config/gwt15_16userApi.conf/ property name=gwt.apicheck.oldroot -location=../gwt-1.5/ +value=../gwt-1.5/ target name=dist depends=dev, user, servlet, tools, jni, doc, samples description=Run the distributions gwt.ant dir=distro-source / Modified: releases/1.6/tools/api-checker/config/gwt15_16userApi.conf == --- releases/1.6/tools/api-checker/config/gwt15_16userApi.conf (original) +++ releases/1.6/tools/api-checker/config/gwt15_16userApi.conf Tue Dec 9 06:27:26 2008 @@ -30,3 +30,4 @@ java.lang.StringBuilder::append(Ljava/lang/StringBuffer;) OVERRIDABLE_METHOD_ARGUMENT_TYPE_CHANGE com.google.gwt.user.client.ui.Button::Button(Ljava/lang/String;Lcom/google/gwt/user/client/ui/ClickListener;) OVERLOADED_METHOD_CALL com.google.gwt.user.client.ui.ToggleButton::ToggleButton(Lcom/google/gwt/user/client/ui/Image;Lcom/google/gwt/user/client/ui/Image;Lcom/google/gwt/user/client/ui/ClickListener;) OVERLOADED_METHOD_CALL +com.google.gwt.user.client.ui.Tree::setImageBase(Ljava/lang/String;) MISSING \ No newline at end of file --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4278 - releases/1.6/eclipse
Author: [EMAIL PROTECTED] Date: Tue Dec 9 07:43:57 2008 New Revision: 4278 Modified: releases/1.6/eclipse/README.txt Log: Forgot to commit the updated eclipse/README.txt when I was removing references to projectCreator. Modified: releases/1.6/eclipse/README.txt == --- releases/1.6/eclipse/README.txt (original) +++ releases/1.6/eclipse/README.txt Tue Dec 9 07:43:57 2008 @@ -159,11 +159,11 @@ == Launching 'Hello' == -While the 'projectCreator' and 'applicationCreator' scripts are useful for -setting up projects and launch configurations that target a GWT installation, -they are not intended for GWT developers working against the source code. You -will want to run not against .jar files, but against the class files built by -Eclipse. The following instructions help you do just that. +While the 'applicationCreator' script is useful for setting up projects and +launch configurations that target a GWT installation, it is not intended for +GWT developers working against the source code. You will want to run not +against .jar files, but against the class files built by Eclipse. The +following instructions help you do just that. 1) Import the 'Hello' project if you haven't already. @@ -211,10 +211,9 @@ 1) Create or Import a new project - Using the 'projectCreator' and 'applicationCreator' scripts is - an easy way to do this, but you cannot use the created launch - scripts to develop the GWT core source because they are - configured to run with .jar files from a GWT installation. + Using the 'applicationCreator' script is an easy way to do this, but you + cannot use the created launch scripts to develop the GWT core source because + they are configured to run with .jar files from a GWT installation. 2) Add a project reference to the gwt-user project: --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4279 - releases/1.6/user/test/com/google/gwt/user/client/ui
Author: [EMAIL PROTECTED]
Date: Tue Dec 9 08:28:08 2008
New Revision: 4279
Modified:
releases/1.6/user/test/com/google/gwt/user/client/ui/TreeTest.java
Log:
Removing test that should have been removed with last commit.
TBA:jlabanca
Modified: releases/1.6/user/test/com/google/gwt/user/client/ui/TreeTest.java
==
--- releases/1.6/user/test/com/google/gwt/user/client/ui/TreeTest.java
(original)
+++ releases/1.6/user/test/com/google/gwt/user/client/ui/TreeTest.java Tue
Dec 9 08:28:08 2008
@@ -270,21 +270,4 @@
assertNull(eLabel.getParent());
assertFalse(childTree.getChildWidgets().containsKey(eLabel.getParent()));
}
-
- /**
- * Tests setImageBase() which, though deprecated, should still work.
- */
- public void testSetImageBase() {
-Tree t = new Tree();
-TreeItem parent = new TreeItem(parent);
-parent.addItem(child);
-t.addItem(parent);
-RootPanel.get().add(t);
-
-// Make sure the parent open/close image actually got created (there's
-// no actual public image file to back this up, but it won't matter
from
-// the standpoint of this test).
-String parentSrc = DOM.getImgSrc(parent.getImageElement());
-assertTrue(parentSrc.endsWith(tree_closed.gif));
- }
}
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4277 - releases/1.6/reference/code-museum/src/com/google/gwt/museum/public
Author: [EMAIL PROTECTED] Date: Tue Dec 9 07:24:19 2008 New Revision: 4277 Modified: releases/1.6/reference/code-museum/src/com/google/gwt/museum/public/SingleIssue.html Log: I accidentally changed the doc type of SingleIssue.html before submitting r4276. The doctype should have been changed to quirks mode, not standards mode. Patch by: jlabanca Review by: ecc (reviewed r4276) Issue: 3172 Modified: releases/1.6/reference/code-museum/src/com/google/gwt/museum/public/SingleIssue.html == --- releases/1.6/reference/code-museum/src/com/google/gwt/museum/public/SingleIssue.html (original) +++ releases/1.6/reference/code-museum/src/com/google/gwt/museum/public/SingleIssue.html Tue Dec 9 07:24:19 2008 @@ -1,5 +1,4 @@ -!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.0 Transitional//EN - http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd; +!DOCTYPE HTML PUBLIC -//W3C//DTD HTML 4.01 Transitional//EN html head titleSingle issue from Museum/title --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4276 - in releases/1.6: reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum ref...
Author: [EMAIL PROTECTED]
Date: Tue Dec 9 07:17:36 2008
New Revision: 4276
Added:
releases/1.6/reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/Issue3172.java
Modified:
releases/1.6/reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/DefaultMuseum.java
releases/1.6/reference/code-museum/src/com/google/gwt/museum/public/DefaultMuseum.html
releases/1.6/reference/code-museum/src/com/google/gwt/museum/public/Museum.html
releases/1.6/reference/code-museum/src/com/google/gwt/museum/public/SingleIssue.html
releases/1.6/user/src/com/google/gwt/dom/client/DOMImplIE6.java
Log:
Fixed the return values of getAbsoluteTop/Left() in IE when the browser is
zoomed in. Previously, getAbsoluteTop/Left() returned real coordinates
instead of logical coordinates, as they do in FF.
Patch by: jlabanca
Review by: ecc
Issue: 3172
Modified:
releases/1.6/reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/DefaultMuseum.java
==
---
releases/1.6/reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/DefaultMuseum.java
(original)
+++
releases/1.6/reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/DefaultMuseum.java
Tue Dec 9 07:17:36 2008
@@ -47,6 +47,7 @@
addIssue(new Issue2392());
addIssue(new Issue2443());
addIssue(new Issue2855());
+addIssue(new Issue3172());
}
public void addVisuals() {
Added:
releases/1.6/reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/Issue3172.java
==
--- (empty file)
+++
releases/1.6/reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/Issue3172.java
Tue Dec 9 07:17:36 2008
@@ -0,0 +1,89 @@
+/*
+ * Copyright 2008 Google Inc.
+ *
+ * Licensed under the Apache License, Version 2.0 (the License); you may
not
+ * use this file except in compliance with the License. You may obtain a
copy of
+ * the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an AS IS BASIS,
WITHOUT
+ * WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
+ * License for the specific language governing permissions and limitations
under
+ * the License.
+ */
+package com.google.gwt.museum.client.defaultmuseum;
+
+import com.google.gwt.museum.client.common.AbstractIssue;
+import com.google.gwt.user.client.Command;
+import com.google.gwt.user.client.ui.MenuBar;
+import com.google.gwt.user.client.ui.MenuItem;
+import com.google.gwt.user.client.ui.Widget;
+
+/**
+ * Verify that IE returns the correct value for getAbsoluteLeft() when
zoomed
+ * in. The absolute left coordinate should NOT depend on the zoom. That
is, an
+ * elements absoluteLeft position should be the same regardless of zoom (IE
+ * automatically multiplies it by the zoom).
+ */
+public class Issue3172 extends AbstractIssue {
+
+ @Override
+ public Widget createIssue() {
+// Create a command that will execute on menu item selection
+Command emptyCommand = new Command() {
+ public void execute() {
+ }
+};
+
+// Create a menu bar
+MenuBar menu = new MenuBar();
+menu.setWidth(500px);
+menu.setAutoOpen(true);
+
+// Create a sub menu of recent documents
+MenuBar recentDocsMenu = new MenuBar(true);
+recentDocsMenu.addItem(Document 0, emptyCommand);
+recentDocsMenu.addItem(Document 1, emptyCommand);
+recentDocsMenu.addItem(Document 2, emptyCommand);
+
+// Create the file menu
+MenuBar fileMenu = new MenuBar(true);
+menu.addItem(new MenuItem(File, fileMenu));
+fileMenu.addItem(New, emptyCommand);
+fileMenu.addItem(Print, emptyCommand);
+fileMenu.addItem(Recent Docs, recentDocsMenu);
+
+// Create the edit menu
+MenuBar editMenu = new MenuBar(true);
+menu.addItem(new MenuItem(Edit, editMenu));
+editMenu.addItem(Cut, emptyCommand);
+editMenu.addItem(Copy, emptyCommand);
+editMenu.addItem(Paste, emptyCommand);
+
+// Create the help menu
+MenuBar helpMenu = new MenuBar(true);
+menu.addItem(new MenuItem(Help, helpMenu));
+helpMenu.addItem(Settings, emptyCommand);
+helpMenu.addItem(About, emptyCommand);
+
+return menu;
+ }
+
+ @Override
+ public String getInstructions() {
+return In IE, press Ctrl++ to zoom in, then verify that the sub menus
open
++ in the correct locations.;
+ }
+
+ @Override
+ public String getSummary() {
+return getAbsoluteLeft() with zoom in IE;
+ }
+
+ @Override
+ public boolean hasCSS() {
+return false;
+ }
+}
Modified:
releases/1.6/reference/code-museum/src/com/google/gwt/museum/public/DefaultMuseum.html
[gwt-contrib] Re: Fix for listenerwrapper, remove listener
LGTM http://gwt-code-reviews.appspot.com/603 --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4280 - wiki
Author: [EMAIL PROTECTED] Date: Tue Dec 9 10:14:21 2008 New Revision: 4280 Modified: wiki/WAR_Design_1_6.wiki Log: Removed the whole module-session idea due to it creating too many issues. Modified: wiki/WAR_Design_1_6.wiki == --- wiki/WAR_Design_1_6.wiki(original) +++ wiki/WAR_Design_1_6.wikiTue Dec 9 10:14:21 2008 @@ -89,39 +89,24 @@ We will no longer use `GWTShellServlet` and embedded Tomcat. Instead, we will used Jetty by default, but allow other servers to be plugged in through a lightweight interface. # `HostedMode` performs an initial link for each module specified on the command line -# Public resources and a generated selection script are copied into `war/qualified.ModuleName/` -# The generated selection script will not override an existing compiled selection script; this is to prevent clobbering a compile -# No generator produced resources will be created +# A generated selection script is copied into `war/qualified.ModuleName/` +# The generated selection script (and other resources) will not override an existing compiled selection script; this is to prevent clobbering a compile +# No public or generator produced resources will be copied # `HostedMode` starts the web server, targeting it at `war/`. # `HostedMode` launches a hosted browser window for each `-startupUrl` specified on the command line # The hosted browser requests the host HTML page from the server. # The host HTML page loads the generated selection script for the included modules. - # The generated selection script recognizes the hosted browser environment and takes special action -# The `window.external` interface is used to create a unique debugging session. -# A random (or monotonically increasing) session ID is chosen -# A new module-session directory, `war/qualified.ModuleName-sessionID/` is created -# Another link is performed into the module-session directory -# The original selection script delegates to the new selection script in the module-session directory -# The GWT module base url targets the new directory -# The new selection script loads `hosted.html` into an `IFRAME`, and hosted mode continues bootstrapping as per 1.5 -# Whenever new resources are generated from a `GWT.create()` resolution, an *incremental link* is performed into the module-session directory. -# The new selection script hooks window closing, and triggers deletion of the module-session directory when the session is complete. - # As a backup, a VM shutdown hook is used to delete any outstanding module-session directories. - # If the user refreshes the page -# The old module-session directory is deleted as per above -# A new module-session directory is created as per above -# We do not provide a mechanism to reload server-side code executing in the servlet container + # The selection script (in hosted mode only) calls `window.external.initModule(moduleName)` +# Hosted mode triggers a new initial link, copying public resources and possibly updating the selection script +# If the selection script was updated, `initModule()` returns `true`, which signals the selection script to force a full-page refresh in order to load the updated selection script + # The selection script loads `hosted.html` into an `IFRAME`, and hosted mode continues bootstrapping as per 1.5 + # Whenever new resources are generated from a `GWT.create()` resolution, an *incremental link* is performed # If the user presses Compile/Browse # The set of modules passed in on the command line are compiled -# They are linked into the canonical path, `war/qualified.ModuleName/`, not the module-session directory. -# A web browser then loads the host HTML page, which loads the compiled selection script. -# The compiled selection script detects that it is not running in the hosted browser, and therefore loads web mode normally. - -== RPC Servlets in Hosted Mode == - -RPC servlets (`RemoteServiceServlet`) present special problems with this design. RPC servlets by design and convention are mounted relative to the module's base URL. However, we are effectively changing the module's base URL for each hosted mode module session. We believe this implies N-many instances of RPC servlets must be instantiated simultaneously, because each instance might have a different serialization policy file corresponding to a different hosted mode session state. N-many instances implies that this cannot be accomplished merely through web.xml configuration, but servlets must be dynamically mapped; perhaps through a servlet filter. - -Alternatively: perhaps we could do write a pattern-match rule in the web.xml combined with some special magic in `RemoteServiceServlet` to avoid having to install a filter, and allow a
[gwt-contrib] Re: Basic rough-cut of 1.6 WAR support
On Fri, Dec 5, 2008 at 12:28 PM, BobV [EMAIL PROTECTED] wrote: - Several classes in user/test/.../server/rpc do not compile against Jetty given the difference in the servlet API in Jetty versus Tomcat. This is problematic when using an Eclipse project structure that isn't hamstrung by linked resources. I've noticed this too. An easy solution would be to switch over to the 1.5 API of servlets throughout the code base. All it should take is adding one method, I think it is ServletContext.getContextPath, to all of our implementations of ServletContext. The Java verifier should be okay even if these things are used on a container that uses the 1.4 API, because the verifier check that would fail does not actually run until the method in question is invoked, and in this case the method would never be invoked. The result would be that our code only compiles against the Servlet API version 1.5, but the compiled files run against version 1.4. -Lex --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Comment on WAR_Design_1_6 in google-web-toolkit
Comment by danigb: great!! i really like this! For more information: http://code.google.com/p/google-web-toolkit/wiki/WAR_Design_1_6 --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Comment on DesignOOPHM in google-web-toolkit
Comment by danigb: this looks amazing! go ahead! For more information: http://code.google.com/p/google-web-toolkit/wiki/DesignOOPHM --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Warning message in IE6 when using NamedFrame on SSL-secured web-site
Reviewers: ecc, Description: Description: The iframe created in a NamedFrame does not have a src, so it throws a mixed content warning in IE6 on an SSL-secured website. Fix: Setting the source to javascript:'' fixes the problem, and we've used the same trick on all other iframes (history iframe, GWT module iframe). In addition, NamedFrame currently replaces the iframe created by its parent class Frame in the super constructor. This patch changes that behavior by passing the named iframe into the super constructor. The code to create the named frame has been abstracted to a private static method. Testing: = Manually verified the patch against an SSL-enabled web server. I added a simple code museum test, but it needs to be run against a secure server. Please review this at http://gwt-code-reviews.appspot.com/808 Affected files: reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/DefaultMuseum.java reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/Issue2318.java user/src/com/google/gwt/user/client/ui/NamedFrame.java --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: Warning message in IE6 when using NamedFrame on SSL-secured web-site
The diff didn't go through for DefaultMuseum.java. Here is that part of the patch: Index: reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/DefaultMuseum.java === --- reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/DefaultMuseum.java (revision 4279) +++ reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/DefaultMuseum.java (working copy) @@ -38,6 +38,7 @@ addIssue(new Issue2261()); addIssue(new Issue2290()); addIssue(new Issue2307()); +addIssue(new Issue2318()); addIssue(new Issue2321()); addIssue(new Issue2331()); addIssue(new Issue2338()); http://gwt-code-reviews.appspot.com/808 --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: Warning message in IE6 when using NamedFrame on SSL-secured web-site
Frames are used to load external sites, so the src is likely an actual URL, whereas NamedFrames are used locally and in FormPanels. While NamedFrames can be used for external sites and vice versa, that isn't the default use case. Also, people can change the URL of a NamedFrame via setUrl(), and they can pass the URL into Frame, so there are workarounds for either use case. If that makes sense, I'll commit. Note: we could set the default URL of a named frame to javascript:'', but I'm not sure thats makes logical sense. We could even make Document.createIFrame() add the javascript:'' source automatically. I don't think it will have any side effects, but I don't know for sure. Thanks, John LaBanca [EMAIL PROTECTED] On Tue, Dec 9, 2008 at 3:34 PM, Emily Crutcher [EMAIL PROTECTED] wrote: Why is this a problem for NamedFrames but not Frames? Other then that, LGTM. On Tue, Dec 9, 2008 at 3:10 PM, [EMAIL PROTECTED] wrote: Reviewers: ecc, Description: Description: The iframe created in a NamedFrame does not have a src, so it throws a mixed content warning in IE6 on an SSL-secured website. Fix: Setting the source to javascript:'' fixes the problem, and we've used the same trick on all other iframes (history iframe, GWT module iframe). In addition, NamedFrame currently replaces the iframe created by its parent class Frame in the super constructor. This patch changes that behavior by passing the named iframe into the super constructor. The code to create the named frame has been abstracted to a private static method. Testing: = Manually verified the patch against an SSL-enabled web server. I added a simple code museum test, but it needs to be run against a secure server. Please review this at http://gwt-code-reviews.appspot.com/808 Affected files: reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/DefaultMuseum.java reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/Issue2318.java user/src/com/google/gwt/user/client/ui/NamedFrame.java -- There are only 10 types of people in the world: Those who understand binary, and those who don't --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: Warning message in IE6 when using NamedFrame on SSL-secured web-site
Why is this a problem for NamedFrames but not Frames? Other then that, LGTM. On Tue, Dec 9, 2008 at 3:10 PM, [EMAIL PROTECTED] wrote: Reviewers: ecc, Description: Description: The iframe created in a NamedFrame does not have a src, so it throws a mixed content warning in IE6 on an SSL-secured website. Fix: Setting the source to javascript:'' fixes the problem, and we've used the same trick on all other iframes (history iframe, GWT module iframe). In addition, NamedFrame currently replaces the iframe created by its parent class Frame in the super constructor. This patch changes that behavior by passing the named iframe into the super constructor. The code to create the named frame has been abstracted to a private static method. Testing: = Manually verified the patch against an SSL-enabled web server. I added a simple code museum test, but it needs to be run against a secure server. Please review this at http://gwt-code-reviews.appspot.com/808 Affected files: reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/DefaultMuseum.java reference/code-museum/src/com/google/gwt/museum/client/defaultmuseum/Issue2318.java user/src/com/google/gwt/user/client/ui/NamedFrame.java -- There are only 10 types of people in the world: Those who understand binary, and those who don't --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4284 - wiki
Author: [EMAIL PROTECTED] Date: Tue Dec 9 12:58:53 2008 New Revision: 4284 Modified: wiki/GwtJavaApiCompatibilityChecker.wiki Log: Edited wiki page through web user interface. Modified: wiki/GwtJavaApiCompatibilityChecker.wiki == --- wiki/GwtJavaApiCompatibilityChecker.wiki(original) +++ wiki/GwtJavaApiCompatibilityChecker.wikiTue Dec 9 12:58:53 2008 @@ -4,13 +4,13 @@ GWT Java API compatibility checker is a tool to check two versions of GWT for API source compatibility. In particular, the tool can ensure that newer releases of GWT are able to compile applications that previous versions could compile. A user can also specify explicit API changes that must be white-listed, i.e., ignored by the tool. While we focus on GWT, this tool works for any Java API. = Background = -A key advantage of GWT is that client applications (developed using GWT) do not have to worry about supporting new browsers or newer versions of a previously supported browser. GWT handles such issues. For example, when IE8 will be released, client application developers will be able to easily support IE8 by simply compiling their applications against a newer version of GWT. In general, as GWT continues to improve both in the quality of the JavaScript code it generates and the number of platforms it supports, client application developers can tap into these improvements by simply compiling the Java versions of their applications against the latest version of GWT. For client application developers to be able to successfully tap into these improvements, new GWT releases must successfully compile applications that previous versions could compile. We call this property API source compatibility. +A key advantage of GWT is that client applications (developed using GWT) do not have to worry about supporting new browsers or newer versions of a previously supported browser. GWT handles such issues. For example, when IE8 will be released, client application developers will be able to easily support IE8 by simply compiling their applications against a newer version of GWT. In general, as GWT continues to improve both in the quality of the !JavaScript code it generates and the number of platforms it supports, client application developers can tap into these improvements by simply compiling the Java versions of their applications against the latest version of GWT. For client application developers to be able to successfully tap into these improvements, new GWT releases must successfully compile applications that previous versions could compile. We call this property API source compatibility. As GWT's popularity increases, the challenge of maintaining GWT's API source compatibility is going to increase due to two factors. First, the GWT code is likely to become more complex over time as the number of features and platforms it supports increases. Second, the number of contributors to GWT is likely to increase as well. With increasing number of contributors, the changes to the source code will increase in both magnitude and number. Therefore it is desirable to automate the task of checking API source compatibility. -Other evolving APIs, most notably the Java language API, also face a similar problem [1]. Almost all of these APIs aim for binary compatibility, as specified in the Java language specification [2]. With binary compatibility, the aim for a new API release is to ensure that the client applications can use the class files of the new release in place of the class files of the previous release. There is no recompilation involved. Several tools exist for checking API binary compatibility [3, 4]. To the best of our knowledge, no tool exists for checking API source compatibility. +Other evolving APIs, most notably the Java language API, also face a similar problem ![1]. Almost all of these APIs aim for binary compatibility, as specified in the Java language specification ![2]. With binary compatibility, the aim for a new API release is to ensure that the client applications can use the class files of the new release in place of the class files of the previous release. There is no recompilation involved. Several tools exist for checking API binary compatibility [3, 4]. To the best of our knowledge, no tool exists for checking API source compatibility. Of course, there can be cases when breaking the API is necessary. To handle these cases, the tool should support white-lists. Specifying a whitelist explicitly should force the developers to think twice before breaking an API. The whitelist would also help client applications in refactoring their code appropriately. @@ -71,7 +71,8 @@ # Check compatibility: When ApiComptabilityChecker is provided a configuration file with information about the two repositories, it checks them for
[gwt-contrib] [google-web-toolkit commit] r4286 - wiki
Author: [EMAIL PROTECTED] Date: Tue Dec 9 13:04:40 2008 New Revision: 4286 Modified: wiki/GwtJavaApiCompatibilityChecker.wiki Log: Edited wiki page through web user interface. Modified: wiki/GwtJavaApiCompatibilityChecker.wiki == --- wiki/GwtJavaApiCompatibilityChecker.wiki(original) +++ wiki/GwtJavaApiCompatibilityChecker.wikiTue Dec 9 13:04:40 2008 @@ -10,7 +10,7 @@ As GWT's popularity increases, the challenge of maintaining GWT's API source compatibility is going to increase due to two factors. First, the GWT code is likely to become more complex over time as the number of features and platforms it supports increases. Second, the number of contributors to GWT is likely to increase as well. With increasing number of contributors, the changes to the source code will increase in both magnitude and number. Therefore it is desirable to automate the task of checking API source compatibility. -Other evolving APIs, most notably the Java language API, also face a similar problem [http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs 1]. Almost all of these APIs aim for binary compatibility, as specified in the Java language specification [http://java.sun.com/docs/books/jls/third_edition/html/binaryComp.html 2]. With binary compatibility, the aim for a new API release is to ensure that the client applications can use the class files of the new release in place of the class files of the previous release. There is no recompilation involved. Several tools exist for checking API binary compatibility [[http://clirr.sourceforge.net/ 3], [http://sab39.netreach.com/Software/Japitools/Usage/japize/59/ 4]. To the best of our knowledge, no tool exists for checking API source compatibility. +Other evolving APIs, most notably the Java language API, also face a similar problem [[http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs 1]]. Almost all of these APIs aim for binary compatibility, as specified in the Java language specification [[http://java.sun.com/docs/books/jls/third_edition/html/binaryComp.html 2]]. With binary compatibility, the aim for a new API release is to ensure that the client applications can use the class files of the new release in place of the class files of the previous release. There is no recompilation involved. Several tools exist for checking API binary compatibility [[http://clirr.sourceforge.net/ 3], [http://sab39.netreach.com/Software/Japitools/Usage/japize/59/ 4]]. To the best of our knowledge, no tool exists for checking API source compatibility. Of course, there can be cases when breaking the API is necessary. To handle these cases, the tool should support white-lists. Specifying a whitelist explicitly should force the developers to think twice before breaking an API. The whitelist would also help client applications in refactoring their code appropriately. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] RR: Adding api-checker to selected packages in gwt-incubator
In gwt-incubator, we want to be able to tag widgets/libaries alpha/beta/releaseCandidate. However, this implies an extra level of support for releaseCandidate libraries/widgets. Specifically, between each incubator drop, if we had to break the API, which we will occasionally need to do, we want to make sure it is listed in our release notes. In order to enforce this, Amit and I are proposing that we add an api checker config to gwt-incubator for release quality libraries and widgets. For now, the process would be informal, where a config file would specify the release quality libraries and widgets. Once a library or widget was listed as a release candidate, any breaking API changes since the last gwt-incubator drop would have to be whitelisted. The whitelist config would be checked into svn so developers could submit changes + new whitelist entries on demand. Above each whitelist entry, the developer should put a comment for why the change was made and what new API should be used instead. Everytime we created a new gwt-incubator drop, we would use the comments in the whitelist to generate a breaking changes section to our release notes. The whitelist would then be reset for the next drop. The gwt project has been using the api checker very effectively for the last several months. To read more about the API checker in general, click herehttp://code.google.com/p/google-web-toolkit/wiki/GwtJavaApiCompatibilityChecker. Comments and (polite) flames welcome. Cheers, Amit and Emily -- There are only 10 types of people in the world: Those who understand binary, and those who don't --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4282 - wiki
Author: [EMAIL PROTECTED] Date: Tue Dec 9 12:49:24 2008 New Revision: 4282 Modified: wiki/GwtJavaApiCompatibilityChecker.wiki Log: Edited wiki page through web user interface. Modified: wiki/GwtJavaApiCompatibilityChecker.wiki == --- wiki/GwtJavaApiCompatibilityChecker.wiki(original) +++ wiki/GwtJavaApiCompatibilityChecker.wikiTue Dec 9 12:49:24 2008 @@ -66,7 +66,7 @@ dirRoot_new ../gwt-14/ sourceFiles_new dev/core:user/super:user/src excludeFiles_new user/super/com/google/gwt/junit - +}}} 2. Check compatibility: When ApiComptabilityChecker is provided a configuration file with information about the two repositories, it checks them for source compatibility and outputs the API difference. The API difference is a list of API change messages, with each API change message listed on a separate line. An API change message specifies two things: (i) a java package, class, method, or field in the existing API, (ii) the manner in which the API has changed. For example, an API change message could be java.net MISSING indicating that the package java.net has been removed. Each API change message is followed by an optional string containing additional information about the API change. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4285 - wiki
Author: [EMAIL PROTECTED] Date: Tue Dec 9 13:02:03 2008 New Revision: 4285 Modified: wiki/GwtJavaApiCompatibilityChecker.wiki Log: Edited wiki page through web user interface. Modified: wiki/GwtJavaApiCompatibilityChecker.wiki == --- wiki/GwtJavaApiCompatibilityChecker.wiki(original) +++ wiki/GwtJavaApiCompatibilityChecker.wikiTue Dec 9 13:02:03 2008 @@ -10,7 +10,7 @@ As GWT's popularity increases, the challenge of maintaining GWT's API source compatibility is going to increase due to two factors. First, the GWT code is likely to become more complex over time as the number of features and platforms it supports increases. Second, the number of contributors to GWT is likely to increase as well. With increasing number of contributors, the changes to the source code will increase in both magnitude and number. Therefore it is desirable to automate the task of checking API source compatibility. -Other evolving APIs, most notably the Java language API, also face a similar problem ![1]. Almost all of these APIs aim for binary compatibility, as specified in the Java language specification ![2]. With binary compatibility, the aim for a new API release is to ensure that the client applications can use the class files of the new release in place of the class files of the previous release. There is no recompilation involved. Several tools exist for checking API binary compatibility [3, 4]. To the best of our knowledge, no tool exists for checking API source compatibility. +Other evolving APIs, most notably the Java language API, also face a similar problem [http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs 1]. Almost all of these APIs aim for binary compatibility, as specified in the Java language specification [http://java.sun.com/docs/books/jls/third_edition/html/binaryComp.html 2]. With binary compatibility, the aim for a new API release is to ensure that the client applications can use the class files of the new release in place of the class files of the previous release. There is no recompilation involved. Several tools exist for checking API binary compatibility [[http://clirr.sourceforge.net/ 3], [http://sab39.netreach.com/Software/Japitools/Usage/japize/59/ 4]. To the best of our knowledge, no tool exists for checking API source compatibility. Of course, there can be cases when breaking the API is necessary. To handle these cases, the tool should support white-lists. Specifying a whitelist explicitly should force the developers to think twice before breaking an API. The whitelist would also help client applications in refactoring their code appropriately. --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4283 - wiki
Author: [EMAIL PROTECTED]
Date: Tue Dec 9 12:52:36 2008
New Revision: 4283
Modified:
wiki/GwtJavaApiCompatibilityChecker.wiki
Log:
Edited wiki page through web user interface.
Modified: wiki/GwtJavaApiCompatibilityChecker.wiki
==
--- wiki/GwtJavaApiCompatibilityChecker.wiki(original)
+++ wiki/GwtJavaApiCompatibilityChecker.wikiTue Dec 9 12:52:36 2008
@@ -46,7 +46,8 @@
{{{
java ApiCompatibilityChecker configFile
-The ApiCompatibilityChecker tool requires a config file as an argument.
The config file must specify two repositories of java source files: '_old'
and '_new', which are to be compared for API source compatibility.
+The ApiCompatibilityChecker tool requires a config file as an argument.
The config file must specify two repositories of
+java source files: '_old' and '_new', which are to be compared for API
source compatibility.
An optional whitelist is present at the end of the config file. The format
of the whitelist is same as the output of the tool without the whitelist.
@@ -68,11 +69,12 @@
excludeFiles_new user/super/com/google/gwt/junit
}}}
- 2. Check compatibility: When ApiComptabilityChecker is provided a
configuration file with information about the two repositories, it checks
them for source compatibility and outputs the API difference. The API
difference is a list of API change messages, with each API change message
listed on a separate line. An API change message specifies two things: (i)
a java package, class, method, or field in the existing API, (ii) the
manner in which the API has changed. For example, an API change message
could be java.net MISSING indicating that the package java.net has been
removed. Each API change message is followed by an optional string
containing additional information about the API change.
+ # Check compatibility: When ApiComptabilityChecker is provided a
configuration file with information about the two repositories, it checks
them for source compatibility and outputs the API difference. The API
difference is a list of API change messages, with each API change message
listed on a separate line. An API change message specifies two things: (i)
a java package, class, method, or field in the existing API, (ii) the
manner in which the API has changed. For example, an API change message
could be java.net MISSING indicating that the package java.net has been
removed. Each API change message is followed by an optional string
containing additional information about the API change.
-{{{ java ApiCompatibilityChecker configFile }}}
+{{{ java ApiCompatibilityChecker configFile
+}}}
- 3. Check compatibility with expected failures whitelisted: The tool can
handle a whitelist of API changes, specified in the whitelist section of
the config file. These changes are excluded from the output.
+ # Check compatibility with expected failures whitelisted: The tool can
handle a whitelist of API changes, specified in the whitelist section of
the config file. These changes are excluded from the output.
We plan to put the tool into the GWT build, so that any update to the GWT
trunk is checked for API compatibility against a reference version of GWT.
Additionally, the tool will be used to check whether the JRE library
support that GWT offers is compatible with the real JRE libraries. Ensuring
this compatibility will allow developers to develop utility software that
can be deployed on both the server-side and the client-side.
@@ -109,7 +111,7 @@
# With TypeOracle, we could tap into the already existing GWT compiler
infrastructure. We could not find an analogous tool (with compatible
licenses) in case of Java Reflection. (Japize, a tool which uses Java
reflection to check for binary compatibility, could have been suitable,
but the tool was under a GPL license.) With Reflection, everything would
have to be developed from scratch.
= References =
- 1. http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs
- 2. http://java.sun.com/docs/books/jls/third_edition/html/binaryComp.html
- 3. http://clirr.sourceforge.net/
- 4. http://sab39.netreach.com/Software/Japitools/Usage/japize/59/
\ No newline at end of file
+ # http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs
+ # http://java.sun.com/docs/books/jls/third_edition/html/binaryComp.html
+ # http://clirr.sourceforge.net/
+ # http://sab39.netreach.com/Software/Japitools/Usage/japize/59/
\ No newline at end of file
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4289 - wiki
Author: [EMAIL PROTECTED] Date: Tue Dec 9 13:13:01 2008 New Revision: 4289 Modified: wiki/GwtJavaApiCompatibilityChecker.wiki Log: Edited wiki page through web user interface. Modified: wiki/GwtJavaApiCompatibilityChecker.wiki == --- wiki/GwtJavaApiCompatibilityChecker.wiki(original) +++ wiki/GwtJavaApiCompatibilityChecker.wikiTue Dec 9 13:13:01 2008 @@ -106,11 +106,11 @@ = Discussion = -The !ApiCompatibilityChecker tool uses TypeOracle to compute the API differences. !TypeOracle in turn requires access to the java source code. Thus the tool can only work when Java source is available. An alternative to TypeOracle would be to use Java reflection which works on class files, and would not have required access to the source files. However, because of three disadvantages, we chose TypeOracle over Java relfection: +The !ApiCompatibilityChecker tool uses !TypeOracle to compute the API differences. !TypeOracle in turn requires access to the java source code. Thus the tool can only work when Java source is available. An alternative to !TypeOracle would be to use Java reflection which works on class files, and would not have required access to the source files. However, because of three disadvantages, we chose !TypeOracle over Java relfection: # One use case for the tool was to make the JRE library support that GWT offers be compatible to a real JRE implementation. However, the JRE libraries that GWT currently offers are not complete, and are currently not offered as class files. The use of Java reflection would have prevented us from running the tool to compare GWT's current support of JRE with a real JRE. # Annotations that have a retention policy of SOURCE are only present in source files -- they are discarded by the compiler during the generation of class files. For example, the @deprecated annotation falls in this category. This annotation is particularly useful for the API Compatibility Checker tool, since the tool can ignore API changes in members, classes, or packages that are deprecated. The tool currently does not support annotations, but with little effort, it can be supported in the next version. - # With TypeOracle, we could tap into the already existing GWT compiler infrastructure. We could not find an analogous tool (with compatible licenses) in case of Java Reflection. (Japize, a tool which uses Java reflection to check for binary compatibility, could have been suitable, but the tool was under a GPL license.) With Reflection, everything would have to be developed from scratch. + # With !TypeOracle, we could tap into the already existing GWT compiler infrastructure. We could not find an analogous tool (with compatible licenses) in case of Java Reflection. (Japize, a tool which uses Java reflection to check for binary compatibility, could have been suitable, but the tool was under a GPL license.) With Reflection, everything would have to be developed from scratch. = References = # http://wiki.eclipse.org/index.php/Evolving_Java-based_APIs --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: review: build.xml fix on my r4271
LGTM.
I had to make this change myself. (Apparently, this does not happen with ant
1.7+)
On Tue, Dec 9, 2008 at 11:55 AM, Freeland Abbott [EMAIL PROTECTED]
wrote:
Another patch-review for you, sorry: I'm actually a bit surprised that the
prior built, which it did, but I just got a local build error complaining
about tarfileset occurring inside a zip for the windows build... dangers
of too much cut-n-paste.
Patch in-line, as it's so short:
Index: distro-source/windows/build.xml
===
--- distro-source/windows/build.xml (revision 4279)
+++ distro-source/windows/build.xml (working copy)
@@ -13,7 +13,7 @@
zipfileset file=${gwt.build.lib}/gwt-user.jar
prefix=${project.distname} /
zipfileset file=${gwt.build.lib}/gwt-servlet.jar
prefix=${project.distname} /
zipfileset file=${gwt.build.lib}/gwt-benchmark-viewer.jar
prefix=${project.distname} /
- tarfileset file=${gwt.build.lib}/gwt-soyc-vis.jar
prefix=${project.distname} /
+ zipfileset file=${gwt.build.lib}/gwt-soyc-vis.jar
prefix=${project.distname} /
!-- jni libs--
zipfileset dir=${gwt.build.jni}/${dist.platform}
prefix=${project.distname} /
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] TabBar setTabText doesn't set word wrap false
Reviewers: ecc, Description: Description: TabBar.insertTab(text) adds a Label with wordWrap set to false. TabBar.setTabText(text) adds a Label without setting wordWrap (defaults to true). Also, there is no way to change wordWrap programatically on a tab. Fix: TabBar.setTabText(text) now sets wordWrap to false. TabBar.Tab now implements HasWordWrap, which allows users to set wordWrap on the underlying widget. If the underlying widget doesn't implement HasWordWrap, an UnsupportedOperationException is thrown. Users can check this using TabBar.Tab.hasWordWrap(). Testing: Manually verified in hosted mode and added a JUnit test. Please review this at http://gwt-code-reviews.appspot.com/604 Affected files: user/src/com/google/gwt/user/client/ui/TabBar.java user/test/com/google/gwt/user/client/ui/TabBarTest.java --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Allowing collapsible panel to have collapsed state programically controled
Reviewers: jlabanca, Description: Allows collapsible panel to have it state controlled via code. Please review this at http://gwt-code-reviews.appspot.com/809 Affected files: src-demo/com/google/gwt/widgetideas/demo/collapsiblepanel/client/CollapsiblePanelDemo.java src-demo/com/google/gwt/widgetideas/demo/collapsiblepanel/public/CollapsiblePanelDemo.html src/com/google/gwt/widgetideas/client/CollapsiblePanel.java --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: TabBar setTabText doesn't set word wrap false
The expansion of the tab interface looks great. Don't quite understand the change to the default word wrapping... http://gwt-code-reviews.appspot.com/604/diff/1/2 File user/src/com/google/gwt/user/client/ui/TabBar.java (right): http://gwt-code-reviews.appspot.com/604/diff/1/2#newcode488 Line 488: focusablePanel.setWidget(new HTML(html, false)); Why are we disabling word wrap here? http://gwt-code-reviews.appspot.com/604/diff/1/2#newcode507 Line 507: } See above comment. http://gwt-code-reviews.appspot.com/604 --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: Basic rough-cut of 1.6 WAR support
Yes, we need to implement this method in our implementations, but then not actually call the method anywhere ourselves. On Tue, Dec 9, 2008 at 1:33 PM, Lex Spoon [EMAIL PROTECTED] wrote: On Fri, Dec 5, 2008 at 12:28 PM, BobV [EMAIL PROTECTED] wrote: - Several classes in user/test/.../server/rpc do not compile against Jetty given the difference in the servlet API in Jetty versus Tomcat. This is problematic when using an Eclipse project structure that isn't hamstrung by linked resources. I've noticed this too. An easy solution would be to switch over to the 1.5 API of servlets throughout the code base. All it should take is adding one method, I think it is ServletContext.getContextPath, to all of our implementations of ServletContext. The Java verifier should be okay even if these things are used on a container that uses the 1.4 API, because the verifier check that would fail does not actually run until the method in question is invoked, and in this case the method would never be invoked. The result would be that our code only compiles against the Servlet API version 1.5, but the compiled files run against version 1.4. -Lex --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: TabBar setTabText doesn't set word wrap false
Ah, I see, the normal add(String) already sets word-wrap to false. In that case LGTM. On Tue, Dec 9, 2008 at 6:05 PM, [EMAIL PROTECTED] wrote: insertTab(String text, boolean asHTML, int beforeIndex) already disabled wordWrap, and we want insertTab() and setTabText() to be consistent. setTabText() actually unwraps the text because it replaces the element. I think its too late to change the fact that we set wordWrap to false in insertTab, and I think they should be consistent. At least now users can change the value. http://gwt-code-reviews.appspot.com/604/diff/1/2 File user/src/com/google/gwt/user/client/ui/TabBar.java (right): http://gwt-code-reviews.appspot.com/604/diff/1/2#newcode488 Line 488: focusablePanel.setWidget(new HTML(html, false)); On 2008/12/09 22:57:55, ecc wrote: Why are we disabling word wrap here? Because its disabled by default in: insertTab(String text, boolean asHTML, int beforeIndex); We want them to be consistent. http://gwt-code-reviews.appspot.com/604 -- There are only 10 types of people in the world: Those who understand binary, and those who don't --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: review: build.xml fix on my r4271
Submitted; the ant dependency would explain why the builds succeeded
On Tue, Dec 9, 2008 at 4:27 PM, Amit Manjhi [EMAIL PROTECTED] wrote:
LGTM.
I had to make this change myself. (Apparently, this does not happen with
ant 1.7+)
On Tue, Dec 9, 2008 at 11:55 AM, Freeland Abbott
[EMAIL PROTECTED] wrote:
Another patch-review for you, sorry: I'm actually a bit surprised that the
prior built, which it did, but I just got a local build error complaining
about tarfileset occurring inside a zip for the windows build... dangers
of too much cut-n-paste.
Patch in-line, as it's so short:
Index: distro-source/windows/build.xml
===
--- distro-source/windows/build.xml (revision 4279)
+++ distro-source/windows/build.xml (working copy)
@@ -13,7 +13,7 @@
zipfileset file=${gwt.build.lib}/gwt-user.jar
prefix=${project.distname} /
zipfileset file=${gwt.build.lib}/gwt-servlet.jar
prefix=${project.distname} /
zipfileset file=${gwt.build.lib}/gwt-benchmark-viewer.jar
prefix=${project.distname} /
- tarfileset file=${gwt.build.lib}/gwt-soyc-vis.jar
prefix=${project.distname} /
+ zipfileset file=${gwt.build.lib}/gwt-soyc-vis.jar
prefix=${project.distname} /
!-- jni libs--
zipfileset dir=${gwt.build.jni}/${dist.platform}
prefix=${project.distname} /
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4290 - releases/1.6/user/src/com/google/gwt/core/public
Author: [EMAIL PROTECTED] Date: Tue Dec 9 18:09:48 2008 New Revision: 4290 Removed: releases/1.6/user/src/com/google/gwt/core/public/ Log: Deleting history.html. Review by: jgw --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: Need review for more 1.6 WAR changes
On Tue, Dec 9, 2008 at 9:43 PM, Scott Blum [EMAIL PROTECTED] wrote: We deal with this problem now by asserting that hosted mode will generally not overwrite web mode artifacts unless they are newer. For the specific case of the selection script, we give the hosted mode generated selection script the same timestamp as the GWT module that produced it. This means a hosted mode selection script will not overwrite a web mode selection script except when you change the module definition, which should be acceptable. What about if the change was actually in an inherited module? Will it simply continue to use the old selection script until I manually remove it or do a web mode compile? Would it be possible to have them both produce the same selection script so it doesn't matter? -- John A. Tamplin Software Engineer (GWT), Google --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] Re: Need review for more 1.6 WAR changes
On Tue, Dec 9, 2008 at 9:48 PM, John Tamplin [EMAIL PROTECTED] wrote: On Tue, Dec 9, 2008 at 9:43 PM, Scott Blum [EMAIL PROTECTED] wrote: We deal with this problem now by asserting that hosted mode will generally not overwrite web mode artifacts unless they are newer. For the specific case of the selection script, we give the hosted mode generated selection script the same timestamp as the GWT module that produced it. This means a hosted mode selection script will not overwrite a web mode selection script except when you change the module definition, which should be acceptable. What about if the change was actually in an inherited module? Will it simply continue to use the old selection script until I manually remove it or do a web mode compile? Changing and inherited module would update the lastModification time on the leaf module, triggering an overwrite. Would it be possible to have them both produce the same selection script so it doesn't matter? In the general case, I can't think of a clean way to do it. You'd have to add some really weird logic to the primary linker. Scott --~--~-~--~~~---~--~~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~--~~~~--~~--~--~---
[gwt-contrib] [google-web-toolkit commit] r4291 - releases/1.6/dev/core/src/com/google/gwt/dev
Author: [EMAIL PROTECTED]
Date: Tue Dec 9 18:22:07 2008
New Revision: 4291
Modified:
releases/1.6/dev/core/src/com/google/gwt/dev/Compiler.java
Log:
Type fix.
Modified: releases/1.6/dev/core/src/com/google/gwt/dev/Compiler.java
==
--- releases/1.6/dev/core/src/com/google/gwt/dev/Compiler.java (original)
+++ releases/1.6/dev/core/src/com/google/gwt/dev/Compiler.java Tue Dec 9
18:22:07 2008
@@ -53,7 +53,7 @@
@Override
protected String getName() {
- return GWTCompiler.class.getName();
+ return Compiler.class.getName();
}
}
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---
