to open an issue in order to track
this.
On Thursday, April 2, 2015 at 4:24:03 AM UTC+2, Abraham Lin wrote:
The GWT distribution currently contains an InterfaceGenerator tool for
generating CssResource interfaces from a CSS source file; however, this
tool is still using the old Flute parser
The GWT distribution currently contains an InterfaceGenerator tool for
generating CssResource interfaces from a CSS source file; however, this
tool is still using the old Flute parser and thus does not support CSS3
syntax.
Is there any chance that this tool will be overhauled/ported to support
I believe I came across this as well (see issue
8251https://code.google.com/p/google-web-toolkit/issues/detail?id=8251).
I wasn't able to pinpoint the root cause as you did, but there's a test
case attached to the issue that might be helpful.
--
You received this message because you are
Integer#compare(int, int) was added in Java 7, which isn't supported by GWT
2.5.1.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
On Sunday, March 17, 2013 8:06:00 AM UTC-4, Thomas Broyer wrote:
Also, one thing to discuss asap is where to put the sources: say I have
lib-shared and lib-client, would you bundle the sources of lib-shared into
the lib-client JAR or rather just have a dependency from lib-client to the
What you want is the margin property, not the padding property.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
What you really want is
#setHref:
http://google-web-toolkit.googlecode.com/svn/javadoc/latest/com/google/gwt/user/client/ui/Anchor.html#setHref(java.lang.String)
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this
This is typically caused by incorrect project classpath settings (check the
includes/excludes for the resources folder). It's not clear whether m2e or
GPE is to blame here.
-Abraham
On Mon, Jan 28, 2013 at 4:02 AM, Olivier NOUGUIER
olivier.nougu...@gmail.com wrote:
Hum
Sorry to say, that
Have you tried using either of DockLayoutPanel or LayoutPanel? Since you're
already using layout panels, it should be fairly straightforward to use
absolute positioning to create three DIVs of approximately equal width.
Then you can just set the text-align property for each DIV as necessary.
Looks like there's an extra comma on line 20 (right before the opening
brace). Not sure why the line number is off, but the column offset is
correct.
-Abraham
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the
I think that Joerg's proposal is exactly what you're looking for, though
what may not be immediately obvious is how the various components relate to
one another. The basic idea is that myproject-componentN-client depends on
myproject-componentN-shared and that myproject-componentN-server
It comes without saying (for me at least) that Java sources would go into
src/main/java and public resources (i.e. the things within **/public/**,
e.g. the CSS and image files from the themes) into src/main/resources
I agree with this.
everything in src/main/java
super-sources in
This is option 3 then (you agreed that It comes without saying (for me at
least) that Java sources would go into src/main/java, and I suppose that
by public resources you mean not only **/public/** but also *.ui.xml and
the like)
Ah sorry, I had misread your definition of everything to
This is specified by Java and is by design. The rationale is here:
http://docs.oracle.com/javase/tutorial/essential/exceptions/runtime.html
-Abraham
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
On Wednesday, October 24, 2012 5:41:06 AM UTC-4, Flying-w wrote:
I am investigating security considerations around the user login for a GWT
application in respect of the following strategy:
- User enters their id and password in a dialogue;
- Client transmits the login request with
The path rewriting should be done by the proxy, not by your code. What are
you using as the proxy?
-Abraham
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
Use the
ProxyPassReverseCookieDomainhttp://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassreversecookiedomain
and
ProxyPassReverseCookiePathhttp://httpd.apache.org/docs/2.2/mod/mod_proxy.html#proxypassreversecookiepath
directives
in your httpd config. Depending on how your virtual
One possibility is to replace the FlowPanel with an HTML widget, generate a
SafeHtml instance containing your raw HTML, and then call the #setHTML
method. You could also build the markup using the DOM API, though that will
almost certainly be slower and more verbose.
GWT adds wrapper DIV/SPAN
Does your JAR file contain the source code for your library? The GWT
compiler needs to have access to the source files, not just the compiled
class files.
-Abraham
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion
Add the root of your super-source folder as a source folder (right-click
the folder, open the Build Path submenu, and click Use as Source
Folder). Eclipse should automatically make the necessary modifications to
the parent source folder, but you might want to check to make sure.
-Abraham
--
On Friday, October 5, 2012 10:47:33 AM UTC-4, Thomas Broyer wrote:
Don't do that: Eclipse will then compile you super-source and you then
risk making your non-client code using those classes fail (unit-tests,
server-side, etc.)
Ah, that's true. I'm used to separating client and server
On Friday, October 5, 2012 1:46:54 PM UTC-4, Thomas Broyer wrote:
It's not only about client vs. server, it also affects non-GWTTestCase
unit tests of your client code.
This doesn't seem right. Given that your client classes will be relying on
the super-sourced logic at runtime, why
On Tuesday, September 11, 2012 3:54:55 PM UTC-4, Thomas Lefort wrote:
This is my code for the anchor
AnchorElement anchor =
DOM.createAnchor().cast();
anchor.setHref(#EISearchResultPlace: +
result);
You'll need to set the encoding as part of the Content-Type header:
builder.setHeader(Content-Type, application/x-www-form-urlencoded;
charset=UTF-8);
The default encoding is ISO-8859-1, which does not support the euro symbol
(I believe the standard was established prior to the formation of
I just re-read your original post, and I think the problem is that you're
using utf8_decode on the server side. According to the
documentationhttp://php.net/manual/en/function.utf8-decode.php,
utf8_decode converts a UTF-8 string into ISO-8859-1, which doesn't support
the euro symbol. Have you
The keypress event tends to be handled inconsistently by different
browsers/environments: http://www.quirksmode.org/js/keys.html
As noted in the link above, you should probably stick with keyup or keydown
events.
-Abraham
--
You received this message because you are subscribed to the Google
the only empty DIV I see is the label, and it's empty because the label
does not contain text.
Right, and that's why it has zero height as you observed.
Do you agree to the statement posted in this thread that the GWT's layout
panels should be used for the overall page layout
I think you're misunderstanding how GWT works. Everything written using GWT
compiles down to HTML, CSS, and other native web technologies - there is
no difference between panels (LayoutPanels or otherwise) and widgets as far
as mapping goes.
What seems to be the issue here is that the
What could possibly help is to precompile the modules into *.gwtar files,
but it's something that's supposed to only be used by GWT itself (you'll
find such gwtar files in the gwt-user.jar) AFAIK. At least it's not
designed to build libraries, as the gwtar files depend on the version of
In sample/pom.xml, add the following after line 34 (after
artifactIdgwt-maven-plugin/artifactId):
version${gwtversion}/version
Then add the following between /plugins and /build (following line
71 after the first step):
pluginManagement
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
Why don't you define a CSSResource with the shared rules and import it
where needed? See
https://developers.google.com/web-toolkit/doc/latest/DevGuideClientBundle#Imported_scopes
(and
possibly
https://developers.google.com/web-toolkit/doc/latest/DevGuideClientBundle#Shared_scopes
depending
The following should work:
yourQuery site:developers.google.com/web-toolkit/
You can use the same construct in the general Google search engine.
-Abraham
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the
32 matches
Mail list logo
