date:20090910

2009/9/10 Alexander Cherednichenko lex...@gmail.com


 That's true; I was also thinking of redirect.

 Also, this is good for non-js browsers. Links users would see it OK,
 which is really valuable for me.

 Although, does not google ban for body onload='javascript:
 widnow.location= http://newsite?aaa'/ ?


Maybe - I don't use that. It would seem a bit harsh if they do. But Google
is following IBM's FUD route on things like that.


 This sounds pretty much like a doorway page.
 I'm really interested in how searchers treat this.

 In official release what's they say about cloacking:
 
  So what's an honest web designer to do? The only hard and fast rule
 is to show Googlebot the  exact same thing as your users. If you
 don't, your site risks appearing suspicious to our search algorithms.
 This simple rule covers a lot of cases including cloaking, JavaScript
 redirects, hidden text, and doorway pages.


My site does show the non-JS Googlebot exactly what a non-JS user would see.
If Google decide to develop a JS-enabled Googlebot, it will see what a
JS-enabled user will see. It's not my fault if they are not technically
savvy enough to do it. Not only that, JS-users get *exactly* the same
content as non-JS-users (albeit with menus and demos and stuff)

If they *don't* allow me to do this, then effectively they are banning
anyone who wants to be listed from using JavaScript, and how many sites does
that leave them?


 And our engineers have
 gathered a few more practical suggestions:
 
 (taken from http://googlewebmastercentral.blogspot.com/2007/07/best-
 uses-of-flash.html,
 though it's old)

 Unclear moment for me is that what do they mean saying 'exact same
 thing as your users. '. If it is same content (like compared by user)
 - your method would work, as you load the SAME page as the one shown
 to bot.


Cloaking is giving a different to a bot from the page you give to a user.
They cannot expect their non-enabled bot to get the same as an enabled user
or, for example, using Flash and Java applets and images of text and video
and audio would earn you a ban as well.


 But textually - the contents are different.


No they are not


 Bot may think that you're
 blindly redirecting the user to strange page with the only 1
 javascript file inclusion and no content at all.


But I don't. My index page is used to pick up the home page text.



 Maybe, something new has happened which allows more SEO methodics and
 i missed this?

 Thanks for the point with redirect,
 Alex.



From a purely practical point of view, if I can't do this and they do ban me
and my site isn't listed, then how much worse off am I than if my site is
not being listed because I don't have any content that the bots can see?

Less than 5% of my traffic comes from search engines anyway - about 15% is
from referring sites, and over 80% is direct. It wouldn't be a great loss if
I did get banned. In fact, the amount of free advertising and links I'd get
from the news articles I could generate and the resulting knock-on news
coverage, social network and blog activity and links ('Google Bans Site For
Using Google Web Toolkit' - that would get picked up) it would probably make
it a positive blessing if all I wanted was traffic.

My site has been doing this for nearly 3 years and I described the whole
setup here on this forum over 2 years ago. No-one official said it *wasn't*
OK.

Because Google use IBM's FUD approach, you won't see anyone from Google say
that this is OK to do (AFAIK they still haven't publicly said that
underscores are used as work delimiters in file names, and how uncontentious
and long-running is that?) but if you are doing something that is
unequivocally wrong, they usually tell you.

Watch this space.

Ian

http://examples.roughian.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: seo and google web toolkit

'word delimiter' not 'work delimiter' - I think I was subconciously longing
for a coffee break.

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

Why does this test fail ?

2009-09-10 Thread hjo1620


CustomerComponent extends Composite,
I do panel.add(widget) for all my widgets,
and then do initWidget(panel), in the constructor.

However this GWTTestCase test fails:

public void testShouldAttachAllWidgets() throws Exception {
CustomerComponent component = new CustomerComponent();
assertNotNull(component);
assertTrue(component.hasWidget());
LinkedHashMapString, Widget widgets =
component.getWidgets();
IteratorWidget it = widgets.values().iterator();
while (it.hasNext()) {
assertTrue(it.next().isAttached());
}
}


What am I missing ?
Should they not have been attached by the panel.add(widget) ?

--~--~-~--~~~---~--~~
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: Cookies not available in Hosted Mode

2009-09-10 Thread 徐恒飞

you mean session?
at you project :war/WEB-INF/appengine-web.xml
add this:
sessions-enabledtrue/sessions-enabled


2009/9/10 Anca ai...@computervoice.ro


 Hi,

 When I run my GWT application in Hosted Mode, I'm unable to retrieve
 cookies that I previously set. I also compiled the application using
 Compile/Browse button in the Hosted Mode, run it in Chrome and the
 result is the same: i couldn't even find them in the browser's list of
 cookies.


 But, if i deployed the application on Tomcat, I could see that the
 cookies were well set and retrieved. I want to be able to do the same
 in Hosted Mode. Is it possible?


 Thanks,
 Anca

 


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

Using GWT within Jx components in Firefox

2009-09-10 Thread Ganaga


Hello,

I'm not sure exactly whether this thread is about a Jx or GWT issue.

In a html page, I try to display a GWT div within a Jx component.

The following example works fine with IE but not Firefox where the
panel is empty and the GWT divs are not resolved when I inspect the
page with Firebug.

p1 = new Jx.Panel({label: 'My Title 1'});
p1.content.id = 'gwt_id_1';
var p2 = new Jx.Panel({label: 'My Title 2'});
p2.content.id = 'gwt_id_2';
var pm = new Jx.PanelManager('PanelPane', [p1, p2]);

However, if I do:

new Jx.Layout('gwt_id_1', {top: 60, bottom: 22, width: 250, left:
null});

Then the div with id gwt_id_1 is resolved correctly in Firefox (and
also IE).

Thanks in advance if you see anything that looks wrong with the code.
Might be a bug in Firefox?

Cheers,
Ganael
--~--~-~--~~~---~--~~
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 RPC Hibernate - again and again

2009-09-10 Thread Kango_V


fyi:  I have posted a feature request into Hibernates Jira asking for
a new entity mode be added.

Current Hibernate supports the current entity modes.

XML
POJO
MAP

This means that entities can be retrieved and updated again in these
formats.  Now, if we could just add JSON to this list.
Having JSON would mean you would be able to get an object graph out of
hibernate as JSON, send it down using GWT, update it and send it back
to Hibernate.

This would solve many, many issues.  I think it requires a new
Tuplizer implementation for Hibernate.  I meight even have a go at
this when I have time.

What do you all think?

Here's the Jira issue.  Go vote

http://opensource.atlassian.com/projects/hibernate/browse/HHH-4040

--
Darren.



On Sep 9, 8:29 pm, Thomas Holmes thomas.j.hol...@gmail.com wrote:
 Yes, absolutely 100% I do have Hibernate working with Annotations!
 The Hibernate DAO's and POJO's have all been Unit Tested and work
 perfectly 100%.
 And we are using Spring with the DAO's and POJO's defined in the
 applicationContext.xml file.
 There are NO hibernate.cfg.xml and Object.hm.xml files defined, and we
 don't seem to need them since all that is defined within the
 applicationContext.xml file.

 Yes, I have learned that I can't call Spring classes from within GWT.

 I agree with you, I need to create some DTO classes that handle the
 wire transfer between the UI and the database.
 I gather from reading that the DTO custom classes have to implement
 isSerializable and collections are ArrayList, String array, Vector,
 HashMap, and HashSet.

 So, I'm looking now for examples on when exactly the Service calls the
 backend database ...
 The GWT-RPC Service at some point either has to call the DAO's to
 create, retrieve/fetch, update, delete data.
 Where and how that happens I am looking for.

 I looked at Gilead and the samples, and they use Hibernate.cfg.xml and
 the Object.hbm.xml ... which I don't have in this application.
 So, if I found an example of Gilead with Spring, that would help.

 Thanks for the help, I do appreciate it!   :-)

 Tom

 On Sep 9, 1:38 pm, Robnauticus- robnauti...@gmail.com wrote:



  Hello Thomas,

  Do you have Hibernate working with annotations?  If you don't have an
  cfg.xml file set up and mapping files, Hibernate will not work.  You
  are also attempting to call spring classes inside of GWT which will
  not work.

  I created a Domain package that serves as the in-between for your
  shared client/server data classes that are passed via RPC.

  In your .gwt.xml file for your project you need to add source
  path=domain / to the file to tell GWT that it can use those classes
  as well as the client package.

  Now you have the problem with serializing Hibernate object from client/
  server.  Gilead is what I am using, there are other ways to do this
  but Bruno did a great job creating the lib.  Basically the Hibernate
  objects that are generated are too complex to be converted to js
  objects so Gilead takes the nasty work out of the conversion.

  Take a look at which core java libraries can be converted to js by
  GWT.  Anything else will fail for the most part so don't try to
  include it in your client code.  The server package will allow you to
  do anything you want java-wise.

  HTH,
  Rob

  On Sep 9, 8:35 am, Thomas Holmes thomas.j.hol...@gmail.com wrote:

   I get the idea that ouside packages need to be include in the module ...
   but of course I am going to include code from outside packages 
   Hibernate and Spring jars are outside ... and there is no source code:

   so, here are some errors;
   [ERROR] Line 5: The import org.springframework.orm cannot be resolved
   [ERROR] Line 10: HibernateDaoSupport cannot be resolved to a type
   [ERROR] Line 14: The method getHibernateTemplate() is undefined for the 
   type
   TestDaoImpl

   So, I added this to my StockWatcher.gwt.xml:
    !-- Other module inherits      --
     inherits
   name='org.springframework.orm.hibernate3.support.HibernateDaoSupport'/

   But now I get:
   [TRACE] Loading inherited module
   'org.springframework.orm.hibernate3.support.HibernateDaoSupport'
   [ERROR] Unable to find
   'org/springframework/orm/hibernate3/support/HibernateDaoSupport.gwt.xml' 
   on
   your classpath;
   could be a typo, or maybe you forgot to include a classpath entry for
   source?

   And then the application won't run at all ..

   On Wed, Sep 9, 2009 at 6:49 AM, Raphael André Bauer 

   raphael.andre.ba...@gmail.com wrote:

On Tue, Sep 8, 2009 at 10:17 PM, Thomas 
Holmesthomas.j.hol...@gmail.com
wrote:

 Would you have some sample code that I could see ... or a link to
 some.

 I'm going to continue looking through my book, and use their example
 that uses the Command Pattern.

 I am getting tons of errors because my DAO's and POJO's are in another
 package, so I was working with GWT Modules to try and make that work.
 I finally gave that up and tried to move

Re: Why does this test fail ?

2009-09-10 Thread Thomas Broyer




On 10 sep, 13:40, hjo1620 hjo1...@gmail.com wrote:
 CustomerComponent extends Composite,
 I do panel.add(widget) for all my widgets,
 and then do initWidget(panel), in the constructor.

 However this GWTTestCase test fails:

 public void testShouldAttachAllWidgets() throws Exception {
             CustomerComponent component = new CustomerComponent();
             assertNotNull(component);
             assertTrue(component.hasWidget());
             LinkedHashMapString, Widget widgets =
 component.getWidgets();
             IteratorWidget it = widgets.values().iterator();
             while (it.hasNext()) {
                         assertTrue(it.next().isAttached());
             }

 }

 What am I missing ?
 Should they not have been attached by the panel.add(widget) ?

No, after panel.add(widget), all widget has is a parent
(widget.getParent() != null).

Being attached in GWT means you're attached to the *document* (i.e.
by walking the parents of the widget's element, you'll find the body
and then the html elements of $doc).
In other words, if component (hence panel) isn't itself attached, its
children (widget) can't be attached.
For your test to pass, you'd have to do something like RootPanel.get
().add(component); this would attach component (because a RootPanel is
a wrapper around an existing, attached, element, it is inherently
attached, so when you add(component), component is automatically
attached too; as well as its children)
Well, actually, such a test would actually test GWT's behavior rather
your component's behavior; IMO your test should rather assertSame
(component, it.next().getParent()).

...assuming the assertion failure is in the latest assertTrue in your
code, of course...
--~--~-~--~~~---~--~~
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: Translate localised messages in GWT app

2009-09-10 Thread mars1412


 We adandoned google static i18n because of compile time -  we have
 huge app, and having 6 languages * 5 browsers = 30 different bundles
 was killer shot.

