Thanks for your message,
Very good idea about transpiling jquery! I was hoping to ship that
immediately but jquery shown me darker side of typing defintions with
typescript, so there are a lot of bugs I didn't see at first on my tool
(angular is written in an oop style) I need to fix now.
Let me
Thanks Joseph,
Not right now, I still need to adjust a few things..
I will let you know when Tour of heroes and all other ANgular 2 samples
will have been ported to Angular 4
Thanks
Arnaud
Le ven. 29 sept. 2017 à 11:09, Joseph Webber a
écrit :
> This is totally awesome!
Why not make a polyfill on the native js array loaded with the gwt runtime
(dynamically adding needed functions on it) so that it conforms to the Java
array type?
Would be ok to do that 99%of the time I think.
It would simplify so much interoperability between them, IMHO...
Arnaud
Le jeu. 3 août
About the iframe instanceof problem, I think this is due to the fact that
JavaScript prototypes do not cross frame boundaries (for security and
privacy reasons). So even in JavaScript, the instanceof operator would not
work.
You can try this example :
let frame =
Thanks for the info. Did you write it in Java? I found it very natural to
write "TS 2 Java" in typescript, using the typescript compiler API and
generated ast directly.
I wonder how we could coordinate our efforts to get something usable
sooner...
Do you have plans to do the translation the other
union types).
The typescript 2 jsinterop tool I made is not ready yet, but capable of
translating the Angular 2 api into JsInterop, and should also be usable to
integrate other js librairies (when they have a correct TS def file on
definitely typed).
Thanks
Arnaud
Le jeu. 6 avr. 2017 à 19:44, Arnaud
Perfect time ! Thanks for the hard work!
Arnaud
Le jeu. 6 avr. 2017 à 12:49, <
google-web-toolkit-contributors@googlegroups.com> a écrit :
> google-web-toolkit-contributors@googlegroups.com
>
anged... Is
that better or worse ? I don't know, it's different... and also the same !
Java will be dead one day, and Javascript will also be dead one day, that's
just how it goes, nothing lasts forever.
Peace,
Thanks
Arnaud Tournier
Le jeudi 12 janvier 2017 22:43:57 UTC+1, sanny...@gmail.com
Makes sense! So better to have a "nostrict" option for the special cases
Thanks
Le sam. 10 sept. 2016 14:57, Jens a écrit :
>
> Thank you I will try that -strict option.
>>
>> My suggestion is that exported @JsType (when the -generateJsExport option
>> is turned on)
WT does not see the class,
> much less know it is a JsType. Strict mode should give you an error in this
> case.
>
> On Fri, Sep 9, 2016 at 6:09 AM, Arnaud TOURNIER <lte...@gmail.com
> > wrote:
>
>> I have one problem which is recurring, related to JsInterop.
>>
he problem is not that the compile does not work, but that no
useful message is generated to understand the error.
For this one, i can give you the code, but privately since it is a business
app that is not open source...
Thanks !
Arnaud Tournier
LTE Consulting
Le jeudi 8 septembre 2016 16:2
@JsOverlay
> default void resolve(Promise value) { resolve(value); }
> }
>
> Let's us know before it is too late if you hit any bugs around this :)
>
>
> On Tue, Aug 30, 2016 at 7:13 AM, Arnaud TOURNIER <ltea...@gmail.com>
> wrote:
>
>> Oh thanks! I'll try that
hen overload the function so that it took
> each of the resolver interfaces.
>
>
> On Saturday, August 27, 2016 at 9:51:50 AM UTC-4, Arnaud TOURNIER wrote:
>>
>> Hi,
>>
>> I am playing with js Promises and maybe there's a problem with JsInterop
>> or i don't
er, I'm not a JsInterop expect, but I'm trying to learn quickly.)
>
> On Sat, Aug 27, 2016 at 8:51 AM Arnaud TOURNIER <ltea...@gmail.com> wrote:
>
>> Hi,
>>
>> I am playing with js Promises and maybe there's a problem with JsInterop
>> or i don't underst
Hi,
I am playing with js Promises and maybe there's a problem with JsInterop or
i don't understand something.
When wrapping the promises with JsInterop, i come to define the Resolver
interface which represents the resolving callback that is given when
constructing a promise. In Javascript it
M UTC+2, Daniel Kurka wrote:
>>>
>>> It's not my desktop machine, but you are right I did the final
>>> compilation of the release. I thought we had already killed of gwttars
>>> anyway.
>>>
>>> On Thu, Jul 2, 2015, 11:21 AM Arnaud TOURNIER <l
Hi !
I have a question : do you already plan that the JsInterop spec will be the
same to be implemented in GWT 3.0 ?
Meaning, if one invests time to master the new JsInterop api, will he have
to learn something new when switching to GWT 3 or most of the concepts will
stay (which i both hope and
, Arnaud TOURNIER ltea...@gmail.com a écrit :
It's a project of one of my customers which is on gwt 2.6 and needs to
migrate to 2.7.
In the cours of doing that, i got this errors...
If you need, i can investigate a bit more, but seems to be coming from
those [ERROR] java.lang.String cannot
Hi Daniel,
Just to say : the more i think about this new GWT compiler, the more i
think it's the right choice for GWT !
Great work to you all !
Arnaud
Le jeudi 18 juin 2015 14:37:31 UTC+2, Daniel Kurka a écrit :
One other thing: It won't matter which system we use to build the new
Just dumping a bit of errors i get for a project :
Tracing compile failure path for type 'java.lang.Object'
[INFO] [ERROR] Errors in 'file:
*/usr/local/google/home/dankurka/gwt/user/super/co*
m/google/gwt/emul/java/lang/Object.java'
[INFO] [ERROR] java.lang.String cannot be
juil. 2015 à 18:20, 'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com a écrit :
Hi Arnaud,
how are you producing these?
-Daniel
On Wed, Jul 1, 2015 at 9:06 AM Arnaud TOURNIER ltea...@gmail.com wrote:
Just dumping a bit of errors i get for a project
kinds of JavaScript build tools.
On Thu, Jun 18, 2015 at 1:16 PM Arnaud TOURNIER ltea...@gmail.com wrote:
Hi everyone,
I've been watching an reflecting upon the gwt meetup you had few weeks
ago. And one of my concern is about a decent build system that gwt should
be based upon. As for now
Hi everyone,
I've been watching an reflecting upon the gwt meetup you had few weeks ago.
And one of my concern is about a decent build system that gwt should be
based upon. As for now, Bazel is not ready for Windows, and also it needs
to be installed, configured and so on, which can be
Ok great ! True that Google will always have the master hand over GWT, fair
because code is committed by almost only google people ! Community has to
keep that in mind.
Thanks
Arnaud
Le jeu. 18 juin 2015 à 14:37, Daniel Kurka danku...@google.com a écrit :
One other thing: It won't matter which
Jeff Larsen larsenje@... writes:
From 2.1 on it has databinding added. Check out the editor framework.
http://code.google.com/p/google-web-toolkit/wiki/Editors
I suggest you try HexaBinding, which is non invasive and only focused on
data binding. Here is the link :
Hi Jens,
True that HexaCss allows for theme switching, but it is only a side effect
of what it really allows : to have multiple css files bound to the same gwt
application, without needing to recompile the application.
For example, you might want to rebrand your application for another
customer,
Not exactly because the css files are typically served from the war file.
You could of course host them on a CDN so that you don't have to redeploy
your war (but then you need an internet connection and your application
will depend on it to have the CSS, which i find OK only if your application
is
Thanks Jens for your advice,
i will definitely change the text on the website in the way you said it.
Obvisouly i lack skills in communicating !
Thanks again !
Arnaud
Le ven. 24 avr. 2015 à 21:46, Jens jens.nehlme...@gmail.com a écrit :
I am not sure i am really clear in my explanation, but
Thanks Ed, i will have a look at Errai again, last time i did i focused on
other parts and missed the theming parts...
Arnaud
Le ven. 24 avr. 2015 à 21:53, Ed Bras post2edb...@gmail.com a écrit :
Have a look at the RedHat Errai templating mechanism.
Errai is setup in modules (jar's), so you
Cool, but sometimes CSS is not about just colors !
You may want to change the structure of the CSS between themes. For example
one theme would have the checkboxes styled so they look as iOS ones
(through some known CSS tricks with ::content and so on) and other times
you might want them to appear
prioriticize the features and organize contributions...
Thanks
Arnaud
Le sam. 4 avr. 2015 à 11:37, Arnaud TOURNIER ltea...@gmail.com a écrit :
Hi Ed,
This project is indeed used in one big application in production (100k+
loc on the client side).
I use it mainly to maintain 3 different
it works well, i had the idea to extract it from the main project
and give it to the community.
So of course, there might be some work to be fully industrialized, in order
to adapt to any context.
Any contribution, idea and so on is of course welcome !
Thanks
Arnaud Tournier
Le ven. 3 avr. 2015 à
/ltearno/hexa.tools
Of course, it is open source and will stay so !
Stay tuned, because i have other announcements to make soon
Please tell me if you find the idea interesting and if it might help you. I
also very much welcome anyone wishing to contribute to this project !
Thanks
Arnaud Tournier
, 2015 at 11:08 AM, Arnaud TOURNIER ltea...@gmail.com
wrote:
Hello Everyone,
I come up here to let you know about a library i build, aiming at
integrating efficiently any CSS framework with GWT.
This allows your application to type-safely use Sass, Less, Susy, GSS,
vanilla css or any
Please tell me if you find the idea interesting and if it might help
you. I
also very much welcome anyone wishing to contribute to this project !
Thanks
Arnaud Tournier
www.lteconsulting.fr
twitter : @ltearno
--
You received this message because you are subscribed
You may check the sdbg project which aims to drive the chrome debugger from
eclipse.
You get an experience really close to the old dev mode, like working with
breakpoints from eclipse
Thanks
Arnaud
Le mar. 25 nov. 2014 11:55, null
google-web-toolkit-contributors@googlegroups.com a écrit :
Can that be an option ? So that the user knows what happens consciously, in
order to optimize the runtime. I admit, that this would not simplify the
jscompiler base code, but would provide the user with another powerful
optimization...
Just an idea...
Thanks
Arnaud
Le vendredi 21 novembre
Hello,
I totally agree on your first two points. I would add a third which is that
since this SAM functionnality will be very essential to javascript
interoperability, it will be used a lot (already in some projects i am
eagerly waiting for this to be implemented, instead of writing my own
By adding the -XjsInteropMode JS option, the thing should work.
Le mardi 30 septembre 2014 12:55:57 UTC+2, Michael Vogt a écrit :
Hello.
Should it be possible right now to use JsInterop to use the facebook
Javascript sdk?
The call I want to use is FB.XFBML.parse
So I created 2
the experience
Thanks a lot again for all the work and the good things coming out !
Arnaud
Le lundi 1 septembre 2014 12:25:38 UTC+2, Daniel Kurka a écrit :
Hi Arnaud,
are those 10s after the changes we made or before?
-Daniel
On Mon, Sep 1, 2014 at 12:02 PM, Arnaud TOURNIER lte...@gmail.com
Thanks to all of you who participated to this very good things !
I am now able (from the trunk) to have a great experience debugging with
Gwt + Eclipse + Sdbg + Chrome.
I cannot be quantitatively very precise but the latest optimization
(-XcompilePerFile) seems to give good results. My project
'Daniel Kurka' via GWT Contributors
google-web-toolkit-contributors@googlegroups.com:
Hi Arnaud,
are those 10s after the changes we made or before?
-Daniel
On Mon, Sep 1, 2014 at 12:02 PM, Arnaud TOURNIER ltea...@gmail.com
wrote:
Thanks to all of you who participated to this very good
.
http://www.lteconsulting.fr/jpa-for-gwt.html
Thank you all !
Arnaud Tournier
http://www.lteconsulting.fr
--
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 it instead of
rolling with a yet a new library ?
Sounds good though :)
2013/11/27 Arnaud TOURNIER ltea...@gmail.com
Yes i know ERRAI but :
- You can only execute very simple queries,
- You cannot use any joins or nested attribute retrieval,
- All queries should be parsable
I completely agree with this point ! It should be fast enough so that
browser doesn't seem sluggish.
Arnaud
2013/11/27 Jens jens.nehlme...@gmail.com
- You can only execute very simple queries,
- You cannot use any joins or nested attribute retrieval,
- All queries should be
45 matches
Mail list logo