Hi Thomas,
I'm (part-time) having a look at your gwt-sandbox with maven build;
I like the way it is modularized:
gwt-dev-parent
gwt-jsni-parser
gwt-util-parent
gwt-shared
gwt-tools-api
gwt-dev-json
gwt-dev-ext
gwt-user-parent
gwt-core-shared
gwt-core-client
gwt-compiler
gwt-maven-plugin
I'm a little bit late in this discoussion, i see there is a lot of work
already on going.
But +1 for this.
SASS or LESS would be a big plus.
For me I think supporting OOCSS is more important than supporting CSS3
without workarounds.
Thank you guys!
Sam
On Friday, December 16, 2011 11:51:43 PM
Hi to all contributors
I'm developing with GWT since two years and now i want to contribute to GWT.
I checked out the GWT Source Code with
git clone https://gwt.googlesource.com/gwt trunk
But I don't understand how to setup my eclipse project.
Does somebody have some hints for me?
Sam
--
Have you tried following the eclipse/README.txt?
BTW, you also need to svn checkout
http://google-web-toolkit.googlecode.com/svn/tools;
On Wednesday, September 25, 2013 11:13:06 AM UTC+2, Samuel Schmid wrote:
Hi to all contributors
I'm developing with GWT since two years and now i want to
No i did't saw that. Thanks for the hint. I'll check this and come back if
I stuck.
Sam
On Wednesday, September 25, 2013 12:15:27 PM UTC+2, Thomas Broyer wrote:
Have you tried following the eclipse/README.txt?
BTW, you also need to svn checkout
The biggest problem with being a GWT contributor today is that it is hard,
very hard, to set up an environment to develop. If you look at the original
GWT instructions for Eclipse, and that was *with* already provided
.project/.classpath files, it was ridiculous. Starting from scratch is even
Its never too late - I don't know how far Julien has gotten, but I've been
distracted by other work, as well as trying to nail down conceptually where
GSS meets ClientBundle.
For my part, SASS or LESS are a major step down from what we already have -
the purpose of GWT in general is to let you
As a stop-gap measure, can you clean up and check in your IDEA module(s)?
- Brian
On Wed, Sep 25, 2013 at 9:20 AM, Ray Cromwell cromwell...@google.comwrote:
The biggest problem with being a GWT contributor today is that it is hard,
very hard, to set up an environment to develop. If you look
On Wednesday, September 25, 2013 6:20:19 PM UTC+2, Ray Cromwell wrote:
The biggest problem with being a GWT contributor today is that it is hard,
very hard, to set up an environment to develop. If you look at the original
GWT instructions for Eclipse, and that was *with* already provided
I've shared an item with you:
GWT 2.6 Release Plan
https://docs.google.com/document/d/1ZdMwcTjc4rkWg6nntCY1BDB1xI2PHPwaCnTYw-9uAKE/edit?usp=sharing
It's not an attachment -- it's stored online. To open this item, just click
the link above.
--
Hi Thomas,
today I've tried to test the build with buck, but it has not worked for
me...
On the root, the command buck build asks to specify a build target, while
buck targets prints lots of empty lines then it rise a RuntimeException:
Not an ordinary file:
On Thursday, September 26, 2013 1:47:22 AM UTC+2, Cristiano wrote:
Hi Thomas,
today I've tried to test the build with buck, but it has not worked for
me...
On the root, the command buck build asks to specify a build target,
while buck targets prints lots of empty lines then it rise a
Thomas,
In terms of Gradle vs Buck models, is there any possibility of writing a
tool that takes a Buck build file and produces Gradle files? That would
seem like a good option in lieu of waiting for Buck support in IntelliJ and
Eclipse. This isn't to say I have anything against Buck, it is
13 matches
Mail list logo
