Hi Predrag;
There is not currently an online demo of the framework just yet,
but the prototype application being built with it is designed to make
explaining complex ideas and processes as simple and as concise as possible,
and it will certainly contain tutorials on how the custom elements are
It's interesting how people think differently about the question: "How
software development should look like" :-)
>From the couple of the last posts we can see that:
One person think that James framework is too weird to have any value in it,
other one respects his hard work and wants to learn
On Thursday, January 26, 2017 at 7:33:06 PM UTC+1, Jens wrote:
>
> Wow that looks too weird for me to see any value in it :D
>
+1
I tend to remove as much "magic" as possible from my projects, even if that
means writing 2 lines of code instead of 1, trying to have the code be as
explicit as
@James, do you have any working example (link to some site where
application is hosted or youtube video of locally running application) of
your framework that you can share with us ?
Can you create something like this http://petclinic.cloudapp.net/ with your
framework and then to demonstrate
Wow that looks too weird for me to see any value in it :D
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
So, a little late to jump in, but figured I'd add my $0.02 to this
conversation.
I've been hard at work building a future-oriented declarative UI DSL.
Specifically, I extended the Java 8 JavaCC parser to include xml, json and
css expression syntax.
This allows creation of UI's like the
David,
Here is the post about Meta approach you asked for:
http://www.codeless.solutions/#!Meta-Platform-survival-guide/enstx/566ac8fc0cf239106876cf13
I believe it will give you the answer on your post question or at least an
idea what you can do next.
Kind regards,
Predrag.
--
You
Yes, very nice city I know. I been there couple of times ~ 10 years ago
when I was living in Rotterdam.
On Tue, Nov 24, 2015 at 9:38 AM, David wrote:
> Thanks for the info.
>
> And don't worry, Leuven is still a peaceful and quite city which is worth
> a visit thanks to
> Typescript uses type definitions for 3rd party JS libraries (
http://definitelytyped.org/). Potentially something similar could be done
for GWT/Java or even one could leverage the Typescript type definitions to
automatically create Java wrappers.
I'm working on a tool that could convert these
did you post any articles about the design of your meta approach - I'm very
interested in reading a bit about it to see if I can learn from it ? I've
seen similar approaches where an XML representation was used (looking a lot
like XUL syntax), but I had to help in improving the performance and
Good points and in most cases we are covered:
- Using a Command Processor over GWT-RPC, but I will move it to a REST
implementation.
- GUI is split up in MVP and the important code is not depending on any GWT
widgets or anything else.
We are using UiBinder in our current application, but
Good points and I agree with almost all you said ;-) We did not notice any
performance degradation by using meta approach comparing to manual or
UIBinder way, but that is something that we will try to demonstrate in the
following weeks. Well, we do not have to support IE6/IE7 so this would be a
No, but intend to will write a blog or an article about this. I will let
you know when it's done. Probably in a few weeks as I need to write some
other things before this.
In the meantime, you can take a look here: http://www.codeless.solutions or
here:
This is very good question and actually one of the biggest problem not only
in this particular situation but also in general software development.
Imagine you decide to build something large like ERP or Banking Information
system for an example (with hundreds even thousands of tables and
I think I need to make a few clarifications.
We (we as in Google) are not planning to go on delete any code from GWT-SDK
after 2.8 release.
Yes, we believe Widget, GWT-RPC, RF etc. reached end of its useful life and
we will not invest on them anymore however if there is enough
interest/demand
Exactly, although future releases of GWT will still allow you to create
your UI components (you have access to the DOM tree), the point is to reuse
external widget collections instead of reinvent the wheel.
Obviously nowadays UI designers are much more comfortable writing
components using html +
On Monday, 16 November 2015 18:52:50 UTC, Jens wrote:
>
>
> I'm not talking about a re-write here, I'm talking about new projects. For
>> new projects, I can't see a compelling reason for picking GWT, if the devs
>> are going to have to understand JS to use GWT then it is better to invest
>>
Keep in mind at Google, we write lots of large Web projects, and even the
ones that are pure JS (G+, Gmail, Docs, Maps, etc) use Closure Compiler and
lots of typing. We find it invaluable.
But the world is going mobile, and going forward, you need to support
Android, iOS, and Web, and you need to
Thomas gets it all correct. I just want to add one thing: If you are happy
with the current GWT stack (uibinder + widget ...), stay with it. As I
mentioned during the key notes, the GWT 2.8 will be a long maintenance
release and you have now everything you need to do a great web app.
Don't try to
On Monday, 16 November 2015 12:34:51 UTC, Thomas Broyer wrote:
>
>
>
> On Monday, November 16, 2015 at 11:29:14 AM UTC+1, Robert Stone wrote:
>>
>>
>>
>> On Sunday, 15 November 2015 15:37:29 UTC, Stephen Haberman wrote:
>>>
>>>
>>> My worry about "just pick a mainstream JS framework and use it
On Monday, 16 November 2015 12:51:35 UTC, Thomas Broyer wrote:
>
>
>
> On Monday, November 16, 2015 at 1:28:16 PM UTC+1, stuckagain wrote:
>>
>> Thanks for all the feedback. But it does not put my mind at rest right
>> now.
>>
>> It would have been much better if GWT 2.8 would have provided
On Monday, November 16, 2015 at 11:29:14 AM UTC+1, Robert Stone wrote:
>
>
>
> On Sunday, 15 November 2015 15:37:29 UTC, Stephen Haberman wrote:
>>
>>
>> My worry about "just pick a mainstream JS framework and use it via
>> JSInterop" is that if you're a) coupled to a JS environment for unit
On Monday, November 16, 2015 at 1:28:16 PM UTC+1, stuckagain wrote:
>
> Thanks for all the feedback. But it does not put my mind at rest right
> now.
>
> It would have been much better if GWT 2.8 would have provided at least the
> basis for the future of GUI development - because that was
David Chandler from Sencha answered a question about widgets and GWT 3.0:
https://www.sencha.com/forum/showthread.php?306057-GWT-3.0-Sencha-GXT-and-the-future-of-the-widget-eco-system-
"Thanks for the kinds words about GXT. We still don't have any more info on
GWT 3 than what has been
Thanks for all the feedback. But it does not put my mind at rest right now.
It would have been much better if GWT 2.8 would have provided at least the
basis for the future of GUI development - because that was one of its main
selling points for me.
I understand why element/widget/uibinder are
> I'm not talking about a re-write here, I'm talking about new projects. For
> new projects, I can't see a compelling reason for picking GWT, if the devs
> are going to have to understand JS to use GWT then it is better to invest
> up front time in getting them familiar enough with JS to use
> I guess I will be trying UiBinder with GQuery and not rely on Widget for
> my project. The UiBinder might disappear, but we are using mostly plain
> HTML and Bootstrap styles. So we are only interested in binding events. The
> UiBinder templates will be easy to migrate later on.
>
FWIW this is
Errai UI ?
On 17 Nov 2015 00:41, "Stephen Haberman" wrote:
>
>
>> I guess I will be trying UiBinder with GQuery and not rely on Widget for
>> my project. The UiBinder might disappear, but we are using mostly plain
>> HTML and Bootstrap styles. So we are only
My hope would be that some enterprising individuals will start porting
pieces of GWT generators to annotation processors in the future. Some of
them are definitely doable without much effort
(CssResource/ClientBundle/etc) Some of them will require more work, but are
still possible (UiBinder with
On Sunday, 15 November 2015 15:37:29 UTC, Stephen Haberman wrote:
>
>
> My worry about "just pick a mainstream JS framework and use it via
> JSInterop" is that if you're a) coupled to a JS environment for unit
> testing and b) interfacing with a framework that is inherently
> dynamic/untyped,
This is an interesting question (what to use for a greenfield GWT
project)...
> UiBinder: Would need a rewrite to use APT. I guess no one has looked into
> it yet. One main issue is that APT won't get triggered when updating
> resources (*.ui.xml)
>
Yeah, I would probably skip APT and just use
>
> Yeah. The conundrum for me is that I'm addicted to the pure-JVM unit
> testing/debugging that MVP gives you.
>
I believe Angular controllers, Flux Stores etc. can be just as
JUnit-testable as MVP, when implemented in Java and exposed through
JsInterop.
There is a lot of pioneering to do,
>
> The important thing is to keep an open mind, not trying to force JS
> frameworks into our current best practices, and willingness to be inspired
> by the best practices of the chosen JS framework.
>
> Our best practices has emerged from the constraints of GWT, and those
> constraints has just
I think you get it all correct; in particular J2CL != GWT3.
J2CL is a separate/unbundled "Java to Closure style ES6" transpiler that
Google works on and only shares the JRE emulation and JsInterop from
GWT-SDK. There is an intention to open-source it when it is ready and
J2CL+JsCompiler together
David Chandler made a statement regarding Sencha GXT:
https://www.sencha.com/forum/showthread.php?306057-GWT-3.0-Sencha-GXT-and-the-future-of-the-widget-eco-system-
--
You received this message because you are subscribed to the Google Groups "GWT
Contributors" group.
To unsubscribe from
I was at GWTcon, and my perception of Juliens keynote and his presentation
on JSInterop was, that he used AngularJS to demonstrate that it is now
possible to use a JS based framework with GWT 2.8 through JSInterop, and to
show solutions to common issues you might run into while doing so.
Which
Well if you want to switch to J2CL in the future and you want to be
absolutely sure that you actually can switch then you should not use any
GWT library/framework and GWT SDK features that can not guarantee to work
with J2CL.
GXT/Vaadin: You should ask them about their plans regarding J2CL
37 matches
Mail list logo