I don't get that point:
 * during development you use hosted mode
 * and if you wish to test something specific, you only
   need to compile the one permutation your interessted in:
   and in the case of one permutation the compile-time will
   not be much better in the dynamic approach
 * and once-in-a-while when you want to release a version,
   you'll build the full set of permutations, test them and
   deploy them
   but since this is something you do infrequently
   so the compile time shouldn't really matter

This can be achieved with Generators - you need to create JSON-like
file with all strings, then load in to the client, then (through JSNI)
give access to these loaded strings. That's all.
I guess you could.
with the exception of inlining the translated strings:
but I think this will not harm client-side performance too much.

so to recap the advantages you want to get:
 * faster compile time
 * immediate display of translated strings
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Seriously getting beyond my capabilities with GWT....

2009-09-10 Thread John V Denley


Is there anyone out there who would l like to help me out? Its
ultimately a commercial product, but Im really not a programmer
anymore, I used to know C, but all this webstuff is hurting my brain!

My current problem is that Ive managed to get my application to create
entries in the datastore (I know thats a bit of a GAE area) but the
problem Im having now is retrieving the data. Im storing an
appointment into the datastore, but now when trying to retrieve it, I
need to get several variables back, so far I can only get strings or
string arrays back.But I really need to retrieve the date back now, as
its stored as a UTC on the server, and of course that means that when
if I pass it back as a string and parse it then the time is wrong for
my local timezone (I know this is a horrible way to do it, but i was
just trying to get something quick and dirty up and running, and then
work out later how to do it properly!)

I have tried to change my server calls so they use a more complex data
type (Appointment class) but the compiler is now giving me a ton of
error messages which i dont understand (basically lots of i cant
resolve that type kinds of messages)

Im a bit lost and could use some more expert help with this, but cant
seem to find anyone willing to put in a bit of time and effort to help
me out without wanting payment!!!

Can anyone help me please?!
--~--~-~--~~~---~--~~
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: Hosted mode browser to permit self-signed server certs?

2009-09-10 Thread Mike Grayson

Thanks, I'll take a look.

On Thu, Sep 10, 2009 at 2:58 AM, Paul Robinson ukcue...@gmail.com wrote:


 Have you tried OOPHM? (assuming it's the browser itself that's causing
 your problem)


 Mike Grayson wrote:
  Hi all,
 
  I'm trying to use GWT-RPC in hosted mode to make client requests
  against a remote (Weblogic) server.  The remote server only accepts
  HTTPS connections and identifies itself with a self signed cert.
  Unfortunately it appears the hosted mode browser doesn't accept self
  signed server certs.  (The server uses a self signed cert because it's
  a test/dev box, not a full on production box.)
 
  Any way I can work around this?
 
  Cheers,
  Mike

 


--~--~-~--~~~---~--~~
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: seo and google web toolkit

At the end of the day, I'm not trying to con them and get them to see
something different from my ordinary visitors - actually, the opposite - I'm
trying to get them to see what my ordinary visitors see, rather than a blank
page.
Even if they banned me, I'd still do it for accessibility reasons, the
reduced initial download size, and the advantage of not having to recompile
if I make a correction or addition to a page.

Download size and ease of writing copy in HTML (rather than Java strings)
was the original reason - lack of recompile was a bonus, and after that, it
occurred to me I could come up with a 'ghost' site which would allow non-JS
users, SEO and screen readers to access the site.

Ian

http://examples.roughian.com


2009/9/10 Alexander Cherednichenko lex...@gmail.com


 nice answer. big thanks :)


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---

Re: Script tag in GWT

2009-09-10 Thread Senshi


I have equal problem
IE7 not draw this
texto = new HTML();
texto.setHTML(scriptbuildRow();/script);
panel.add(texto);

Please help
--~--~-~--~~~---~--~~
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: URL and GET method

2009-09-10 Thread ThomasWrobel


Window.Location.getParameter(FOO);

If I remember correctly.

On Sep 10, 5:02 pm, Pion onlee2...@gmail.com wrote:
 How do I retrieve the value of FOO parameter using GWT of the
 following: http://localhost:8080/get?FOO=BAR; ?

 Thanks in advance for your help.
--~--~-~--~~~---~--~~
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 RPC Hibernate - again and again

2009-09-10 Thread Robnauticus-


Another thing to look at is GWT-SL it has Spring, hibernate, Gilead
and many other tools for integration.


Rob

On Sep 9, 12:29 pm, Thomas Holmes thomas.j.hol...@gmail.com wrote:
 Yes, absolutely 100% I do have Hibernate working with Annotations!
 The Hibernate DAO's and POJO's have all been Unit Tested and work
 perfectly 100%.
 And we are using Spring with the DAO's and POJO's defined in the
 applicationContext.xml file.
 There are NO hibernate.cfg.xml and Object.hm.xml files defined, and we
 don't seem to need them since all that is defined within the
 applicationContext.xml file.

 Yes, I have learned that I can't call Spring classes from within GWT.

 I agree with you, I need to create some DTO classes that handle the
 wire transfer between the UI and the database.
 I gather from reading that the DTO custom classes have to implement
 isSerializable and collections are ArrayList, String array, Vector,
 HashMap, and HashSet.

 So, I'm looking now for examples on when exactly the Service calls the
 backend database ...
 The GWT-RPC Service at some point either has to call the DAO's to
 create, retrieve/fetch, update, delete data.
 Where and how that happens I am looking for.

 I looked at Gilead and the samples, and they use Hibernate.cfg.xml and
 the Object.hbm.xml ... which I don't have in this application.
 So, if I found an example of Gilead with Spring, that would help.

 Thanks for the help, I do appreciate it!   :-)

 Tom

 On Sep 9, 1:38 pm, Robnauticus- robnauti...@gmail.com wrote:



  Hello Thomas,

  Do you have Hibernate working with annotations?  If you don't have an
  cfg.xml file set up and mapping files, Hibernate will not work.  You
  are also attempting to call spring classes inside of GWT which will
  not work.

  I created a Domain package that serves as the in-between for your
  shared client/server data classes that are passed via RPC.

  In your .gwt.xml file for your project you need to add source
  path=domain / to the file to tell GWT that it can use those classes
  as well as the client package.

  Now you have the problem with serializing Hibernate object from client/
  server.  Gilead is what I am using, there are other ways to do this
  but Bruno did a great job creating the lib.  Basically the Hibernate
  objects that are generated are too complex to be converted to js
  objects so Gilead takes the nasty work out of the conversion.

  Take a look at which core java libraries can be converted to js by
  GWT.  Anything else will fail for the most part so don't try to
  include it in your client code.  The server package will allow you to
  do anything you want java-wise.

  HTH,
  Rob

  On Sep 9, 8:35 am, Thomas Holmes thomas.j.hol...@gmail.com wrote:

   I get the idea that ouside packages need to be include in the module ...
   but of course I am going to include code from outside packages 
   Hibernate and Spring jars are outside ... and there is no source code:

   so, here are some errors;
   [ERROR] Line 5: The import org.springframework.orm cannot be resolved
   [ERROR] Line 10: HibernateDaoSupport cannot be resolved to a type
   [ERROR] Line 14: The method getHibernateTemplate() is undefined for the 
   type
   TestDaoImpl

   So, I added this to my StockWatcher.gwt.xml:
    !-- Other module inherits      --
     inherits
   name='org.springframework.orm.hibernate3.support.HibernateDaoSupport'/

   But now I get:
   [TRACE] Loading inherited module
   'org.springframework.orm.hibernate3.support.HibernateDaoSupport'
   [ERROR] Unable to find
   'org/springframework/orm/hibernate3/support/HibernateDaoSupport.gwt.xml' 
   on
   your classpath;
   could be a typo, or maybe you forgot to include a classpath entry for
   source?

   And then the application won't run at all ..

   On Wed, Sep 9, 2009 at 6:49 AM, Raphael André Bauer 

   raphael.andre.ba...@gmail.com wrote:

On Tue, Sep 8, 2009 at 10:17 PM, Thomas 
Holmesthomas.j.hol...@gmail.com
wrote:

 Would you have some sample code that I could see ... or a link to
 some.

 I'm going to continue looking through my book, and use their example
 that uses the Command Pattern.

 I am getting tons of errors because my DAO's and POJO's are in another
 package, so I was working with GWT Modules to try and make that work.
 I finally gave that up and tried to move that code closer to the
 Client directory ... and there a still a ton of errors.

 The most bothersome was in my UserDaoImpl where I have a
 getHibernateTemplate method, and it says that the source code isn't
 there.
most likely this code is referenced by a module. some ideas:
- check by which module it is referenced (if you have more than one)
and make sure it is inherited by that module.
- make sure it is under the /client/ directory, so that the gwt
crosscompiler can find the sourcecode.
- make sure the file has no external references (import xyz) that are
not in the client

Re: URL and GET method

But you probably don't want to be doing that because if anything between the
? and the first # changes, your whole app will reload from scratch and
you'll lose all state..

Ian

http://examples.roughian.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
-~--~~~~--~~--~--~---

Problem with call function external javascript

2009-09-10 Thread Senshi


Hi
I have Problem with call function external javascript in IE7 not draw
this in reload html page

texto = new HTML();
texto.setHTML(scriptbuildRow();/script);
panel.add(texto);

no call function ..??

...no show alert??
texto = new HTML();
texto.setHTML(scriptalert(\Hello\);/script);
panel.add(texto);

Please help
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

How to get mouse x/y outside of a click event?

2009-09-10 Thread darkflame


Id like to know the current mouse x/y, relative to an element, at an
arbitrary point in my code.
(in this specific case during a scroll wheel event, but I might want
it elsewhere later)

How would I do this?
I'm sure theres a simple function I'm missing, but it just escapes
me :-/


--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---

Re: URL and GET method

2009-09-10 Thread Lothar Kimmeringer


Ian Bambury schrieb:
 But you probably don't want to be doing that because if anything between
 the ? and the first # changes, your whole app will reload from scratch
 and you'll lose all state..

So you have to use http://www.example.com/get#?[querystring]
to avoid that effect?


Regards, Lothar

--~--~-~--~~~---~--~~
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: CSS Theme File - Disabled

2009-09-10 Thread ThomasWrobel


You can always just comment them out;

 !-- --

On Sep 10, 4:19 am, josivan josiva...@gmail.com wrote:
 tks... :)
 other framework have enabled this feature :)

 j.

 On 7 set, 06:21, Thomas Broyer t.bro...@gmail.com wrote:



  On 7 sep, 02:40, josivan josiva...@gmail.com wrote:

   Hi, my application has currently many files for CSS oftheme.
   My doubt! Is possible disabledtheme(css) file generation?
   I need only my css file, where I'm setting css rules (gwt-*)
   inclusive.

  Just remove any inherit name=com.google.gwt.user.theme.XXX / line
  from your gwt.xml file(s)
--~--~-~--~~~---~--~~
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: URL and GET method

I don't know - it depends what you are trying to do.
You probably want to be using history in some way or passing parameters as
JS variables or JSON or...

Ian

http://examples.roughian.com


2009/9/10 Lothar Kimmeringer j...@kimmeringer.de


 Ian Bambury schrieb:
  But you probably don't want to be doing that because if anything between
  the ? and the first # changes, your whole app will reload from scratch
  and you'll lose all state..

 So you have to use http://www.example.com/get#?[querystring]
 to avoid that effect?


 Regards, Lothar

 


--~--~-~--~~~---~--~~
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: Aborting a server request

2009-09-10 Thread Simal


Thanks Jay.. This is great help to me!

- Simal

On Sep 9, 4:47 pm, jay jay.gin...@gmail.com wrote:
 In your async interface, rather than declaring the method to return
 void, have it return a Request. You can then use the Request::cancel()
 method.

 jay

 On Sep 9, 1:10 pm,Simalsimalhance...@gmail.com wrote:

  Sorry I didn't mention that.. I'm using GWT-RPC.

  -Simal

  On Sep 9, 4:09 pm, Ian Petersen ispet...@gmail.com wrote:

   On Wed, Sep 9, 2009 at 1:01 PM,Simalsimalhance...@gmail.com wrote:
I was wondering if there is a way to cancel an ongoing server request
(from client side) and if we get handles to our server requests at
all..

   Yes.  Are you talking GWT-RPC or hand-rolled requests?

   Ian


--~--~-~--~~~---~--~~
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: MVP HasClickHandler

2009-09-10 Thread fonghuangyee


Thanks for ur advise.
How about if i define a interface ( View Listener ), then my presenter
implement the View Listener?

Example :

public class MyView extend Composite implement MyPresenter.View {

  public interface Listerner {

