date:20101103

Showing facebook like button using GWT code

2010-11-03 Thread Aditya

hello,
i m trying to embed facbook's like button on page.
it works completely fine in Firefox but it is not shown in Google
chrome and IE 6 and above.
In chrome i tried to dig using inspect element feature so there i
found exactly same set statement from firefox.

i am embedding it in FlextTable,setting html of one cell using
fxtMainTbl.setHTML("http://connect.facebook.net/en_US/
all.js#xfbml=1\">" +

"http://www.demositeurl.com/\"; width=
\"328\">");

how i should make it work in chrome and IE too.

regards,
Aditya

-- 
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: Performance issues with large number of divs

2010-11-03 Thread Daniel Kurka

Hi Chris,

I would suggest to go down another path, based on what ive found to be fast
in GWT and whats not:

Your performance issue seems to derive from two problems: first GWT RPC and
second single DOM manipulations.

To get your datastructures faster into the client I would suggest reading up
on GWT Javascript Overlays and JSON. I recently replaced GWT RPC in a large
project with lots of hased structures and we could drop the average
serialization time in the client from 2 secs to 20 ms. (but be aware of the
Javascript overlay restrictions)

The second thing is DOM operations in general are very expensive and widgets
are event more expensive. I would suggest to go the same way like CellTable
did. Render your content as html inside only one widget. THis will handle
all events. I did this by giving each element inside the markup an id,
events bubbled up to the widget where id figured out which element was
clicked, changed or whatever

You should also take a look at the Cells introduced with celltable and their
Templates...

Hope i could give you some pointers.

-Daniel Kurka





2010/11/2 Jeff Schwartz 

> I believe it would be trivial in that you would only need to add OnClick
> event handlers for each of your divs. You would also have to refactor the
> divs to be actual widgets such as Labels. If you are using UiBinder this
> will be a piece of cake though if you aren't it is only slightly more
> complex.
>
> However, with that said, when you render the view which contains the text
> elements that the user can click on then why don't you also call back to
> your server with a list of those elements and using that list, return
> whatever information pertains to each item in the list. If you return a
> HashMap, for instance, then your OnClick handlers would just need to do a
> get("someKey") on the HashMap to retrieve what ever information is tied to
> the element that the user clicked on. If I were designing this that is how I
> would do it. It is a very "ajaxian" way of doing things like this.
>
> If the list of clickable elements is extremely large (in the thousands) or
> if the data tied to those elements is large then you can defer calling back
> to the server until each item is clicked. In this case you would only return
> the data pertaining to the clicked item from the server back to the client.
> Depending on your server's response time (start up latency, for example)
> this may also be a good solution.
>
> Both of the 2 above  aren't difficult to achieve. GWT actually makes it
> very easy, in fact (GWT is absolutely fantastic!!!). Just one word of
> caution, mark all you data structures as serializable otherwise you will get
> weird errors when you call back to your server or worse, you will get no
> errors but the data transported back to the client will not be right.
>
> Jeff
>
>
> On Tue, Nov 2, 2010 at 9:45 AM, Chris wrote:
>
>> Thanks Jeff. I had thought of that idea, but then I'd somehow need to
>> tie in to the GWT event model so that I could capture when people
>> click on this text, firing through all my presenters and event bus. (I
>> just realised that I missed that bit off the first message).
>>
>> Perhaps though that is fairly trivial?
>> Chris
>>
>>
>> On Oct 30, 1:42 pm, Jeff Schwartz  wrote:
>> > BTW, if the process to generate the content on the server were very
>> > intensive and you wanted to minimize the impact of generating your
>> content
>> > on other users you could break the process up into smaller chunks or
>> work by
>> > making repetitive calls back to the server. How you'd coordinate these
>> calls
>> > with your client would be use-case dependent of course.
>> >
>> > For example, if you are deploying to App Engine you could use tasks &
>> the
>> > datastore to do this:
>> > 1) 1st call back to the server asks to start the process of generating
>> your
>> > content which kicks off a task to do it and when it completes it stores
>> the
>> > generated content as a string in a datastore entity. This could actually
>> use
>> > more than one task but again is  use-case dependent.
>> > 2) onSuccess method of the step 1 above loops call backs to the server
>> to
>> > check if the entity in the table exists. If it does the server returns
>> the
>> > string in the payload otherwise it returns null.
>> > 3)onSuccess method of step 2 above checks for a valid string having been
>> > returned and if true appends it to the dom. If null was returned it
>> would
>> > just continue looping until a valid string were returned.
>> >
>> > While this process is ongoing you could put up an activity ajax
>> indicator so
>> > the user knows that there is something 'cooking'.
>> >
>> > This is a very 'ajaxian' way of doing things.
>> >
>> > Jeff
>> >
>> > On Sat, Oct 30, 2010 at 9:28 AM, Jeff Schwartz > >wrote:
>> >
>> >
>> >
>> >
>> >
>> > > Setting inner text or html for each item will be very, very slow if
>> done on
>> > > the client.
>> >
>> > > I'd generate all the items inside a p

