Chris,
Unfortunately, we have to manually approve posts from new members to
control spam. We typically review postings from new members several
times a day. After that, your posts should appear immediately.
Please, consider removing this manual control spam. It is slowing
down the
Unfortunately, we have to manually approve posts from new members to
. We typically review postings from new members several
times a day. After that, your posts should appear immediately.
Please, consider removing this manual control spam. It is slowing
down the community. We have to wait
This is true, you shouldn't be moderated on each post. Is this not the case?
-- Chris
On Fri, Aug 27, 2010 at 3:39 AM, Shawn Brown big.coffee.lo...@gmail.comwrote:
Unfortunately, we have to manually approve posts from new members to
. We typically review postings from new members several
Hi,
Since I get no response from the GWT dev-team on reported bugs I am
beginning to wonder about the future of GWT. It looks like stability
of the existing features is not very high on the list. I've heard
excuses in all the previous release that you guys were going to sort
out long-standing
Didn't read everything but:
How come I can not use CssResource with the standard widgets of GWT ?
This is easy to do... I even like more the old widgets then the new Cell
widget for css customization.
And as far sa I can tell, a big majority of the bug I've seen so far are
often because the
This is easy to do... I even like more the old widgets then the new Cell
widget for css customization.
Did you try it ?
Because it's hard, and in many cases, espcially with dependent styles
not possible!
Have a look as this issue and the related topic...:
On Aug 26, 7:06 am, Ed post2edb...@gmail.com wrote:
This is easy to do... I even like more the old widgets then the new Cell
widget for css customization.
Did you try it ?
Because it's hard, and in many cases, espcially with dependent styles
not possible!
Have a look as this issue and
When we report bugs on other opensource projects (like struts in the
past or eclipse and many others) the new bug reports are quickly
detected and you get some basic feedback... right now the issue
tracker seems like you guys are using the SUN bug database.
On a note loosely related to
Here's my example... say you want to customize MenuBar from GWT.
You have to declare in your CssResource file some styles.
@ClassName(mesy-MainMenu)
String mesyMainMenu();
@ClassName(mesy-Separator)
String mesySeparator();
Those are my two style, you don't need anything else, since everything
David,
Thank for your honest feedback and your enthusiasm for GWT. Google
uses GWT in many other apps besides Wave and continues to increase
investment in GWT as part of Google's overall interest in improving
user experience on the Web. In addition, it is an open source project
with a very active
To add to David's answer: we use GWT extensively internally and externally
as well. There are a number of products that launch quickly using GWT/App
Engine. One of the ads tools administrative interfaces also runs on GWT.
While Wave was definitely the highest profile GWT application, just keep
Chris,
Unfortunately, we have to manually approve posts from new members to
control spam. We typically review postings from new members several
times a day. After that, your posts should appear immediately.
/dmc
David Chandler
Google Web Toolkit Team
On Aug 26, 9:06 am, chrisr
The @external part is what I don't like. This makes it impossible to
obfuscate and thus optimize the generated code.
The CssResource stuff also has the added benefit that you can not make
a mistake in stylenames since it is checked at compile time.
For the rest of your email, I just want to say
The @external part is what I don't like. This makes it impossible to
obfuscate and thus optimize the generated code.
Yeah well, right, but in that case, it doesn't really matter, in the
following, the only part that will no get obfuscated is : gwt-MenuItem
. The external style you use are the
David,
On Aug 26, 7:54 pm, David Chandler drfibona...@google.com wrote:
David,
At this time, there is a lot of activity around the 2.1 release, and
you can get some sense of this by watching the SVN trunk. In addition,
the GWT team has considerably stepped up maven support (see recent
I've
The @external part is what I don't like. This makes it impossible to
I agree with this (stuckagain was just a bit faster then me...)
Like mentioned in the doc. @external is there for legacy support.
I don't like the write legacy code...
Said that: Especially when having large projects with
I read through the newsgroup thread but I must say I don't agree with
everything that was said there. CssResources are really great, just
too bad that they were not retrofitted to the existing widgets.
I agree with you, I also was a bit suprised that it wasn't fully used
by the GWT widgets,
That is: using Clientbundles/CssResources in reusable components.
Suppose your component has also ImageSources and CssResources and I
want to inject mine such that I change the style and images... How do
you accomplish that?
Yeah well in that case I would have to redesign this in a way
18 matches
Mail list logo