 public void onEdit(String id);
  }

  .
  .

  Listener listener;

  // a List of Button here
  button.addClickHandler(new ClickHandler(){

 public void onClick(ClickEvent event){
 listener.onEdit(id);
 }
  );

}

public class MyPresenter implement MyView.Listener {

  public interface View {

  }

  public void onEdit(String id){
   // Do something here.
  };
}

Please correct me if i am following the wrong way.
Thanks.

On Sep 7, 8:32 am, Jason A. Beranek jason.bera...@gmail.com wrote:
 One approach I've used is to put some logic in the View to forward a
 different event than the purely GUI events to the Presenter. For
 example, if you have a table or list of items which can be clicked,
 and a click signifies selection of an item, use HasSelectionHandlers()
 in the View, and translate in the View which item is selected by the
 click. This seems to work for selection use cases, but it makes your
 View in theMVPmore Supervising Controller (http://martinfowler.com/
 eaaDev/SupervisingPresenter.html) than Passive View (http://
 martinfowler.com/eaaDev/PassiveScreen.html).

 If you were to need separate handling for each list item being
 clicked, then you are likely looking at a Presenter per list item or
 at having the View include a factory to add list items and return
 handlers (i.e., HasClickHandlers addListItem() ). Any of these
 approaches will work, it just depends on what you are looking to do
 with each click handler.

 V/r,

 Jason

 On Sep 6, 3:19 am, fonghuangyee fonghuang...@gmail.com wrote:



  Hihi ,
  After i go through so manyMVPexample, i found that we always use
  presenter to get thoseHasClickHandlerfrom Display( Or View) to do
  some action. This way works nice for static clickable action, but if
  we have some dynamic button ( example a table listing with a list of
  clickable  action ), then i have to get a list ofHasClickHandler
  from
  display? and every time i add new row to the table listing, i have to
  take care of the handler action, quite troublesome.
  any advice?

  Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---

Re: URL and GET method

2009-09-10 Thread Pion


Thanks. Window.Location.getParameter(FOO);  works.

What does the # mean?
I use http://localhost:8080/get?FOO=BAR#;  but
Window.Location.getParameter(FOO) does not pick up the # sign.
How do I retrieve the # as well?

Again, thanks.

On Sep 10, 8:17 am, Ian Bambury ianbamb...@gmail.com wrote:
 But you probably don't want to be doing that because if anything between the
 ? and the first # changes, your whole app will reload from scratch and
 you'll lose all state..

 Ian

 http://examples.roughian.com
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---

Re: GWT RPC Hibernate - again and again

2009-09-10 Thread jdwy


Hey Thomas,

A little late to the conversation, but I just want to say that I don't
think the ToCollege code (or structure) should require a
hibernate.cfg.xml. It should be ok to annotate the models that live in
your client directory. That wasn't the case with earlier GWT because
the annotations broke if it couldn't find the annotation package
within client/, but I believe that's fixed.

I just want to make sure that your UserDaoImpl and getHibernateTemplate
() methods are not in the client package. That's definitely not what
you want. Those should all be in the server/ package. inherits
name='org.springframework.orm.hibernate3.support.HibernateDaoSupport'/
 is definitely not going to work.

Rather than bring hibernate the pattern that the book espouses is to
leave all of that on the server and communicate solely via commands.

Annotated Domain objects  commands in the client package. DAOs 
CommandProcessing classes in the server package.

gl

-Jeff Dwyer

On Sep 10, 11:15 am, Robnauticus- robnauti...@gmail.com wrote:
 Another thing to look at is GWT-SL it has Spring, hibernate, Gilead
 and many other tools for integration.

 Rob

 On Sep 9, 12:29 pm, Thomas Holmes thomas.j.hol...@gmail.com wrote:



  Yes, absolutely 100% I do have Hibernate working with Annotations!
  The Hibernate DAO's and POJO's have all been Unit Tested and work
  perfectly 100%.
  And we are using Spring with the DAO's and POJO's defined in the
  applicationContext.xml file.
  There are NO hibernate.cfg.xml and Object.hm.xml files defined, and we
  don't seem to need them since all that is defined within the
  applicationContext.xml file.

  Yes, I have learned that I can't call Spring classes from within GWT.

  I agree with you, I need to create some DTO classes that handle the
  wire transfer between the UI and the database.
  I gather from reading that the DTO custom classes have to implement
  isSerializable and collections are ArrayList, String array, Vector,
  HashMap, and HashSet.

  So, I'm looking now for examples on when exactly the Service calls the
  backend database ...
  The GWT-RPC Service at some point either has to call the DAO's to
  create, retrieve/fetch, update, delete data.
  Where and how that happens I am looking for.

  I looked at Gilead and the samples, and they use Hibernate.cfg.xml and
  the Object.hbm.xml ... which I don't have in this application.
  So, if I found an example of Gilead with Spring, that would help.

  Thanks for the help, I do appreciate it!   :-)

  Tom

  On Sep 9, 1:38 pm, Robnauticus- robnauti...@gmail.com wrote:

   Hello Thomas,

   Do you have Hibernate working with annotations?  If you don't have an
   cfg.xml file set up and mapping files, Hibernate will not work.  You
   are also attempting to call spring classes inside of GWT which will
   not work.

   I created a Domain package that serves as the in-between for your
   shared client/server data classes that are passed via RPC.

   In your .gwt.xml file for your project you need to add source
   path=domain / to the file to tell GWT that it can use those classes
   as well as the client package.

   Now you have the problem with serializing Hibernate object from client/
   server.  Gilead is what I am using, there are other ways to do this
   but Bruno did a great job creating the lib.  Basically the Hibernate
   objects that are generated are too complex to be converted to js
   objects so Gilead takes the nasty work out of the conversion.

   Take a look at which core java libraries can be converted to js by
   GWT.  Anything else will fail for the most part so don't try to
   include it in your client code.  The server package will allow you to
   do anything you want java-wise.

   HTH,
   Rob

   On Sep 9, 8:35 am, Thomas Holmes thomas.j.hol...@gmail.com wrote:

I get the idea that ouside packages need to be include in the module ...
but of course I am going to include code from outside packages 
Hibernate and Spring jars are outside ... and there is no source code:

so, here are some errors;
[ERROR] Line 5: The import org.springframework.orm cannot be resolved
[ERROR] Line 10: HibernateDaoSupport cannot be resolved to a type
[ERROR] Line 14: The method getHibernateTemplate() is undefined for the 
type
TestDaoImpl

So, I added this to my StockWatcher.gwt.xml:
 !-- Other module inherits      --
  inherits
name='org.springframework.orm.hibernate3.support.HibernateDaoSupport'/

But now I get:
[TRACE] Loading inherited module
'org.springframework.orm.hibernate3.support.HibernateDaoSupport'
[ERROR] Unable to find
'org/springframework/orm/hibernate3/support/HibernateDaoSupport.gwt.xml'
 on
your classpath;
could be a typo, or maybe you forgot to include a classpath entry for
source?

And then the application won't run at all ..

On Wed, Sep 9, 2009 at 6:49 AM, Raphael André Bauer 

raphael.andre.ba...@gmail.com wrote:

Re: How to get mouse x/y outside of a click event?

2009-09-10 Thread Thomas Broyer




On 10 sep, 17:22, darkflame darkfl...@gmail.com wrote:
 Id like to know the current mouse x/y, relative to an element, at an
 arbitrary point in my code.
 (in this specific case during a scroll wheel event, but I might want
 it elsewhere later)

 How would I do this?
 I'm sure theres a simple function I'm missing, but it just escapes
 me :-/

No, there's no mean to ask the mouse where she is; your only
option (afaict) is to listen to mousemove events and store the
coordinates in global variables that you can then read from another
event loop iteration.
--~--~-~--~~~---~--~~
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: URL and GET method

2009-09-10 Thread Pion


I just saw http://en.wikipedia.org/wiki/Uniform_Resource_Locator#Syntax
which mentions about the # sign.

How do I retrieve the value of FOO which includes on this URL:
http://localhost:8080/get?FOO=BAR#123; ?
The result/value of FOO should be BAR#123.


On Sep 10, 8:56 am, Pion onlee2...@gmail.com wrote:
 Thanks. Window.Location.getParameter(FOO);  works.

 What does the # mean?
 I use http://localhost:8080/get?FOO=BAR#;  but
 Window.Location.getParameter(FOO) does not pick up the # sign.
 How do I retrieve the # as well?

 Again, thanks.

 On Sep 10, 8:17 am, Ian Bambury ianbamb...@gmail.com wrote:

  But you probably don't want to be doing that because if anything between the
  ? and the first # changes, your whole app will reload from scratch and
  you'll lose all state..

  Ian

 http://examples.roughian.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
-~--~~~~--~~--~--~---

GWT RPC miss timeout

2009-09-10 Thread And


Hi,
I couldn't find a way to set a timeout in GWT RPC call. Am I missing
something or this is done deliberately?

This feature is essential if your client use the system in low quality
network. Responses from the server might be lost sometimes and we
don't want obviously to loose one of two active connections to the
server.

I see there is nice implementation of timeout (with abort on
XmlHttpRequest) in RequestBuilder class, so any http request in GWT
supports timeout. Why I cannot use timeout with RPC? It should be easy
to implement because RPC uses RequestBuilder anyway (if I understand
GWT code correctly).

Did anybody cope with this issue?

Any help would be appreciated.

Many thanks,
Andrzej Bednarz

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

ListBox scroll index to visible

2009-09-10 Thread Jim Douglas


This seems to work ok, but I hate to write code that depends on
undocumented internals:

ListBox listbox = ...;
int index = ...;
SelectElement selectElement = SelectElement.as
(listbox.getElement());
OptionElement optionElement = selectElement.getOptions
().getItem(index);
optionElement.scrollIntoView();

Is that the correct approach?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---

Re: How to get mouse x/y outside of a click event?

2009-09-10 Thread ThomasWrobel


I guess thats how I'll do it :-/
Sure I saw a Dom call once or something though.

On Sep 10, 6:17 pm, Thomas Broyer t.bro...@gmail.com wrote:
 On 10 sep, 17:22, darkflame darkfl...@gmail.com wrote:

  Id like to know the current mouse x/y, relative to an element, at an
  arbitrary point in my code.
  (in this specific case during a scroll wheel event, but I might want
  it elsewhere later)

  How would I do this?
  I'm sure theres a simple function I'm missing, but it just escapes
  me :-/

 No, there's no mean to ask the mouse where she is; your only
 option (afaict) is to listen to mousemove events and store the
 coordinates in global variables that you can then read from another
 event loop iteration.
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Odd unable to find type error

2009-09-10 Thread Allen Firstenberg

I'm getting the following error when trying to compile an entry-point
module:

Compiling module com.example.gwt.selector.ArticleSelector
   Computing all possible rebind results for
'com.example.gwt.selector.ui.ArticleSelector'
  Rebinding com.example.gwt.selector.ui.ArticleSelector
 Checking rule generate-with
class='com.google.gwt.user.rebind.ui.ImageBundleGenerator'/
[ERROR] Unable to find type
'com.example.gwt.selector.ui.ArticleSelector'
   [ERROR] Hint: Previous compiler errors may have made this
type unavailable

Normally I get something like this when I omit an inherits configuration...
but all of them appear to be in my .gwt.xml and none are listed as missing
in the error messages above. I'm not using image bundles - at least nowhere
intentionally that I'm aware of. I'm not even sure where else to look for
the source of the problem at this point.

Contents of com/example/gwt/selector/ArticleSelector.gwt.xml:

?xml version=1.0 encoding=UTF-8?
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 1.7.0//EN 
http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd

module
  inherits name='com.google.gwt.dom.DOM'/

  inherits name='com.google.gwt.user.theme.chrome.Chrome'/
  inherits name='com.google.gwt.user.theme.chrome.ChromeResources'/

  inherits name=com.example.gwt.order.Order /

  entry-point class=com.example.gwt.selector.ui.ArticleSelector/
/module

Contents of com/example/gwt/order/Order.gwt.xml:

?xml version=1.0 encoding=UTF-8?
!DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 1.7.0//EN 
http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source/core/src/gwt-module.dtd

module
inherits name=com.google.gwt.user.User /
inherits name='com.allen_sauer.gwt.dnd.gwt-dnd'/
inherits name='com.spiders.gwt.lib.Lib'/
/module

Any suggestions or pointers where else to look?  Thanks!
Allen

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