Re: Image Update Memory Leak

2010-11-03 Thread Daniel Kurka

Hi there,

from first glance there seems to be nothing wrong with your code. I think
with IE7/8 there was an issue with the cache control that properly, does the
leak still exists when removing the cache controls?

response.addHeader("Pragma", "no-cache");
response.addHeader("Cache-Control", "no-cache");

- Daniel Kurka

2010/11/1 hermis 

> Hello,
>
> I have written a simple application which fills a FlexTable with a set
> of images. There is a timer which updates the URL of each image every
> second. The URL points to a Servlet which in turn generates a random
> PNG image on its doGet() method and writes it to the response output
> stream. The servlet sets the "Cache-Control" header to "No-Cache".
>
> When I run the webapp in IE7 / 8 the memory gradually increases.
> Leaving it overnight can get it close to 1Gb.
>
> Here is the client code:
>
> #
>
> public class LeakyApp implements EntryPoint
> {
>public static final String IMAGE_SERVLET_NAME = "imageServlet";
>
>public void onModuleLoad()
>{
>leak();
>}
>
>private void leak()
>{
>UrlBuilder urlBuilder = createUrlBuilder();
>
>final FlexTable table = new FlexTable();
>
>final List lstImages = createAndAddImages(5,10 ,table
> );
>
>final String strURL = urlBuilder.buildString();
>
>final Timer timer = new Timer(){
>
>int nCounter = 0;
>
>@Override
>public void run()
>{
>for (Image img : lstImages)
>{
>img.setUrl( strURL + "?" +
> nCounter++) ;
>}
>}
>};
>
>final Button btnStartLeak = new Button("Leak");
>btnStartLeak.addClickHandler( new ClickHandler()
>{
>@Override
>public void onClick(ClickEvent event)
>{
>RootPanel.get().remove( btnStartLeak );
>RootPanel.get().add( table );
>timer.scheduleRepeating( 1000 );
>}
>});
>
>RootPanel.get().add( btnStartLeak );
>}
>
>private List createAndAddImages(int rowCount, int colCount,
> FlexTable table)
>{
>List lstImages = new ArrayList();
>
>for(int row = 0; row{
>for(int col = 0; col{
>Image image = new Image();
>lstImages.add( image );
>table.setWidget(row, col, image);
>}
>}
>
>return lstImages;
>}
>
>private UrlBuilder createUrlBuilder()
>{
>UrlBuilder urlBuilder = null;
>
>if( GWT.isScript() )
>{
>urlBuilder = new UrlBuilder();
>urlBuilder.setHost( Window.Location.getHost() );
>urlBuilder.setPath( Window.Location.getPath() +
> IMAGE_SERVLET_NAME );
>}
>else
>{
>urlBuilder = Window.Location.createUrlBuilder();
>urlBuilder.setPath( IMAGE_SERVLET_NAME );
>}
>
>return urlBuilder;
>}
> }
>
> 
>
> Here is the servlet code:
>
> 
>
> public class ImageServlet extends HttpServlet
> {
>private int nCounter = 0;
>private Font font = new Font("Tahoma", Font.BOLD, 10);
>
>private static Color getRandomColor()
>{
>int r = (int)(Math.random()* 255);
>int g = (int)(Math.random()* 255);
>int b = (int)(Math.random()* 255);
>
>return new Color(r,g,b);
>}
>
>@Override
>protected void doGet ( HttpServletRequest request,
> HttpServletResponse response ) throws IOException
>{
>
>OutputStream out = response.getOutputStream();
>
>response.setContentType("image/png");
>response.addHeader("Pragma", "no-cache");
>response.addHeader("Cache-Control", "no-cache");
>
>ImageIO.write( generateRandomImage(), "png", out );
>
>out.close();
>}
>
>private BufferedImage generateRandomImage()
>{
>return generateRandomImage(80, 80);
>}
>
>private BufferedImage generateRandomImage(int width, int height)
>{
>BufferedImage image = new BufferedImage(width, height,
> BufferedImage.TYPE_INT_ARGB);
>
>Graphics2D g2d = image.createGraphics();
>g2d.setFont(

Re: CellTable as a replacement for incubator ?

2010-11-03 Thread stuckagain

Hi John,

On Nov 2, 6:50 pm, John LaBanca  wrote:
> CellTable isn't a complete replacement of PagingScrollTable, but we put a
> lot of work into the API to make it more clear and extensible.  We'd like to
> create a full featured enterprise CellTable, but we also have a lot of other
> projects going on and don't have the dev time to do it right now.

And what would be the right time ? I agree that the design looks
sound, but scrolling a table is really something that should be
standard in a table. People working on applications don't want to
spend time writing their own table implementation. And currently there
is still no table available that really uses GWT the way it should.
I've seen multiple enterprise projects that went for GXT mostly
because of the mature set of widgets that just look good without much
effort. This is very nice for prototypes and having a short time to
market ... but for bigger applications these widget sets have a lot of
limitations and can not be easily combined with other widget sets. So
after the prototype phase many realize that they need something else.

> in IE8 I see 3-4 seconds 100% CPU just to let the browser calculate
>
> mouse over row highlighting, when showing a lot of rows.
>
> Have you tried looking at it with SpeedTracer?  We tested with large tables
> (100 rows), and the hover code is pretty straight forward.  In past
> applications, we've seen performance problems when hovering due
> to descendent style selectors because of the way they are implemented in
> browser.

I was using the standard google user theme
(com.google.gwt.user.theme.standard.Standard) with no custom styling
at all.

As far as I know speedtracer can not be used in IE ... or did that
change in this release ? I checked with DynaTrace and that one is
telling me that IE is stuck in reflow calculations.

I posted a few messages in GWT contributors a few weeks ago because I
had similar issues on our custom build scrolling table. I was using
decendent styles in their, but after removing them I did not see any
improvement. One thing that did improve the performance by a factor of
10, is to stop using addStyleName or setStyleName in the mouseover and
using the getStyle().setBackgroundColor directly. So maybe it would
already be a big improvement if we could somehow override that way
mouseover and selection styles are applied. Most people only want to
change the background color in mouseover.

Alternatively their could be some changes in CssResource that would
allow us to put some styling code in the CssResource instead, which
would keep a better separation between the presentation and view.

Or we could just wait for IE9 to become the standard browser on
Windows... but in the banking sector many of our clients are reluctant
to move away from IE6 since they still have a lot of sites that only
work in that browser and they don't want to spend money on migrating
these applications.

> And you have a CellTable that is NOT myRandomWidget, then changing the hover
> style of the row will cause IE to walk up from every TD in the CellTable
> trying to match the style definition.  In the degenerate case, where
> CellTable is not myRandomWidget, this means walking up to the body element.
>  This is a native browser implementation, and the only solution is to avoid
> descendent style selectors.

I know, I never use descendant styles only really simple styles, with
the expense that I need to have a large set of stylenames, but with
CssResource all this is very easy to manage and group. So that is
really a very good feature of GWT.

David

-- 
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.

Spring Roo and GWT

2010-11-03 Thread Stefan Bachert

Hi,

does anyone have the luck, to get a non trivial case to run with
Spring Roo 1.1.0?

I tried the modified clinic sample, but it results in a loading screen
doing NOTHING.
(Remove Calendar, change boolean to type java.lang.Boolean)

At the moment it seems that Spring Roo with GWT is (still) a waste of
time.

Stefan Bachert
http://gwtworld.de

-- 
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: Reload CellTable data

2010-11-03 Thread Geoffrey De Smet

I use AsyncDataProvider, but that one doesn't have a refresh()
method. I made an issue:
http://code.google.com/p/google-web-toolkit/issues/detail?id=5533

Op 02-11-10 18:42, John LaBanca schreef:

  Thomas
is correct on both accounts.  cellTable.setVisibleRangeAndClearData(cellTable.getVisibleRange(), true);
  will force a RangeChangeEvent to fire to the backend, but
  really your backend should be pushing the new data into the
  CellTable.  For example, if you use ListDataProvider you can
  call ListDataProvider#refresh() to push the data back into the
  views.

  Thanks,
  John LaBanca
  jlaba...@google.com

  On Tue, Nov 2, 2010 at 12:49 PM, Thomas
Broyer 
wrote:

On 2 nov, 17:07, Geoffrey De Smet 
wrote:
> I 'd like to add a button to reload the CellTable when
it's pushed,
> but I can only find:
> - cellTable.redraw(); // Doesn't reload the data from
the backend
> - simplePager.firstPage(); // I don't want it to change
the page
>
> Is there an easy way to do something like
cellTable.reload() or
> cellTable.refresh() ?

  Maybe:
cellTable.setVisibleRangeAndClearData(cellTable.getVisibleRange(),
  true);

  http://google-web-toolkit.googlecode.com/svn/javadoc/2.1/com/google/gwt/user/cellview/client/AbstractHasData.html#setVisibleRangeAndClearData(com.google.gwt.view.client.Range,
  boolean)

  But I think the expected use is to do it in your "model"
  rather than
  the "view" (CellTable), where the "model" (or presenter, or
  whatever)
  will fetch the data from the backend (maybe using
  getVisibleRange() to
  filter it) and call setRowData() on the CellTable to update
  it.

  --
  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-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.

-- 
With kind regards,
Geoffrey De Smet

-- 
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: CellTable as a replacement for incubator ?

2010-11-03 Thread Geoffrey De Smet

Op 03-11-10 08:58, stuckagain schreef:

Hi John,

On Nov 2, 6:50 pm, John LaBanca wrote:

CellTable isn't a complete replacement of PagingScrollTable, but we put a
lot of work into the API to make it more clear and extensible. We'd like to
create a full featured enterprise CellTable, but we also have a lot of other
projects going on and don't have the dev time to do it right now.

And what would be the right time ? I agree that the design looks
sound, but scrolling a table is really something that should be
standard in a table. People working on applications don't want to
spend time writing their own table implementation. And currently there
is still no table available that really uses GWT the way it should.
I've seen multiple enterprise projects that went for GXT mostly
because of the mature set of widgets that just look good without much
effort. This is very nice for prototypes and having a short time to
market ... but for bigger applications these widget sets have a lot of
limitations and can not be easily combined with other widget sets. So
after the prototype phase many realize that they need something else.

I also get the feeling that CellTable is the only scalable implementation,
but it lacks a couple of important features to surpass the other and
draw all development to itself,

such as:
- header sorting
- column resizing
- column picker

Extracting those extra features from bikeshed works clunky: there's no
decent integration.

Here's my implementation (ASL license):

http://anonsvn.jboss.org/repos/labs/labs/jbossrules/trunk/drools-guvnor/src/main/java/org/drools/guvnor/client/table/
As you can see I had to create a ColumnMeta class (in the ColumnPicker)
to wrap Column because the Column class doesn't have a "visible" property.

--
With kind regards,
Geoffrey De Smet

--
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.

1 2 >

1 - 100 of 104 matches

Mail list logo