Re: Printing
i Freller can u send me the full code for printing a doc in
gwt2.4(rahul.ranja...@gmail.com)
Actually i very new to gwt so plz help me out.
On Monday, January 15, 2007 8:05:55 PM UTC+5:30, Freller wrote:
Following the thread about printing at
http://groups-beta.google.com/group/Google-Web-Toolkit/browse_frm/thread/53624cb05aa85624/247e890d73a76948?lnk=gstq=printrnum=2#247e890d73a76948
I created a simple class that can print any HTML, DOM.Element or Widget
without opening a new window.
Regards,
Freller
/**
* pre
* Generic printing class
* can be used to print the Window it self, DOM.Elements, UIObjects
(Widgets) and plain HTML
*
* Usage:
* You must insert this iframe in your host page:
* iframe id=__printingFrame
style=width:0;height:0;border:0/iframe
*
* Window:
* Print.it();
*
* Objects/HTML:
* Print.it(RootPanel.get(myId));
*
Print.it(DOM.getElementById(myId));
* Print.it(Just bPrint.it()/b!);
*
* Objects/HTML using styles:
* Print.it(link rel='StyleSheet' type='text/css'
media='paper' href='/paperStyle.css', RootPanel.get('myId'));
* Print.it(style type='text/css' media='paper' .newPage {
page-break-after: always; } /style,
*
Hip class='newPage'/pBy);
* /pre
*/
package org.gwtcommons.user.client;
import com.google.gwt.user.client.Element;
import com.google.gwt.user.client.ui.UIObject;
public class Print {
public static native void it() /*-{
$wnd.print();
}-*/;
public static native void it(String html) /*-{
var frame = $doc.getElementById('__printingFrame');
if (!frame) {
$wnd.alert(Error: Can't find printing frame.);
return;
}
frame = frame.contentWindow;
var doc = frame.document;
doc.open();
doc.write(html);
doc.close();
frame.focus();
frame.print();
}-*/;
public static void it(UIObject obj) {
it(, obj.getElement().toString());
}
public static void it(Element element) {
it(, element.toString());
}
public static void it(String style, String it) {
it(itheader+style+/headerbody+it+/body/it);
}
public static void it(String style, UIObject obj) {
it(style, obj.getElement().toString());
}
public static void it(String style, Element element) {
it(style, element.toString ());
}
} // end of class Print
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/w8Ed0Xm4M6sJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
GWT Window.localtion.assign redirect is not working in tomcat/jetty server
** i am using gwt to create a web application. when a user presses the logout button, i want to be able to refresh the page(or basically redirect to the homepage)as my GWT application runs only on one html page. what is the programmatic code to do this? I am doing Async calls to to the server side on button click and able to clear the cookies and refresh as well , but redirect is not happening . i am using Window.localtion.assign (GWT.getHomePageURL+index.html) on the client side code , but it's not redirecting to index.html . one more observation is it is working in DEV environment but once deployed on external servers like Tomcat/Jetty , redirect is hot happening , all the time its going to some other page. Any suggestions will be highly appreciated ... Thanks, Ranjan -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/GASfVYM6wSUJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Window.Location.assign() works in dev but fails in Tomcat/jetty external deployment
i am using gwt to create a web application. when a user presses the logout button, i want to be able to refresh the page(or basically redirect to the homepage)as my GWT application runs only on one html page. what is the programmatic code to do this? Even this Window.Location.assign() works in development machine , but fails in Tomcat/jetty deployment ... if any one has faced such issues , please let me know some tips to implement the same... -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/LqaIURH5gUwJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Tracking multiple steps in a RPC request on the client
Make an async RPC call and update UI on OnSuccess/OnFailure() Mohit On Wed, Sep 7, 2011 at 1:13 AM, Nestor nestord...@gmail.com wrote: I'm trying to find out how to implement the following functionality. Any help would be appreciated. The client sends a RPC request to the server for a set of data. The server has to query the data, then perform some additional processinf (e.g., filter, sort) before sending it back to the client. While this processing is going on, a progess bar is displayed to the user, indicating what step is being performed (Retrieving, Filtering, etc.) I've been looking at Server Push as a potential solution, but I'm not sure how to implement it for this situation. I suppose the server could send status messages indicating completion of each step in the process before sending the final result set. Am I on the right track? 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 google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Setting default value for DateItem()
Using Smart GWT
I am having a DynamicForm with
Code:
final DateItem dateFromFormItem = new DateItem();
{
dateFromFormItem.setTitle(Date from);
dateFromFormItem.setName(dateFrom);
}
final DateItem dateToFormItem = new DateItem();
{
dateToFormItem.setTitle(Date to);
dateToFormItem.setName(dateTo);
}
I want default value of dateToFormItem to be 24 hr from now (next day), but
could not find any related method.
dateToFormItem default value is current time only as required.
Any hint/help for this will be highly appreciated.
Mohit Ranjan
http://www.flipkart.com
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Setting default value for DateItem()
Thanks Tom.
It's working.
Mohit
On Mon, Aug 29, 2011 at 9:10 PM, Tom Carchrae t...@carchrae.net wrote:
dateItem.setDefaultValue(new Date(System.currentTimeMillis() + (24L * 60L *
60L * 1000L)));
On Mon, Aug 29, 2011 at 8:26 AM, mohit ranjan shoonya.mo...@gmail.comwrote:
Using Smart GWT
I am having a DynamicForm with
Code:
final DateItem dateFromFormItem = new DateItem();
{
dateFromFormItem.setTitle(Date from);
dateFromFormItem.setName(dateFrom);
}
final DateItem dateToFormItem = new DateItem();
{
dateToFormItem.setTitle(Date to);
dateToFormItem.setName(dateTo);
}
I want default value of dateToFormItem to be 24 hr from now (next day),
but could not find any related method.
dateToFormItem default value is current time only as required.
Any hint/help for this will be highly appreciated.
Mohit Ranjan
http://www.flipkart.com
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Firefox 6 breaks GWT ?
Also, any idea about dev mode @ FF 6 ? Last I tried, it was not done Mohit On Wed, Aug 24, 2011 at 1:12 AM, Roustalski roustal...@gmail.com wrote: Has anyone else noticed that text boxes do not show the focus ring when the element has focus, and that a KeyPressEvent looking for the charCode KeyCodes.KEY_ENTER doesn't actually work? Why would upgrading Firefox break this functionality? My app works on all other browsers and platforms, but upgrading FF to version 6 breaks things? I don't understand. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT : Best practice to send huge amount of data from server to client
Somewhere I read this binary serialization + compression - send it to client Mohit On Tue, Aug 9, 2011 at 5:03 PM, vaibhav bhalke bhalke.vaib...@gmail.comwrote: Hi folks, Which are the Best practices to send huge amount of data from server to client in GWT? Right now we are facing performance issue in GWT code. Our server side is sending huge xml (Size in MB/GB) to client side, our client side parses that xml and using parsed data, beans are formed for populating data in Celltable grid. We are filling 1k + / 10k+ records in CellTable grid. Is there any effective way/ Best practices followed while dealing with such a huge data? If we parse the data at server side and formed the beans at server side, Is this good? or any alternative way.. Any help or guidance in this matter would be appreciated. -- Best Regards, Vaibhav Bhalke http://about.me/vaibhavbhalke -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: ListListT support by RequestFactorty.
Out of this topic Curious to know, what's advantage of using ListListT over ListT when doing any client/server interaction ? - Mohit On Mon, Aug 8, 2011 at 6:33 PM, br22 g22...@gmail.com wrote: Is it supported? If not, are there planes to support in in the future? Thank you for your help. On Aug 6, 6:08 pm, br22 g22...@gmail.com wrote: It is documented that ListT or SetT are supported, is ListListT supported as well? 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 google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Contents of *gwt.rpc flie
No response :( -Shoonya On Thu, Jul 28, 2011 at 1:19 AM, Shoonya shoonya.mo...@gmail.com wrote: Hi, Can anybody explain me what's the exact format of *.gwt.rpc file? I know that this contains all the whitelisted classes. In my project *gwt.rpc file, there are 2 lines for each class like this com.xxx.yyy.FooData, true, true, true, true, com.xxx.yyy.FooData/ 856412979, 856412979 [Lcom.xxx.yyy.FooData;, true, true, false, false, [Lcom.xxx.yyy.FooData;/1961829462, 1961829462 1. What does true/false means ? 2. What are the numbers in the last ? 3. What does L stand for in 2nd line ? -Shoonya -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How can I prevent from reloading the page when the reload button on browser is clicked?
Simply put, it is impossible to avoid Page reload if the User clicks the 'Refresh' button on the browser. There is no way to avoid it if the user wants to refresh the page. And yes, when the page is refreshed, every object contained within the Page is lost. So you will have to create the whole page from the scratch. Now the problem you are facing (as I have understood) is, as the user works on your application, a number of widgets are created, removed, moved from one place to another, so on. And if at any point, the user Refreshes the page, your page would start up with the initial condition. This is normally solved by using history tokens. Now when I say saving a state, I meant saving it in a small piece of string, that would be a part of the URL (Something like #page/10caf10b or #navigation/91abc, etc). Now this small bits of information are usually sufficient for loading the entire page. It might make few ajax calls with the server. Sessions are used in cases like this. And believe me a very complex applications could be developed using just small bits of tokens that can easily be accommodated in the URL itself. Take GMail for example. You can just browse through different states of the Gmail application, and if you press refresh button at any state, you will get the same page when it refreshes. I hope you got my point. Page reloading is something that is done by the User and it can't be avoided. Its up to the programmer that the user receives the same interface even if he/she refreshes the page at any state of the application. On Jun 1, 6:43 pm, Mike Jiang mikej1...@gmail.com wrote: Thanks for a clear desc. What I'd like to say is that the refresh-save is not a new scenario at all for web apps. Actually I have heavily used the history tokens for back/forward/reloading following the sample code of GWT ShowCase. But saving states is a subtle thing for a stateful app. Accord to the info found, there are some concerns when doing historical back/forward/reloading, 1). reloading is equivalent to rebooting of an operating system or closing of an app, implies lost every and each bit in nature; 2). reloading is a feature of the traditional web app with multiple separate web pages, not a preferred one for ajax apps since a GWT project has only one html file; Actually it was said that the reloading was used less and less in ajax apps if not totally abandoned; 3). Saving the states before reloading is not a simple task to do for a dynamic loaded screen; so does for loading states back and re-displaying the state exactly; 4). there remains an issue for where the states are saved. Save them to the server side or save it as cookie on the client side? a fashionable way is to save the states to the persistence on the server side; 5). saving states involves saving all the state data from every possible screen the app might have, which is not a simple job; I have studied the example of the ShowCase and found that the app actually loads every possible content screen into a collection and adds them all as history tokens while the app initializes. This is good for a small app but not preferable for a very large web project for sure. Secondly it's found when clicking the reloading button from the browser, actually the app only reloads the content widget with static data, not exactly re-display the previous state. You can see it by clicking the Source Code tab then pressing reload button. Welcome any comments. Thanks, Mike J. Based on the above points, I want to avoid reloading or refreshing and let the page simply stays as it is. It's a lazy person's scenario. It might be totally wrong. But I have not been convinced what's the fatal error in this method. On Mon, May 31, 2010 at 10:53 PM, Ranjan ranjan.n...@gmail.com wrote: It is not possible to avoid refresh(reload) through scripts. The only possible thing is you could display an alert message through the browser which provides the User with option to either stay on the page or leave it. Which is what is done in the CloseHandler in your example script. What federico wants to say is you should use history-tokens to save your states. history Use Refresh, Back, Forward as a feature and not a catastrophe, with the the help of GWT History support. On Jun 1, 6:57 am, Mike Jiang mikej1...@gmail.com wrote: Don't get it. Please show your good design in an understandable style. On Fri, May 28, 2010 at 4:49 PM, federico federico.mona...@gmail.com wrote: bad design. refresh is a feature and you should provide bokmarkable refresh-save pages. On 28 Mag, 20:42, Mike J mikej1...@gmail.com wrote: Hi, I ran into a problem about clicking the reload button on a web browser. My app is a stateful GWT app. Users need to be authenticated for login. After login they can surf on various pages. But users sometimes were used to press the reload button
Re: ClickHandler not called on second click
Something like that should not have gone unnoticed for so long. Could
you post your code snippet?
On Jun 1, 12:07 pm, Olivier Monaco olivier.mon...@free.fr wrote:
Danny,
I had no problem (in dev mode). Here is my test case:
public void onModuleLoad()
{
Button b = new Button(click me);
b.addClickHandler(new ClickHandler()
{
@Override
public void onClick(ClickEvent event)
{
RootPanel.get().add(new Label(clicked));
}
});
RootPanel.get().add(b);
}
What's your test case?
Olivier
On 1 juin, 08:07, Danny Goovaerts danny.goovae...@gmail.com wrote:
I have a button with a ClickHandler. When I move the mouse over the
button and click the button, the ClickHandler is called. When I do no
move the mouse away from the button, the ClickHandler is not called on
any subsequent clicks. I have to move the mouse away from the button
and back. Then the ClickHandler is called when I click again.
To investigate, I have added a MouseDownHandler and a MouseUpHandler.
These are called on subsequent clicks, only the ClickHandler is not
called.
As the focus stays on the button, I have tried hitting the enter key.
This triggers calling the ClickHandler.
I 've tried adding a DeferredCommand to the ClickHandler with a
variaty of actions(remove focus, remove focus and set focus again),
but this does not change anything.
Environment
- GWT 2.0.3
- Vista
- Chrome 6.0.408.1 dev / Firefox 3.5.9/ Internet Explorer 7.0
There are several posts in this forum that describe a similar
behaviour
(e.g.http://groups.google.com/group/google-web-toolkit/browse_thread/threa...)
but none have a solution.
Any idea how to solve this?
Thanks in advance,
Danny
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Dialog Box Dragging?
You could add a handler for MouseUpEvent for the dialog box. And then check the coordinates and relocate if needed. You will have to extend the DialogBox to use the handler. On Jun 1, 8:59 am, Sabbir leo.sh...@gmail.com wrote: When a DialogBox is dragged off the screen and realease ur mouse, everthing gets locked. Cant even see the dialog box to drag back... any solutions? -- 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-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: RootPanel from a Node?
You could actually use node.getAttribute(id); to extract the node.
But I really couldn't understand your use case.
On Jun 2, 12:31 am, markww mar...@gmail.com wrote:
Hi,
Is there a way to get the id of a Node, or to just make a RootPanel
from a Node? I am doing this:
RootPanel panel = RootPanel.get(foo);
Element element = panel.getElement();
for (int i = 0; i element.getChildCount(); i++) {
Node node = element.getChildAt(i);
String id = node.getId(); // does not exist.
// I want to do:
RootPanel curr = RootPanel.get(id);
}
Right now, I need to know all ids in advance, that's the only way a
RootPanel can get() an element from the dom. I can't give it a Node. I
might be missing this completely.
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: How can I prevent from reloading the page when the reload button on browser is clicked?
It is not possible to avoid refresh(reload) through scripts. The only
possible thing is you could display an alert message through the
browser which provides the User with option to either stay on the page
or leave it. Which is what is done in the CloseHandler in your example
script.
What federico wants to say is you should use history-tokens to save
your states.
Use Refresh, Back, Forward as a feature and not a catastrophe, with
the the help of GWT History support.
On Jun 1, 6:57 am, Mike Jiang mikej1...@gmail.com wrote:
Don't get it. Please show your good design in an understandable style.
On Fri, May 28, 2010 at 4:49 PM, federico federico.mona...@gmail.comwrote:
bad design.
refresh is a feature and you should provide bokmarkable refresh-save
pages.
On 28 Mag, 20:42, Mike J mikej1...@gmail.com wrote:
Hi,
I ran into a problem about clicking the reload button on a web
browser.
My app is a stateful GWT app. Users need to be authenticated for
login. After login they can surf on various pages. But users sometimes
were used to press the reload button on the browser to refresh the
page.
The reloading process just bring the screen back to a reboot state,
with all state info lost. That's not what we expect.
The quick solution is, catch the reload event before the browser
sends the reload request to the web server and prevent the browser
from sending it.
I have read the relevant posts in this group and found the useful
info that reload event is equivalent to the Window Closing event. So
in the following code snippet I can catch the event,
Window.addCloseHandler(new CloseHandlerWindow() {
public void onClose(CloseEventWindow event) {
//prevent browser sending the reload request to the
web browser
}
});
But I don't know how I can stop the browser from sending the
reload request to the web server.
Thanks for any help,
Mike J.
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.comgoogle-web-toolkit%2Bunsubs
cr...@googlegroups.com
.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
--
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-tool...@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