Discussion on security-for-gwt-applications

2009-09-10 Thread ddyer


Isn't any security that's based on the browser enforcing a policy
essentially a sham?
Or more politely, guaranteed to be ineffective against a deliberate
attack.

The browsers are open source, and the communications channel is
unencrypted,
and you don't have to use a browser at all.  There are just too many
ways for browser
security to be bypassed.

This may not matter much if the target of the attack is presumed to be
the user, but
what if the target is the host site?


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

RootPanel.get(String) + DIV weirdness

2009-09-10 Thread davis


Hi, I've been coding a project for quite some time now.  It has been
stable, and everything was working great, until this afternoon.  I
have a file called Admin.html that has a few div tags:

div id=header align=center/div
div id=button-row align=center/div
div id=content align=center/div
div id=footer align=center/div

This was working fine for a long time.  A lot of code has changed
recently...some re-factoring, etc.  If I knew specifically what change
caused the problem, I wouldn't be asking for help.  It doesn't make
any sense to me.

The problem is that something like RootPanel.get(header).add(...
triggers NullPointerException.

In the browser (FF or IE), if I do View Page Source, I see my four DIV
elements.  But if I debug it in FireBug, I see that the footer div is
there but the others are not:

body class=page-body
div id=footertable cellspacing=0 cellpadding=0 style=height:
5%; width: 100%; class=footer-paneltbodytrtd align=center
style=vertical-align: top;table style=width: 40%; height:
100%;colgroupcol//colgrouptbodytrtd align=center
style=vertical-align: top;div class=footerCopyright © 2009
Footer Text Here. All Rights Reserved./div/td/trtrtd
align=center style=vertical-align: top;div class=footerHeader
Text Here/div/td/tr/tbody/table/td/tr/tbody/table/
div

!-- OPTIONAL: include this if you want history support --
iframe style=border: 0pt none ; position: absolute; width: 0pt;
height: 0pt; tabindex=-1 id=__gwt_historyFrame
src=javascript:''/

iframe src=javascript:'' id=com.example.audit.das.Admin
style=border: medium none ; position: absolute; width: 0pt; height:
0pt; tabindex=-1//body

I'm running out of ideas on this one...any clues?

Regards,
Davis

--~--~-~--~~~---~--~~
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 RPC Hibernate - again and again

2009-09-10 Thread Alexandros Papadakis

Download hibernate4gwt. It is the predecessor of Gilead. There are samples
there on how to use Spring + JPA.
Try the samples, understand how it works, and then move to Gilead. It is
just a matter of changing a few definitions.


If you cant find it, mail me and I will send you the samples.

Alex


On Tue, Sep 8, 2009 at 11:17 PM, Thomas Holmes thomas.j.hol...@gmail.comwrote:


 Would you have some sample code that I could see ... or a link to
 some.

 I'm going to continue looking through my book, and use their example
 that uses the Command Pattern.

 I am getting tons of errors because my DAO's and POJO's are in another
 package, so I was working with GWT Modules to try and make that work.
 I finally gave that up and tried to move that code closer to the
 Client directory ... and there a still a ton of errors.

 The most bothersome was in my UserDaoImpl where I have a
 getHibernateTemplate method, and it says that the source code isn't
 there.

 So ... it is driving me crazy ...

 Thanks!
Tom

 On Sep 8, 4:04 pm, David Durham david.durham...@gmail.com wrote:
   After research in this group, and on Google in general, I have found
   that I should look at Gilead.
   So, I downloaded the latest jars and the latest sample (using GWT 1.6)
   and sure enough, AGAIN, the sample uses hibernate.cfg.xml and
   Object.hbm.xml files 
 
  I was able to make GWT and Hiberate (JPA annotations) work without
  Gilead.  I just used the underlying beanlib replicators to undo the
  cglib or javassist stuff before serializing to client.
 
  -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 
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.get(String) + DIV weirdness

Take a backup
Cut out everything except the basic HTML and the
RootPanel.get(header).add(...

If it still does it, post the exact code here.

If not, go back and cut whole chunks out until it works. Then look at what
you just cut out.

Ian

http://examples.roughian.com


2009/9/10 davis davisf...@zenoconsulting.biz


 Hi, I've been coding a project for quite some time now.  It has been
 stable, and everything was working great, until this afternoon.  I
 have a file called Admin.html that has a few div tags:

 div id=header align=center/div
 div id=button-row align=center/div
 div id=content align=center/div
 div id=footer align=center/div

 This was working fine for a long time.  A lot of code has changed
 recently...some re-factoring, etc.  If I knew specifically what change
 caused the problem, I wouldn't be asking for help.  It doesn't make
 any sense to me.

 The problem is that something like RootPanel.get(header).add(...
 triggers NullPointerException.

 In the browser (FF or IE), if I do View Page Source, I see my four DIV
 elements.  But if I debug it in FireBug, I see that the footer div is
 there but the others are not:

 body class=page-body
 div id=footertable cellspacing=0 cellpadding=0 style=height:
 5%; width: 100%; class=footer-paneltbodytrtd align=center
 style=vertical-align: top;table style=width: 40%; height:
 100%;colgroupcol//colgrouptbodytrtd align=center
 style=vertical-align: top;div class=footerCopyright © 2009
 Footer Text Here. All Rights Reserved./div/td/trtrtd
 align=center style=vertical-align: top;div class=footerHeader
 Text Here/div/td/tr/tbody/table/td/tr/tbody/table/
 div

 !-- OPTIONAL: include this if you want history support --
 iframe style=border: 0pt none ; position: absolute; width: 0pt;
 height: 0pt; tabindex=-1 id=__gwt_historyFrame
 src=javascript:''/

 iframe src=javascript:'' id=com.example.audit.das.Admin
 style=border: medium none ; position: absolute; width: 0pt; height:
 0pt; tabindex=-1//body

 I'm running out of ideas on this one...any clues?

 Regards,
 Davis

 


--~--~-~--~~~---~--~~
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: MVP HasClickHandler

2009-09-10 Thread Jason A. Beranek


I take a little different approach, but you have most of the
fundamentals. The characteristic interface (i.e., Listener in your
example) shouldn't be defined as part of a particular instance of
MyPresenter.View, as that ties the Presenter directly to a specific
view implementation. Also, I would recommend following the Handler
pattern in GWT, as it allows you to utilize some of the Handler
management functions.

Taking your example, here's a possible approach using
SelectionHandlerString instead of MyView.Listener:

public class MyView extend Composite implements MyPresenter.View,
HasSelectionHandlersString {

  HasSelectionHandlersString getSelectionSource() {
return this;
  }

  ...

  //Do something with a click event (called by the ClickHandler)
  void doClick( CLickEvent event ) {
//Retrieve the selection (i.e., item to edit) by processing the
ClickEvent
String selection = getSelectionFromClickEvent( event );
SelectionEvent.fire(this, selection);
  }

}

public class MyPresenter implement MyView.Listener {

  public interface View {
HasSelectionHandlersString getSelectionSource();
  }

  ...

  public void bind(View display){
display.getSelectionSource().addSelectionHandler(new
SelectionHandlerString(){

  public void onSelection(SelectionEventString event) {
//Do Something in response to Selection
  }

});
  };

}

Note that in the example, even though MyView implements the
HasSelectionHandlerString interface directly, the Presenter only
accesses an instance that HasSelectionHandlersString through
View.getSelectionSource(). This allows different View implementations
to implement different sources for the SelectionEvent, reducing
potential coupling between the view and presenter. Hope that helps.

-Jason

On Sep 10, 10:47 am, fonghuangyee fonghuang...@gmail.com wrote:
 Thanks for ur advise.
 How about if i define a interface ( View Listener ), then my presenter
 implement the View Listener?

 Example :

 public class MyView extend Composite implement MyPresenter.View {

       public interface Listerner {

              public void onEdit(String id);
       }

       .
       .

       Listener listener;

       // a List of Button here
       button.addClickHandler(new ClickHandler(){

              public void onClick(ClickEvent event){
                      listener.onEdit(id);
              }
       );

 }

 public class MyPresenter implement MyView.Listener {

       public interface View {

       }

       public void onEdit(String id){
            // Do something here.
       };

 }

 Please correct me if i am following the wrong way.
 Thanks.

 On Sep 7, 8:32 am, Jason A. Beranek jason.bera...@gmail.com wrote:

  One approach I've used is to put some logic in the View to forward a
  different event than the purely GUI events to the Presenter. For
  example, if you have a table or list of items which can be clicked,
  and a click signifies selection of an item, use HasSelectionHandlers()
  in the View, and translate in the View which item is selected by the
  click. This seems to work for selection use cases, but it makes your
  View in theMVPmore Supervising Controller (http://martinfowler.com/
  eaaDev/SupervisingPresenter.html) than Passive View (http://
  martinfowler.com/eaaDev/PassiveScreen.html).

  If you were to need separate handling for each list item being
  clicked, then you are likely looking at a Presenter per list item or
  at having the View include a factory to add list items and return
  handlers (i.e., HasClickHandlers addListItem() ). Any of these
  approaches will work, it just depends on what you are looking to do
  with each click handler.

  V/r,

  Jason

  On Sep 6, 3:19 am, fonghuangyee fonghuang...@gmail.com wrote:

   Hihi ,
   After i go through so manyMVPexample, i found that we always use
   presenter to get thoseHasClickHandlerfrom Display( Or View) to do
   some action. This way works nice for static clickable action, but if
   we have some dynamic button ( example a table listing with a list of
   clickable  action ), then i have to get a list ofHasClickHandler
   from
   display? and every time i add new row to the table listing, i have to
   take care of the handler action, quite troublesome.
   any advice?

   Thanks.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---

How to parse HTML response from a servlet in GWT client side and domain must start with a dot problem

2009-09-10 Thread Ying Pian Wu


I need help with two problems.  Please excuse my noobness and give me
some suggestion.

I am using dyuproject to implement openId functionality and under some
condition, my servlet that uses dyuproject returns a response that is
a HTML page.  In the head section of this HMTL page, there's a
javascript element that contains the url to the openId provider.  The
problem is, I do not know how to extract this url from the response
text.  The HMTL.getElement() methods seems to only extract the body
element.

The second problem is, when a reponse is received by my GWT
application? I have no idea what is actually going on, but it seems
GWT is not adding a dot to the domain name.  Here is the actual error
shown:
Sep 10, 2009 5:18:55 PM org.apache.commons.httpclient.HttpMethodBase
processResponseHeaders
WARNING: Cookie rejected: $Version=0;
ephemeral_session_id=6f611b59416135a10dba1549bc1cc3993a273e284f4b868e649e0d342ff5;
$Path=/; $Domain=myopenid.com. Domain attribute myopenid.com
violates RFC 2109: domain must start with a dot

--~--~-~--~~~---~--~~
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: history token in window.title / document.title (browser window title)


re. 1) Window.setTitle() is the preferred method. Typically, you avoid
using the DOM based classes directly in your GWT Application.
re. 2) History has nothing to do with the title. Both are
independent..

On Sep 10, 5:39 pm, akumar anshulatashi...@gmail.com wrote:
 Hi,

 I am working on the browser history feature.

 Upon navigation from one state of the application to another state of
 the application - I like to programmatically set the browser window
 title.

 1) Doing some lookup on the javadocs - there seems to be two ways to
 do this (don't know which one I should use) but - Document.get
 ().setTitle(...) and Window.setTitle(...) which is the right method to
 use ?

 2) is it true, that history tokens also get attached to the browser
 title - as I see # token in the browser title as well (not sure, if it
 is bug in my code) or default behaviour?

 Thanks in advance.
--~--~-~--~~~---~--~~
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 RPC miss timeout


RPC Services do have timeouts, its just that by default they are set
to 0, which effectively means no timeout.

Here's what you can do to set timeouts on your services -

a) Create a custom RpcRequestBuilder, and set the desired timeout

public class MyRpcRequestBuilder extends RpcRequestBuilder {
@Override
protected RequestBuilder doCreate(String serviceEntryPoint)
{
RequestBuilder builder = new RequestBuilder
(RequestBuilder.POST, serviceEntryPoint);
builder.setTimeoutMillis(RPC_TIMEOUT);
return builder;
}
}

b) Set the custom RpcRequestBuilder immediately after your GWT.create
(..) call

//Can be a global object -- you don't have to create a new one
everytime
RpcRequestBuilder theBuilder = new MyRpcRequestBuilder();

