Hi Gautam,
well, unfortunately I didn't try. I focused in profiling and solving
different parts of the application that were under optimized, as complexity
of merging both activities was a little higher than initially expected. At
the very end, we concluded that performance was acceptable once
Why not say something like: GWT, formerly known as Google Web Toolkit when
run by Google and now simply called GWT when run as an open source project.
Den onsdag 9 december 2015 kl. 07:04:45 UTC+1 skrev Anand, Debasish Gautam:
>
> Unfortunately GWT = GWT web toolkit sounds quite terrible. Anyone
Thank you Stefan. I still feel GWT as a name in itself does a terrible job
in promoting itself and I see the need for finding a better representative
name. Though it could be possibly only myself who sees the need.
Regards,
Gautam
--
You received this message because you are subscribed to the Go
maybe,
but the GWT name has already established a brand name. People know about
it, search engines know about it. IMHO the confusion risk is much bigger
from any gain you might have by removing the G from GWT just because it is
coming from google.
After all, aren't we all coming from somewhere? D
I find it a bit odd. The group reads google-web-toolkit and so as pretty
much everything associated with GWT. How can we possibly expect anyone to
let GWT be pronounced as gwit and not expect them to ask a question as what
it stands for ? GWT in itself is an odd acronym if it doesn't stand for
anyt
> I find it a bit odd. The group reads google-web-toolkit and so as pretty
> much everything associated with GWT.
>
Actually this group is named "GWT Users" (which matches "GWT Contributors",
"GWT Steering"). Only the URL hasn't been changed to not break existing
links to existing discussions
I still think - if one of our goal is to shake off Google from GWT it
deserves a complete name change. An acronym that doesn't stand for anything
is odd IMO and will find few takers. May be we should consider this in 3.0.
On Wednesday, December 9, 2015 at 12:29:26 PM UTC+2, Jens wrote:
>
>
> I
Thanks.. Do you know the name of the runner class used to run GwtTestCase ?
TIA,
Gautam
On Wednesday, December 9, 2015 at 1:22:25 AM UTC+2, Jens wrote:
>
>
> There must be a web.xml used by the embedded jetty somewhere while running
>> the tests - right ? Is this accessible to us to modify ?
>
> May be we should consider this in 3.0.
>
There was already some talk about wether or not renaming GWT when 3.0 is
released as 3.0 will likely be very different. But at the end its a
decision made by the steering group. If they are not sure about it they
will probably do a poll and ask the
> Thanks.. Do you know the name of the runner class used to run GwtTestCase
> ?
>
JUnitShell (which is a subclass of DevMode) sets up the test environment
and executes GwtTestCase.
-- J.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To un
Hello all,
I have found GWT project documentation and examples at website
fantastic. All major subjects are described with nice examples. What do I
really miss there is user login and security (sessions, validation, etc.)
Can't really imagine any web-project without user handling. For su
On Wednesday, December 9, 2015 at 11:29:26 AM UTC+1, Jens wrote:
>
>
> I find it a bit odd. The group reads google-web-toolkit and so as pretty
>> much everything associated with GWT.
>>
>
> Actually this group is named "GWT Users" (which matches "GWT
> Contributors", "GWT Steering"). Only the
GNU's Not Unix.
(note: "Great Web Toolkit" was actually proposed IIRC)
On Wednesday, December 9, 2015 at 7:04:45 AM UTC+1, gau...@ainosoft.com
wrote:
>
> Unfortunately GWT = GWT web toolkit sounds quite terrible. Anyone would
> ask what GWT in GWT stands. By this naming policy we are forcing th
I am using the snapshots version of gwt-bootstrap3 and had no issue
upgrading to GWT2.8.0beta1 yesterday (this is the one I am using to be
absolutely clear: https://github.com/gwtbootstrap3/gwtbootstrap3).
According to me the snapshot version is more stable than the 0.9.3 release
as this conta
Well as for any SPA (Single Page App) authentication and authorization is
a concern of the server and not really the client.
This is how I usually do it:
1.) Make the index.html page dynamic. The backend adds information whether
the user is logged in or not
(http://www.gwtproject.org/article
Is the snapshot available via maven?
On 12/09/2015 07:46 AM, Frank wrote:
I am using the snapshots version of gwt-bootstrap3 and had no issue
upgrading to GWT2.8.0beta1 yesterday (this is the one I am using to be
absolutely clear: https://github.com/gwtbootstrap3/gwtbootstrap3).
According to
whose issue tracker?
gwtbootstrap3's or gwt's?
On 12/08/2015 05:25 PM, Thomas Broyer wrote:
Can you raise it in the issue tracker?
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and stop receiving emails from it
If it used to work previously, then gwt's issue tracker.
On Wednesday, December 9, 2015 at 3:14:02 PM UTC+1, Michael Joyner wrote:
>
> whose issue tracker?
>
> gwtbootstrap3's or gwt's?
>
> On 12/08/2015 05:25 PM, Thomas Broyer wrote:
> > Can you raise it in the issue tracker?
> >
>
>
--
Yo
On 12/09/2015 11:41 AM, Thomas Broyer wrote:
If it used to work previously, then gwt's issue tracker.
For those curious: https://github.com/gwtproject/gwt/issues/9242
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this gr
I get that this is impossible to keep maintaining the previous Dev mode,
but without it GWT cannot be debugged properly anymore.
See the following for example:
http://stackoverflow.com/questions/25105469/how-to-debug-using-superdev-mode
In SDM You cannot watch, it's impossible to check which type
No idea...
But I also should mention that I don't use the Slider anywhere in my
project.
Op woensdag 9 december 2015 15:13:35 UTC+1 schreef Michael Joyner:
>
> Is the snapshot available via maven?
>
> On 12/09/2015 07:46 AM, Frank wrote:
>
> I am using the snapshots version of gwt-bootstrap3 and
Debugging using SuperDevMode is different but definitely not impossible. It
also doesn't cost hours spotting a problem. Eclipse users often use the
Eclipse plugin "SDBG" which allows you to debug your JavaScript code in
your IDE: https://sdbg.github.io . IntelliJ users can do that out of the
bo
Regarding your presentation:
Slide 5 - mentions that GWT 3.0 has "revolutionary use cases". What are you
referring to?
I would add a slide that talks about some of the shortcomings of GWT. For
instance:
Widgets out of the box are somewhat lacking, at least if you want
eye-candy, but html5/css3
On Wednesday, December 9, 2015 at 7:35:38 PM UTC+1, Liraz S wrote:
>
> You have to get the Dev mode back, and to make the legacy Dev mode better
> - not the super dev mode that is aimed to source maps - i think it's a
> mistake.
>
It's not going to please you but 2.8 will be the last release s
I love DevMode, I will miss it :(
Super DevMode, not Super enough for me... (tried it a few times with bigger
apps, got lost in the chrome sources, takes too much time...)
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this gr
25 matches
Mail list logo