MyServiceAsync service = GWT.create(MyService.class);
((ServiceDefTarget) service).setRpcRequestBuilder(theBuilder);


c) Use the service object to invoke methods as you normally do. In
your AsyncCallbacks onFailure(Throwable t), you can check

if (t instanceof RequestTimeoutException) {
  /// handle timeouts..
}

thats it.

On Sep 10, 11:00 am, And and.bed.w...@gmail.com wrote:
 Hi,
 I couldn't find a way to set a timeout in GWT RPC call. Am I missing
 something or this is done deliberately?

 This feature is essential if your client use the system in low quality
 network. Responses from the server might be lost sometimes and we
 don't want obviously to loose one of two active connections to the
 server.

 I see there is nice implementation of timeout (with abort on
 XmlHttpRequest) in RequestBuilder class, so any http request in GWT
 supports timeout. Why I cannot use timeout with RPC? It should be easy
 to implement because RPC uses RequestBuilder anyway (if I understand
 GWT code correctly).

 Did anybody cope with this issue?

 Any help would be appreciated.

 Many thanks,
 Andrzej Bednarz
--~--~-~--~~~---~--~~
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: Odd unable to find type error


Your client side code must reside under the client sub-package
relative to where your module.xml is defined. If classes are not under
the client package, gwt can't find them.

In your case, your class should be defined at the location com/example/
gwt/selector/client/ArticleSelector.java or com/example/gwt/selector/
client/ui/ArticleSelector.java

If you don't want a client sub-package, add a sourcepath entry to your
module.xml; but that would be a non-standard GWT layout and would only
confuse other developers.


On Sep 10, 4:14 pm, Allen Firstenberg g...@addventure.com wrote:
 I'm getting the following error when trying to compile an entry-point
 module:

 Compiling module com.example.gwt.selector.ArticleSelector
    Computing all possible rebind results for
 'com.example.gwt.selector.ui.ArticleSelector'
       Rebinding com.example.gwt.selector.ui.ArticleSelector
          Checking rule generate-with
 class='com.google.gwt.user.rebind.ui.ImageBundleGenerator'/
             [ERROR] Unable to find type
 'com.example.gwt.selector.ui.ArticleSelector'
                [ERROR] Hint: Previous compiler errors may have made this
 type unavailable

 Normally I get something like this when I omit an inherits configuration...
 but all of them appear to be in my .gwt.xml and none are listed as missing
 in the error messages above. I'm not using image bundles - at least nowhere
 intentionally that I'm aware of. I'm not even sure where else to look for
 the source of the problem at this point.

 Contents of com/example/gwt/selector/ArticleSelector.gwt.xml:

 ?xml version=1.0 encoding=UTF-8?
 !DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 1.7.0//EN 
 http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source...
 
 module
   inherits name='com.google.gwt.dom.DOM'/

   inherits name='com.google.gwt.user.theme.chrome.Chrome'/
   inherits name='com.google.gwt.user.theme.chrome.ChromeResources'/

   inherits name=com.example.gwt.order.Order /

   entry-point class=com.example.gwt.selector.ui.ArticleSelector/
 /module

 Contents of com/example/gwt/order/Order.gwt.xml:

 ?xml version=1.0 encoding=UTF-8?
 !DOCTYPE module PUBLIC -//Google Inc.//DTD Google Web Toolkit 1.7.0//EN 
 http://google-web-toolkit.googlecode.com/svn/tags/1.7.0/distro-source...
 
 module
 inherits name=com.google.gwt.user.User /
     inherits name='com.allen_sauer.gwt.dnd.gwt-dnd'/
     inherits name='com.spiders.gwt.lib.Lib'/
 /module

 Any suggestions or pointers where else to look?  Thanks!
 Allen
--~--~-~--~~~---~--~~
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: URL and GET method


Anything after the # can be picked up by calling History.getToken()
method.


On Sep 10, 12:30 pm, Pion onlee2...@gmail.com wrote:
 I just sawhttp://en.wikipedia.org/wiki/Uniform_Resource_Locator#Syntax
 which mentions about the # sign.

 How do I retrieve the value of FOO which includes on this 
 URL:http://localhost:8080/get?FOO=BAR#123; ?
 The result/value of FOO should be BAR#123.

 On Sep 10, 8:56 am, Pion onlee2...@gmail.com wrote:

  Thanks. Window.Location.getParameter(FOO);  works.

  What does the # mean?
  I use http://localhost:8080/get?FOO=BAR#;  but
  Window.Location.getParameter(FOO) does not pick up the # sign.
  How do I retrieve the # as well?

  Again, thanks.

  On Sep 10, 8:17 am, Ian Bambury ianbamb...@gmail.com wrote:

   But you probably don't want to be doing that because if anything between 
   the
   ? and the first # changes, your whole app will reload from scratch and
   you'll lose all state..

   Ian

  http://examples.roughian.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: Problem with call function external javascript


The approach you mention will not work. In fact, if it did work, it
would be a major security issue.

If you want to invoke an external javascript method, you will have to
write some jsni code.

See 
http://googlewebtoolkit.blogspot.com/2008/07/getting-to-really-know-gwt-part-1-jsni.html
The section Using JSNI to access external JavaScript code is what
you are looking for.

--sri

On Sep 10, 11:20 am, Senshi cristian.ro...@gmail.com wrote:
 Hi
 I have Problem with call function external javascript in IE7 not draw
 this in reload html page

                         texto = new HTML();
                         texto.setHTML(scriptbuildRow();/script);
                         panel.add(texto);

 no call function ..??

 ...no show alert??
                         texto = new HTML();
                         texto.setHTML(scriptalert(\Hello\);/script);
                         panel.add(texto);

 Please help
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

Deploy RCP in a subdomain

2009-09-10 Thread Hlunboi

Hi

I want to deploy my GWT RCP application in subdomain of my website.
Example: I have a website www.mysite.org and would like to deploy my GWT so
that i can access using my subdomain www.gwt.mysite.org

Could someone explain how to deploy in a subdomain?

Regards
Hlun

--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
Google Web Toolkit group.
To post to this group, send email to google-web-toolkit@googlegroups.com
To unsubscribe from this group, send email to 
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-web-toolkit?hl=en
-~--~~~~--~~--~--~---

Re: Why does this test fail ?


isAttached() won't return true unless the Widget has been added to the
DOM.

In your case, you should do something like
RootPanel.get().add(component);

After that, the isAttached() method would return true..

--sri

On Sep 10, 7:40 am, hjo1620 hjo1...@gmail.com wrote:
 CustomerComponent extends Composite,
 I do panel.add(widget) for all my widgets,
 and then do initWidget(panel), in the constructor.

 However this GWTTestCase test fails:

 public void testShouldAttachAllWidgets() throws Exception {
             CustomerComponent component = new CustomerComponent();
             assertNotNull(component);
             assertTrue(component.hasWidget());
             LinkedHashMapString, Widget widgets =
 component.getWidgets();
             IteratorWidget it = widgets.values().iterator();
             while (it.hasNext()) {
                         assertTrue(it.next().isAttached());
             }

 }

 What am I missing ?
 Should they not have been attached by the panel.add(widget) ?
--~--~-~--~~~---~--~~
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: Demo servlet rejects java.lang.IllegalStateException: STREAM when invoking resp.getWriter()


I am guessing its because you have already opened the stream by
calling the resp.setContentType(text/plain); method, and are then
trying to get a Writer object. You can either use Stream based
classes, or Writer based classes - not both.

Either remove the setContentType(), or send the response using
response.getOutputStream() method. That should solve the problem.

--sri

On Sep 10, 3:02 am, 6real xirgon...@gmail.com wrote:
 Dear all,

 I met an issue with my servlets, then I try the demo servlet given by
 Google :

 ---
 import java.io.IOException;
 import javax.servlet.http.HttpServlet;
 import javax.servlet.http.HttpServletRequest;
 import javax.servlet.http.HttpServletResponse;

 public class MyServlet extends HttpServlet {
     public void doGet(HttpServletRequest req, HttpServletResponse
 resp)
             throws IOException {
         resp.setContentType(text/plain);
         resp.getWriter().println(Hello, world);
     }}

 

 And I still raise an exception when invoking the method getWriter :

 java.lang.IllegalStateException: STREAM
         at org.mortbay.jetty.Response.getWriter(Response.java:583)
         at .

 Can anyone help me ? Is there a workaround ?

 For information my environment is :
 - Mac OS X 10.5.6
 - I downgraded my default JVM to the JAVA 5 32 bits version (else I
 couln't launch GWT app in hosted mode ...).

 Thanks for your help.

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

Reg : RequestCallBack

2009-09-10 Thread Arthik Babu


I am building a request builder to send the request to the server. For
one time i  m able to get the response back from the server and for
second time for another request i am not able to get the response
back. my GWT application is hanging and I am not able to see the
diplay.

Can u please help me why the request is not call process back by the
call back and for the request its going to sever and its completed its
process.

Regards,
Arthik
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---

[gwt-contrib] Re: IsSerializable in 2.0 : deprecate ?

2009-09-10 Thread nicolas de loof

I understand the idea about some classes beeing GWT-serializable and not
Java-serializable but really can't find a valid use case. Seems more a
misconception to me - just my humble opinion ;)

2009/9/10 George Georgovassilis g.georgovassi...@gmail.com


 I was under the impression that IsSerializable had been deprecated de
 facto. John, does IsSerializable currently override the serialization
 policy or this this a proposed behavior?

 On Sep 9, 4:27 pm, John Tamplin j...@google.com wrote:
  On Wed, Sep 9, 2009 at 9:06 AM, nicolas de loof 
 nicolas.del...@gmail.comwrote:
 
   I wonder that IsSerializable is still in trunk without a depreaction
   annotation. java.io.Serializable is supported by GWT-RPC since few
 major
   versions, maybe it's time to remove such legacy marker interface.
 
  I don't know if this is sufficient reason to keep it, but two reasons:
 
 - you might want a class to be serializable only in GWT and not in
 normal
 Java
 - IsSerializable means that it is always serializable, even without a
 serialization policy file on the server.  I think there are better
 ways to
 do this sort of thing, but some people may be depending on this
 functionality
 
  Maybe it could also extends Serializable so that it can be easier to
 switch
 
   the related tools.
 
  Other than the first issue above, sounds like a good idea.
 
  --
  John A. Tamplin
  Software Engineer (GWT), Google
 


--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: IsSerializable in 2.0 : deprecate ?

2009-09-10 Thread Nathan Wells


Could someone please update the article at

http://code.google.com/webtoolkit/doc/1.6/FAQ_Server.html#Does_the_GWT_RPC_system_support_the_use_of_java.io.Serializable

to indicate that IsSerializable is deprecated (or de facto deprecated,
or will be deprecated, or whatever)? When I read this article it
seemed like GWT was encouraging the use of IsSerializable over
Serializable.

Is this something I should file a ticket on?

On Sep 10, 12:46 am, nicolas de loof nicolas.del...@gmail.com wrote:
 I understand the idea about some classes beeing GWT-serializable and not
 Java-serializable but really can't find a valid use case. Seems more a
 misconception to me - just my humble opinion ;)

 2009/9/10 George Georgovassilis g.georgovassi...@gmail.com





  I was under the impression that IsSerializable had been deprecated de
  facto. John, does IsSerializable currently override the serialization
  policy or this this a proposed behavior?

  On Sep 9, 4:27 pm, John Tamplin j...@google.com wrote:
   On Wed, Sep 9, 2009 at 9:06 AM, nicolas de loof 
  nicolas.del...@gmail.comwrote:

I wonder that IsSerializable is still in trunk without a depreaction
annotation. java.io.Serializable is supported by GWT-RPC since few
  major
versions, maybe it's time to remove such legacy marker interface.

   I don't know if this is sufficient reason to keep it, but two reasons:

      - you might want a class to be serializable only in GWT and not in
  normal
      Java
      - IsSerializable means that it is always serializable, even without a
      serialization policy file on the server.  I think there are better
  ways to
      do this sort of thing, but some people may be depending on this
      functionality

   Maybe it could also extends Serializable so that it can be easier to
  switch

the related tools.

   Other than the first issue above, sounds like a good idea.

   --
   John A. Tamplin
   Software Engineer (GWT), Google
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] [google-web-toolkit] r6110 committed - Initial implementations of Stack and Split layout panels, along with a...


Revision: 6110
Author: j...@google.com
Date: Thu Sep 10 05:47:55 2009
Log: Initial implementations of Stack and Split layout panels, along with a  
few
checkstyle tweaks.
Review: http://gwt-code-reviews.appspot.com/65804
http://code.google.com/p/google-web-toolkit/source/detail?r=6110

Added:
  /trunk/user/javadoc/com/google/gwt/examples/SplitLayoutPanelExample.java
  /trunk/user/javadoc/com/google/gwt/examples/StackLayoutPanelExample.java
  /trunk/user/src/com/google/gwt/user/client/ui/SplitLayoutPanel.java
  /trunk/user/src/com/google/gwt/user/client/ui/StackLayoutPanel.java
Modified:
  /trunk/user/src/com/google/gwt/user/client/ui/DockLayoutPanel.java

===
--- /dev/null
+++  
/trunk/user/javadoc/com/google/gwt/examples/SplitLayoutPanelExample.java
 
Thu Sep 10 05:47:55 2009
@@ -0,0 +1,47 @@
+/*
+ * Copyright 2009 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.examples;
+
+import com.google.gwt.core.client.EntryPoint;
+import com.google.gwt.user.client.ui.HTML;
+import com.google.gwt.user.client.ui.RootLayoutPanel;
+import com.google.gwt.user.client.ui.SplitLayoutPanel;
+import com.google.gwt.user.client.ui.DockLayoutPanel.Direction;
+
+public class SplitLayoutPanelExample implements EntryPoint {
+
+  public void onModuleLoad() {
+// Create a three-pane layout with splitters.
+SplitLayoutPanel p = new SplitLayoutPanel();
+p.add(new HTML(navigation), Direction.WEST, 128);
+p.add(new HTML(list), Direction.NORTH, 384);
+p.add(new HTML(details), Direction.CENTER, 0);
+
+// Note the explicit call to layout(). This is required for the layout  
to
+// take effect.
+p.layout();
+
+// Attach the LayoutPanel to the RootLayoutPanel. The latter will  
listen for
+// resize events on the window to ensure that its children are  
informed of
+// possible size changes.
+RootLayoutPanel rp = RootLayoutPanel.get();
+rp.add(p);
+
+// The RootLayoutPanel also requires that its layout() method be  
explicitly
+// called for the initial layout to take effect.
+rp.layout();
+  }
+}
===
--- /dev/null
+++  
/trunk/user/javadoc/com/google/gwt/examples/StackLayoutPanelExample.java
 
Thu Sep 10 05:47:55 2009
@@ -0,0 +1,47 @@
+/*
+ * Copyright 2009 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.examples;
+
+import com.google.gwt.core.client.EntryPoint;
+import com.google.gwt.dom.client.Style.Unit;
+import com.google.gwt.user.client.ui.HTML;
+import com.google.gwt.user.client.ui.RootLayoutPanel;
+import com.google.gwt.user.client.ui.StackLayoutPanel;
+
+public class StackLayoutPanelExample implements EntryPoint {
+
+  public void onModuleLoad() {
+// Create a three-item stack, with headers sized in EMs.
+StackLayoutPanel p = new StackLayoutPanel(Unit.EM);
+p.add(new HTML(this), new HTML([this]), 128);
+p.add(new HTML(that), new HTML([that]), 384);
+p.add(new HTML(the other), new HTML([the other]), 0);
+
+// Note the explicit call to layout(). This is required for the layout  
to
+// take effect.
+p.layout();
+
+// Attach the LayoutPanel to the RootLayoutPanel. The latter will  
listen for
+// resize events on the window to ensure that its children are  
informed of
+// possible size changes.
+RootLayoutPanel rp = RootLayoutPanel.get();
+rp.add(p);
+
+// The RootLayoutPanel also requires that its layout() method be  
explicitly
+// called for the initial layout to take effect.
+rp.layout();
+  }
+}
===
--- /dev/null
+++ /trunk/user/src/com/google/gwt/user/client/ui/SplitLayoutPanel.java Thu  
Sep 10 05:47:55 2009
@@ -0,0 +1,294 @@
+/*
+ * Copyright 2009 Google Inc.
+ *
+ * Licensed under the Apache License, Version 2.0 (the License); you may  
not
+ * use this file except in

[gwt-contrib] Re: IsSerializable in 2.0 : deprecate ?

The conclusion here is *not* to deprecate it.

On Thursday, September 10, 2009, Nathan Wells nwwe...@gmail.com wrote:

Could someone please update the article at

http://code.google.com/webtoolkit/doc/1.6/FAQ_Server.html#Does_the_GWT_RPC_system_support_the_use_of_java.io.Serializable

to indicate that IsSerializable is deprecated (or de facto deprecated,
or will be deprecated, or whatever)? When I read this article it
seemed like GWT was encouraging the use of IsSerializable over
Serializable.

Is this something I should file a ticket on?

On Sep 10, 12:46 am, nicolas de loof nicolas.del...@gmail.com wrote:
I understand the idea about some classes beeing GWT-serializable and not
Java-serializable but really can't find a valid use case. Seems more a
misconception to me - just my humble opinion ;)

2009/9/10 George Georgovassilis g.georgovassi...@gmail.com

I was under the impression that IsSerializable had been deprecated de
facto. John, does IsSerializable currently override the serialization
policy or this this a proposed behavior?

On Sep 9, 4:27 pm, John Tamplin j...@google.com wrote:
On Wed, Sep 9, 2009 at 9:06 AM, nicolas de loof
nicolas.del...@gmail.comwrote:

I wonder that IsSerializable is still in trunk without a depreaction
annotation. java.io.Serializable is supported by GWT-RPC since few
major
versions, maybe it's time to remove such legacy marker interface.

I don't know if this is sufficient reason to keep it, but two reasons:

- you might want a class to be serializable only in GWT and not in
normal
Java
- IsSerializable means that it is always serializable, even without a
serialization policy file on the server. I think there are better
ways to
do this sort of thing, but some people may be depending on this
functionality

Maybe it could also extends Serializable so that it can be easier to
switch

the related tools.

Other than the first issue above, sounds like a good idea.

--
John A. Tamplin
Software Engineer (GWT), Google

--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: IsSerializable in 2.0 : deprecate ?

2009-09-10 Thread John Tamplin

On Thu, Sep 10, 2009 at 2:11 AM, George Georgovassilis 
g.georgovassi...@gmail.com wrote:

 I was under the impression that IsSerializable had been deprecated de
 facto. John, does IsSerializable currently override the serialization
 policy or this this a proposed behavior?


It doesn't override it -- the legacy serialization policy, which is what is
used if no *.gwt.rpc file is found, allows anything marked IsSerializable to
be serialized.  Allowing Serializable is a security risk in this case, since
many classes are marked as Serializable that should not be returned, and
simply instantiating one of them might provide an attack vector if a
malicious client knew it was on the server's classpath.

IsSerializable doesn't have this problem because it is only used for GWT, so
if the developer marked it in such a way they are explicitly saying it is ok
for GWT to serialize.

-- 
John A. Tamplin
Software Engineer (GWT), Google

--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: IsSerializable in 2.0 : deprecate ?

2009-09-10 Thread Nathan Wells

Thanks Ray, that's comforting to hear, after having built an application on
the assumption that IsSerializable is a recommended way to do gwt-rpc. Not
that it would be a huge problem... just probably a day of refactoring and
adding @SupressWarning annotations.

Thanks again :)
Nathan Wells


On Thu, Sep 10, 2009 at 7:21 AM, John Tamplin j...@google.com wrote:

 On Thu, Sep 10, 2009 at 2:11 AM, George Georgovassilis 
 g.georgovassi...@gmail.comhttps://mail.adaptivecomputing.com/zimbra?app=mailview=composeto=g.georgovassi...@gmail.com
  wrote:

 I was under the impression that IsSerializable had been deprecated de
 facto. John, does IsSerializable currently override the serialization
 policy or this this a proposed behavior?


 It doesn't override it -- the legacy serialization policy, which is what is
 used if no *.gwt.rpc file is found, allows anything marked IsSerializable to
 be serialized.  Allowing Serializable is a security risk in this case, since
 many classes are marked as Serializable that should not be returned, and
 simply instantiating one of them might provide an attack vector if a
 malicious client knew it was on the server's classpath.

 IsSerializable doesn't have this problem because it is only used for GWT,
 so if the developer marked it in such a way they are explicitly saying it is
 ok for GWT to serialize.

 --
 John A. Tamplin
 Software Engineer (GWT), Google

 


--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: GWT Incubator compatibility policy

Hey, Isaac.
That policy has proven very difficult to live with. (And to tell you the
truth I forgot about it.)

The reasoning here was that we have released incubator jars that work with
1.7 and no plans to issue further ones before 2.0 MS1 lands. Should it prove
necessary to go back and do so we can go back and branch.

In the meantime, we were faced bugs due to FastTree in particular being tied
to the old StyleInjector while new development was moving to the version in
GWT.  We saw the opportunity to delete redundant code and took it.

Is this going to cause problems for anyone?

rjrjr

On Wed, Sep 9, 2009 at 3:26 PM, Isaac Truett itru...@gmail.com wrote:

 Last year, Emily stated that it would compile against the latest
 gwt-milestone and gwt-trunk. There hasn't been a 2.0 milestone that
 I've seen, so under the policy from last year StyleInjector should not
 have been removed in revisions 1712-1715.

 So, what's the current policy for incubator trunk compatibility?


--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: Fixes double escaping bug in UiBinder messages


LGTM.  One bit of comment cruft would be good to delete.


http://gwt-code-reviews.appspot.com/64810/diff/1/5
File
user/src/com/google/gwt/uibinder/rebind/messages/PlaceholderInterpreter.java
(right):

http://gwt-code-reviews.appspot.com/64810/diff/1/5#newcode115
Line 115: * @return
Auto-generated cruft.

http://gwt-code-reviews.appspot.com/64810/diff/1/8
File user/test/com/google/gwt/uibinder/sample/client/UiBinderTest.java
(right):

http://gwt-code-reviews.appspot.com/64810/diff/1/8#newcode177
Line 177: assertEquals(funny characters \ \ ' ' { }, t);
Excellent.

http://gwt-code-reviews.appspot.com/64810

--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: Add permutation info to index page for each permutation


LGTM

http://gwt-code-reviews.appspot.com/64808

--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: GWT Incubator compatibility policy

I built incubator against trunk last night. Are you still seeing trouble
there?
The problem on our end has been that having to maintain code that works both
with trunk and with the previous release makes it very difficult to iterate
rapidly on incubator code. What was supposed to be a place that we could
rapidly develop new features instead turns into a morass where forward
progress is twice as hard a normal. That's why UiBinder in particular never
moved to incubator.

Our expectation is that new features will be either developed directly in
trunk (e.g. UiBinder), or else in separate projects on code.google.com that
can determine their own policies on compatibility and contributors (e.g.
Gin). The items that live in incubator already will either gradually move to
trunk or languish.

It sounds like we need to think a bit harder how to handle the stuff that
hasn't graduate yet, but which is still in use. My knee jerk is to cut a 1.7
branch just before the patch that killed off StyleInjector. How does that
sound?

rjrjr

On Thu, Sep 10, 2009 at 8:28 AM, Isaac Truett itru...@gmail.com wrote:


 [oops - +gwtc]


 Hi, Ray,

 I appreciate the drive to move forward and I applaud jumping on
 opportunities to remove redundant code.

 The reason this policy was important, to me at least, is that it
 provided a baseline to work against. The code in the incubator can be
 very useful (I use PagingScrollTable extensively and used DatePicker
 from incubator before it graduated) but it's also risky because the
 code is still experimental and subject to change. The assurance that
 those changes would be compatible with a packaged and released GWT
 build (even just a milestone) meant that I could build incubator from
 trunk and pick up the latest features and bugfixes as long as my
 project tracked the latest GWT build. Because of the GWT policies on
 deprecation and backwards compatibility, this has been fairly easy in
 practice. As it stands now, incubator will not compile except against
 GWT trunk, which is also notoriously unstable (it wasn't building as
 recently as last night, which I see was corrected this morning). This
 presents a much higher risk for those of us using incubator code.

 It also becomes harder to work on the incubator itself when it has to
 compile against GWT trunk. I wanted to look into issue #267 last night
 and I was stymied by GWT trunk not being in a buildable state. Not an
 insurmountable obstacle, but one that seems unnecessary to me.

 - Isaac


 On Thu, Sep 10, 2009 at 11:03 AM, Ray Ryan rj...@google.com wrote:
  Hey, Isaac.
  That policy has proven very difficult to live with. (And to tell you the
  truth I forgot about it.)
  The reasoning here was that we have released incubator jars that work
 with
  1.7 and no plans to issue further ones before 2.0 MS1 lands. Should it
 prove
  necessary to go back and do so we can go back and branch.
  In the meantime, we were faced bugs due to FastTree in particular being
 tied
  to the old StyleInjector while new development was moving to the version
 in
  GWT.  We saw the opportunity to delete redundant code and took it.
  Is this going to cause problems for anyone?
  rjrjr
 
  On Wed, Sep 9, 2009 at 3:26 PM, Isaac Truett itru...@gmail.com wrote:
 
  Last year, Emily stated that it would compile against the latest
  gwt-milestone and gwt-trunk. There hasn't been a 2.0 milestone that
  I've seen, so under the policy from last year StyleInjector should not
  have been removed in revisions 1712-1715.
 
  So, what's the current policy for incubator trunk compatibility?
 
 

 


--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: GWT Incubator compatibility policy

2009-09-10 Thread jay


So...as of right now, what is the *last* version of gwt-incubator that
is guaranteed to work with GWT 1.7? Is it safe to assume that it is
the version immediately prior to the removal of StyleInjector?

thanks,

jay

On Sep 10, 8:28 am, Isaac Truett itru...@gmail.com wrote:
 [oops - +gwtc]

 Hi, Ray,

 I appreciate the drive to move forward and I applaud jumping on
 opportunities to remove redundant code.

 The reason this policy was important, to me at least, is that it
 provided a baseline to work against. The code in the incubator can be
 very useful (I use PagingScrollTable extensively and used DatePicker
 from incubator before it graduated) but it's also risky because the
 code is still experimental and subject to change. The assurance that
 those changes would be compatible with a packaged and released GWT
 build (even just a milestone) meant that I could build incubator from
 trunk and pick up the latest features and bugfixes as long as my
 project tracked the latest GWT build. Because of the GWT policies on
 deprecation and backwards compatibility, this has been fairly easy in
 practice. As it stands now, incubator will not compile except against
 GWT trunk, which is also notoriously unstable (it wasn't building as
 recently as last night, which I see was corrected this morning). This
 presents a much higher risk for those of us using incubator code.

 It also becomes harder to work on the incubator itself when it has to
 compile against GWT trunk. I wanted to look into issue #267 last night
 and I was stymied by GWT trunk not being in a buildable state. Not an
 insurmountable obstacle, but one that seems unnecessary to me.

 - Isaac



 On Thu, Sep 10, 2009 at 11:03 AM, Ray Ryan rj...@google.com wrote:
  Hey, Isaac.
  That policy has proven very difficult to live with. (And to tell you the
  truth I forgot about it.)
  The reasoning here was that we have released incubator jars that work with
  1.7 and no plans to issue further ones before 2.0 MS1 lands. Should it prove
  necessary to go back and do so we can go back and branch.
  In the meantime, we were faced bugs due to FastTree in particular being tied
  to the old StyleInjector while new development was moving to the version in
  GWT.  We saw the opportunity to delete redundant code and took it.
  Is this going to cause problems for anyone?
  rjrjr

  On Wed, Sep 9, 2009 at 3:26 PM, Isaac Truett itru...@gmail.com wrote:

  Last year, Emily stated that it would compile against the latest
  gwt-milestone and gwt-trunk. There hasn't been a 2.0 milestone that
  I've seen, so under the policy from last year StyleInjector should not
  have been removed in revisions 1712-1715.

  So, what's the current policy for incubator trunk compatibility?
--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: GWT Incubator compatibility policy

2009-09-10 Thread Isaac Truett


I am confident that r6108 fixed the problem I was having with GWT
trunk last night. I think I just happened to try to build during a
brief period where the build had broken. By the time r6108 had been
committed, I had already moved on to other things.

I see what you're saying about incubator being bogged down by
backwards compatibility. I had thought of incubator more as a place to
develop new APIs rather than a place to build on pre-release APIs. The
issue as it sounds to me is that when a new API develops outside of
incubator (such as in GWT trunk), you want to develop/update incubator
widgets with that API before it gets into a GWT milestone.

Would a branch for 1.7 really help with the morass problem? If you
maintain the branch, then you still have to code incubator changes
against two different versions of GWT. If you don't maintain the
branch, then it's not particularly useful.

Going forward should the advice be don't use incubator unless you
plan to stay at the bleeding edge of GWT trunk? I can't speak for
other developers, but if that had been the case then I don't think I
would've ever used incubator widgets in my work projects. Maybe I
shouldn't have used them, but they've been very helpful so far. None
of the widgets have been production quality to begin with, but I've
been able to report bugs and get bug fixes committed, sometimes
supplying fixes myself, and build from incubator trunk without
worrying that I'd have to update my GWT core to a trunk build. Losing
that assurance will hurt, but it won't be the end of the world. It
will definitely make it harder for me to benefit from the latest
incubator widget bug fixes.





On Thu, Sep 10, 2009 at 11:44 AM, Ray Ryan rj...@google.com wrote:
 I built incubator against trunk last night. Are you still seeing trouble
 there?
 The problem on our end has been that having to maintain code that works both
 with trunk and with the previous release makes it very difficult to iterate
 rapidly on incubator code. What was supposed to be a place that we could
 rapidly develop new features instead turns into a morass where forward
 progress is twice as hard a normal. That's why UiBinder in particular never
 moved to incubator.
 Our expectation is that new features will be either developed directly in
 trunk (e.g. UiBinder), or else in separate projects on code.google.com that
 can determine their own policies on compatibility and contributors (e.g.
 Gin). The items that live in incubator already will either gradually move to
 trunk or languish.
 It sounds like we need to think a bit harder how to handle the stuff that
 hasn't graduate yet, but which is still in use. My knee jerk is to cut a 1.7
 branch just before the patch that killed off StyleInjector. How does that
 sound?
 rjrjr

 On Thu, Sep 10, 2009 at 8:28 AM, Isaac Truett itru...@gmail.com wrote:

 [oops - +gwtc]


 Hi, Ray,

 I appreciate the drive to move forward and I applaud jumping on
 opportunities to remove redundant code.

 The reason this policy was important, to me at least, is that it
 provided a baseline to work against. The code in the incubator can be
 very useful (I use PagingScrollTable extensively and used DatePicker
 from incubator before it graduated) but it's also risky because the
 code is still experimental and subject to change. The assurance that
 those changes would be compatible with a packaged and released GWT
 build (even just a milestone) meant that I could build incubator from
 trunk and pick up the latest features and bugfixes as long as my
 project tracked the latest GWT build. Because of the GWT policies on
 deprecation and backwards compatibility, this has been fairly easy in
 practice. As it stands now, incubator will not compile except against
 GWT trunk, which is also notoriously unstable (it wasn't building as
 recently as last night, which I see was corrected this morning). This
 presents a much higher risk for those of us using incubator code.

 It also becomes harder to work on the incubator itself when it has to
 compile against GWT trunk. I wanted to look into issue #267 last night
 and I was stymied by GWT trunk not being in a buildable state. Not an
 insurmountable obstacle, but one that seems unnecessary to me.

 - Isaac


 On Thu, Sep 10, 2009 at 11:03 AM, Ray Ryan rj...@google.com wrote:
  Hey, Isaac.
  That policy has proven very difficult to live with. (And to tell you the
  truth I forgot about it.)
  The reasoning here was that we have released incubator jars that work
  with
  1.7 and no plans to issue further ones before 2.0 MS1 lands. Should it
  prove
  necessary to go back and do so we can go back and branch.
  In the meantime, we were faced bugs due to FastTree in particular being
  tied
  to the old StyleInjector while new development was moving to the version
  in
  GWT.  We saw the opportunity to delete redundant code and took it.
  Is this going to cause problems for anyone?
  rjrjr
 
  On Wed, Sep 9, 2009 at 3:26 PM, Isaac Truett

[gwt-contrib] Re: GWT Incubator compatibility policy

2009-09-10 Thread Freeland Abbott

Going forward, I think Ray said incubator bits will either migrate into GWT
proper (and be maintained and branched for releases there) or will
languish, so I imagine the advice will gradually become don't use
incubator.  I take languish as meaning we'd probably remain stable
against existing releases, but face bitrot against trunk which might become
bitrot against new GWT releases, and be fixed only as cases were called out.
 That's my personal interpretation, though; I don't think we've declared a
definition.
Anything that does remain in incubator I think should have release branches,
as Ray suggests... I think it does help the morass, because you can leave
behind a stably working incubator against 1.6/1.7/whatever, and only need
the trunk to work with a trunk of GWT.

If incubator is relatively quiet, I think that's easier... if it's noisy,
then you need the incubator's current-GWT-release branch to be noisy also,
and suck up the merges to incubator trunk, drag on RAD or not.  But I think
it's just bad news to have a given incubator branch promising to be
compatible with some plural number of GWT branches, which is where we are
now I'd rather do merges, and not have to straddle an open-ended set of
differences between GWT branches.



On Thu, Sep 10, 2009 at 1:06 PM, Isaac Truett itru...@gmail.com wrote:


 I am confident that r6108 fixed the problem I was having with GWT
 trunk last night. I think I just happened to try to build during a
 brief period where the build had broken. By the time r6108 had been
 committed, I had already moved on to other things.

 I see what you're saying about incubator being bogged down by
 backwards compatibility. I had thought of incubator more as a place to
 develop new APIs rather than a place to build on pre-release APIs. The
 issue as it sounds to me is that when a new API develops outside of
 incubator (such as in GWT trunk), you want to develop/update incubator
 widgets with that API before it gets into a GWT milestone.

 Would a branch for 1.7 really help with the morass problem? If you
 maintain the branch, then you still have to code incubator changes
 against two different versions of GWT. If you don't maintain the
 branch, then it's not particularly useful.

 Going forward should the advice be don't use incubator unless you
 plan to stay at the bleeding edge of GWT trunk? I can't speak for
 other developers, but if that had been the case then I don't think I
 would've ever used incubator widgets in my work projects. Maybe I
 shouldn't have used them, but they've been very helpful so far. None
 of the widgets have been production quality to begin with, but I've
 been able to report bugs and get bug fixes committed, sometimes
 supplying fixes myself, and build from incubator trunk without
 worrying that I'd have to update my GWT core to a trunk build. Losing
 that assurance will hurt, but it won't be the end of the world. It
 will definitely make it harder for me to benefit from the latest
 incubator widget bug fixes.





 On Thu, Sep 10, 2009 at 11:44 AM, Ray Ryan rj...@google.com wrote:
  I built incubator against trunk last night. Are you still seeing trouble
  there?
  The problem on our end has been that having to maintain code that works
 both
  with trunk and with the previous release makes it very difficult to
 iterate
  rapidly on incubator code. What was supposed to be a place that we could
  rapidly develop new features instead turns into a morass where forward
  progress is twice as hard a normal. That's why UiBinder in particular
 never
  moved to incubator.
  Our expectation is that new features will be either developed directly in
  trunk (e.g. UiBinder), or else in separate projects on code.google.comthat
  can determine their own policies on compatibility and contributors (e.g.
  Gin). The items that live in incubator already will either gradually move
 to
  trunk or languish.
  It sounds like we need to think a bit harder how to handle the stuff that
  hasn't graduate yet, but which is still in use. My knee jerk is to cut a
 1.7
  branch just before the patch that killed off StyleInjector. How does that
  sound?
  rjrjr
 
  On Thu, Sep 10, 2009 at 8:28 AM, Isaac Truett itru...@gmail.com wrote:
 
  [oops - +gwtc]
 
 
  Hi, Ray,
 
  I appreciate the drive to move forward and I applaud jumping on
  opportunities to remove redundant code.
 
  The reason this policy was important, to me at least, is that it
  provided a baseline to work against. The code in the incubator can be
  very useful (I use PagingScrollTable extensively and used DatePicker
  from incubator before it graduated) but it's also risky because the
  code is still experimental and subject to change. The assurance that
  those changes would be compatible with a packaged and released GWT
  build (even just a milestone) meant that I could build incubator from
  trunk and pick up the latest features and bugfixes as long as my
  project tracked the latest GWT build. Because of the

[gwt-contrib] Re: Introduces inline styles to ui.xml files


LGTM.  One comment typo, one question about a possible extra test.


http://gwt-code-reviews.appspot.com/64812/diff/1/5
File
user/src/com/google/gwt/uibinder/rebind/model/ImplicitCssResource.java
(right):

http://gwt-code-reviews.appspot.com/64812/diff/1/5#newcode67
Line 67: * file rather than look load a resource.
Sounds just great.

rather than look load --  rather than load

http://gwt-code-reviews.appspot.com/64812/diff/1/5#newcode138
Line 138: * this package
I don't know what else that utility does, but if nothing else loading
from ResourceOracle has the advantage of centralizing the choice of
class loader.

http://gwt-code-reviews.appspot.com/64812/diff/1/9
File user/test/com/google/gwt/uibinder/sample/client/UiBinderTest.java
(right):

http://gwt-code-reviews.appspot.com/64812/diff/1/9#newcode281
Line 281: widgetUi.totallyPrivateStyleSpan.getClassName().length()  0);
How hard would it be to test that the style contents are sane?

http://gwt-code-reviews.appspot.com/64812

--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: GWT Incubator compatibility policy

If you're after guarantees I guess that would be 1686, the one that the 1.7
jar was cut from (gwt-incubator-july-14-2009.jar). Looking at the svn
history, nothing has actually changed in the code from that one to the
removal of StyleInjector. It's all wiki edits and such since then.

On Thu, Sep 10, 2009 at 8:46 AM, jay jay.gin...@gmail.com wrote:


 So...as of right now, what is the *last* version of gwt-incubator that
 is guaranteed to work with GWT 1.7? Is it safe to assume that it is
 the version immediately prior to the removal of StyleInjector?

 thanks,

 jay

 On Sep 10, 8:28 am, Isaac Truett itru...@gmail.com wrote:
  [oops - +gwtc]
 
  Hi, Ray,
 
  I appreciate the drive to move forward and I applaud jumping on
  opportunities to remove redundant code.
 
  The reason this policy was important, to me at least, is that it
  provided a baseline to work against. The code in the incubator can be
  very useful (I use PagingScrollTable extensively and used DatePicker
  from incubator before it graduated) but it's also risky because the
  code is still experimental and subject to change. The assurance that
  those changes would be compatible with a packaged and released GWT
  build (even just a milestone) meant that I could build incubator from
  trunk and pick up the latest features and bugfixes as long as my
  project tracked the latest GWT build. Because of the GWT policies on
  deprecation and backwards compatibility, this has been fairly easy in
  practice. As it stands now, incubator will not compile except against
  GWT trunk, which is also notoriously unstable (it wasn't building as
  recently as last night, which I see was corrected this morning). This
  presents a much higher risk for those of us using incubator code.
 
  It also becomes harder to work on the incubator itself when it has to
  compile against GWT trunk. I wanted to look into issue #267 last night
  and I was stymied by GWT trunk not being in a buildable state. Not an
  insurmountable obstacle, but one that seems unnecessary to me.
 
  - Isaac
 
 
 
  On Thu, Sep 10, 2009 at 11:03 AM, Ray Ryan rj...@google.com wrote:
   Hey, Isaac.
   That policy has proven very difficult to live with. (And to tell you
 the
   truth I forgot about it.)
   The reasoning here was that we have released incubator jars that work
 with
   1.7 and no plans to issue further ones before 2.0 MS1 lands. Should it
 prove
   necessary to go back and do so we can go back and branch.
   In the meantime, we were faced bugs due to FastTree in particular being
 tied
   to the old StyleInjector while new development was moving to the
 version in
   GWT.  We saw the opportunity to delete redundant code and took it.
   Is this going to cause problems for anyone?
   rjrjr
 
   On Wed, Sep 9, 2009 at 3:26 PM, Isaac Truett itru...@gmail.com
 wrote:
 
   Last year, Emily stated that it would compile against the latest
   gwt-milestone and gwt-trunk. There hasn't been a 2.0 milestone that
   I've seen, so under the policy from last year StyleInjector should not
   have been removed in revisions 1712-1715.
 
   So, what's the current policy for incubator trunk compatibility?
 


--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] [google-web-toolkit] r6112 committed - Delete old cruft, rearrange directory structure to better build the Ch...


Revision: 6112
Author: j...@google.com
Date: Thu Sep 10 11:52:42 2009
Log: Delete old cruft, rearrange directory structure to better build the  
Chrome
plugin with just what is needed.

http://code.google.com/p/google-web-toolkit/source/detail?r=6112

Added:
  /trunk/plugins/npapi/prebuilt/gwtdmp
  /trunk/plugins/npapi/prebuilt/gwtdmp/WINNT_x86-msvc
  /trunk/plugins/npapi/prebuilt/gwtdmp/gwt128.png
  /trunk/plugins/npapi/prebuilt/gwtdmp/gwt16.png
  /trunk/plugins/npapi/prebuilt/gwtdmp/gwt32.png
  /trunk/plugins/npapi/prebuilt/gwtdmp/gwt64.png
  /trunk/plugins/npapi/prebuilt/gwtdmp/manifest.json
Deleted:
  /trunk/plugins/npapi/prebuilt/extension
  /trunk/plugins/npapi/prebuilt/gwt128.png
  /trunk/plugins/npapi/prebuilt/gwt16.png
  /trunk/plugins/npapi/prebuilt/gwt32.png
  /trunk/plugins/npapi/prebuilt/gwt64.png
  /trunk/plugins/npapi/prebuilt/manifest.json
  /trunk/plugins/npapi/prebuilt/oophm.xpi
  /trunk/plugins/npapi/prebuilt/winnt_x86-msvc
Modified:
  /trunk/plugins/npapi/VisualStudio/npapi-plugin.vcproj
  /trunk/plugins/npapi/prebuilt/gwtdmp/WINNT_x86-msvc/npOOPHM.dll
  /trunk/plugins/npapi/prebuilt/gwtdmp.crx

===
--- /dev/null   
+++ /trunk/plugins/npapi/prebuilt/gwtdmp/gwt128.png Thu Sep 10 11:52:42 2009
Binary file, no diff available.
===
--- /dev/null   
+++ /trunk/plugins/npapi/prebuilt/gwtdmp/gwt16.png  Thu Sep 10 11:52:42 2009
Binary file, no diff available.
===
--- /dev/null   
+++ /trunk/plugins/npapi/prebuilt/gwtdmp/gwt32.png  Thu Sep 10 11:52:42 2009
Binary file, no diff available.
===
--- /dev/null   
+++ /trunk/plugins/npapi/prebuilt/gwtdmp/gwt64.png  Thu Sep 10 11:52:42 2009
Binary file, no diff available.
===
--- /dev/null
+++ /trunk/plugins/npapi/prebuilt/gwtdmp/manifest.json  Thu Sep 10 11:52:42  
2009
@@ -0,0 +1,14 @@
+{
+  name: GWT Development Mode Plugin,
+  version: 0.9.0,
+  description: A plugin to enable debugging with GWT's Development  
Mode,
+  icons: {
+16: gwt16.png,
+32: gwt32.png,
+64: gwt64.png,
+128: gwt128.png
+  },
+  plugins: [
+{ path: WINNT_x86-msvc/npOOPHM.dll, public: true }
+  ]
+}
===
--- /trunk/plugins/npapi/prebuilt/gwt128.pngThu Sep 10 07:24:58 2009
+++ /dev/null   
Binary file, no diff available.
===
--- /trunk/plugins/npapi/prebuilt/gwt16.png Thu Sep 10 07:24:58 2009
+++ /dev/null   
Binary file, no diff available.
===
--- /trunk/plugins/npapi/prebuilt/gwt32.png Thu Sep 10 07:24:58 2009
+++ /dev/null   
Binary file, no diff available.
===
--- /trunk/plugins/npapi/prebuilt/gwt64.png Thu Sep 10 07:24:58 2009
+++ /dev/null   
Binary file, no diff available.
===
--- /trunk/plugins/npapi/prebuilt/manifest.json Thu Sep 10 07:24:58 2009
+++ /dev/null
@@ -1,14 +0,0 @@
-{
-  name: GWT Development Mode Plugin,
-  version: 0.9.0,
-  description: A plugin to enable debugging with GWT's Development  
Mode,
-  icons: {
-16: gwt16.png,
-32: gwt32.png,
-64: gwt64.png,
-128: gwt128.png
-  },
-  plugins: [
-{ path: winnt_x86-msvc/npOOPHM.dll, public: true }
-  ]
-}
===
--- /trunk/plugins/npapi/prebuilt/oophm.xpi Mon Aug  3 08:30:11 2009
+++ /dev/null   
File is too large to display a diff.
===
--- /trunk/plugins/npapi/VisualStudio/npapi-plugin.vcproj   Wed Sep  9  
08:52:07 2009
+++ /trunk/plugins/npapi/VisualStudio/npapi-plugin.vcproj   Thu Sep 10  
11:52:42 2009
@@ -63,7 +63,7 @@
Name=VCLinkerTool
AdditionalDependencies=ws2_32.lib
ShowProgress=2
-   
OutputFile=$(ProjectDir)\..\prebuilt\WINNT_x86-msvc\npOOPHM.dll
+
OutputFile=$(ProjectDir)\..\prebuilt\gwtdmp\WINNT_x86-msvc\npOOPHM.dll
LinkIncremental=1

ModuleDefinitionFile=$(ProjectDir)\..\npOOPHM.def
GenerateDebugInformation=true
===
--- /trunk/plugins/npapi/prebuilt/winnt_x86-msvc/npOOPHM.dllWed Sep  9  
14:57:53 2009
+++ /trunk/plugins/npapi/prebuilt/gwtdmp/WINNT_x86-msvc/npOOPHM.dll Thu Sep 
 
10 11:52:42 2009
Binary file, no diff available.
===
--- /trunk/plugins/npapi/prebuilt/gwtdmp.crxWed Sep  9 15:45:43 2009
+++ /trunk/plugins/npapi/prebuilt/gwtdmp.crxThu Sep 10 11:52:42 2009
Binary file, no diff available.

--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors

[gwt-contrib] Re: Introduces inline styles to ui.xml files


Yes, I've been using LGTM with comments to mean go ahead and commit, and
I'll look at the changes afterward.


http://gwt-code-reviews.appspot.com/64812/diff/1/5
File
user/src/com/google/gwt/uibinder/rebind/model/ImplicitCssResource.java
(right):

http://gwt-code-reviews.appspot.com/64812/diff/1/5#newcode138
Line 138: * this package
On 2009/09/10 19:51:09, Ray Ryan wrote:
 I think you just implied that I should change the UiBinder code in
general to
 start using ResourceOracle? If so, I'll put that on the todo list.

It looks like a good idea to me, just because it looks helpful to have a
single API defining what resources come along with the user's code.

http://gwt-code-reviews.appspot.com/64812/diff/1/9
File user/test/com/google/gwt/uibinder/sample/client/UiBinderTest.java
(right):

http://gwt-code-reviews.appspot.com/64812/diff/1/9#newcode281
Line 281: widgetUi.totallyPrivateStyleSpan.getClassName().length()  0);
Okay!  It was just a thought.  If there's not an easy way to dig the
styling back out of the DOM, then so be it.

http://gwt-code-reviews.appspot.com/64812

--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] Re: Introduces inline styles to ui.xml files

2009-09-10 Thread rjrjr


On 2009/09/10 19:54:05, Ray Ryan wrote:


Committed r6114

http://gwt-code-reviews.appspot.com/64812

--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] [google-web-toolkit] r6118 committed - Checking in the htmlunit 2.5 sources, for easier debugging


Revision: 6118
Author: amitman...@google.com
Date: Thu Sep 10 16:21:30 2009
Log: Checking in the htmlunit 2.5 sources, for easier debugging
http://code.google.com/p/google-web-toolkit/source/detail?r=6118

Added:
  /tools/lib/htmlunit/htmlunit-2.5-sources.jar
  /tools/lib/htmlunit/htmlunit-core-js-2.5-sources.jar

===
--- /dev/null   
+++ /tools/lib/htmlunit/htmlunit-2.5-sources.jarThu Sep 10 16:21:30 2009
Binary file, no diff available.
===
--- /dev/null   
+++ /tools/lib/htmlunit/htmlunit-core-js-2.5-sources.jarThu Sep 10  
16:21:30 2009
Binary file, no diff available.

--~--~-~--~~~---~--~~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~--~~~~--~~--~--~---

[gwt-contrib] [google-web-toolkit] r6120 committed - Adds the htmlunit dependency to oophm. ant dist-dev passes...