Monday, April 13, 2020

Debug Ids for Tree items via TreeStore

Hi,

I want to generate debugIDs for a Tree Object

tree = new Tree<CustomType, String>(store, valueProvider);

tree.ensureDebugId("properties-tree");


above code generates the ids for tree root node but for all the items in the tree have automatic ids.


Tree items are created via TreeStore. How can I set the ids for tree items ?


Thanks,

Manpreet



--
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, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/97658b3d-9980-45d9-a1ac-8bd43e75f0a2%40googlegroups.com.

Monday, April 6, 2020

GWT DataGrid CheckBoxSelectionModel Issue

Hello Guys!

I have an issue with GWT Grid using CheckBoxSelectionModel, my ListStore is loaded by default with all the elements (checkboxes) selected and they are locked because they didn't change by user. So when i click on a column header the sort event deselect all ListStore elements. I've tried a lot of examples like handler the sort event or selectionChangedEvent but i can't find out what i missing. 

Someone have an idea? 

P.S: My english is very bad, sorry about that!
Thanks!

--
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, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/65909706-4f71-46f4-af21-13044a9063c8%40googlegroups.com.

Sunday, April 5, 2020

Re: [ANN] Sting v0.13 (Beta) release

On Sun, Apr 5, 2020 at 7:55 PM foal <sspiridonov@gmail.com> wrote:
> Does Sting support the GWT "Code Splitting"? (http://www.gwtproject.org/doc/latest/DevGuideCodeSplitting.html), I tried to migrate from GIN to the Dagger, but it was the main issue why I still use the GIN.

Sting does not do it much differently than Dagger. It has been a while
since we used code-splitting but I believe all you would need to do is
use an interface to define the service and instantiate the service
implementation behind a split point from a provider method in a
@Fragment annotated type. (A similar approach should be achievable in
dagger but putting the split point in a @Provides annotated method in
a @Module but I have not checked daggers generated code to make sure
it would still work)

So, in theory, it should be fine but I have yet to try it myself ;)

--
Cheers,

Peter Donald

--
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, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc6Sy8yW28wXt%2BV4mEG%2B4E6it7Gif7RVeqhZBH-oavByOQ%40mail.gmail.com.

Re: [ANN] Sting v0.13 (Beta) release

Hi, 

Does Sting support the GWT "Code Splitting"? (http://www.gwtproject.org/doc/latest/DevGuideCodeSplitting.html), I tried to migrate from GIN to the Dagger, but it was the main issue why I still use the GIN.

With Dagger, I had tried to do the same as https://github.com/ibaca/gwt-dagger2-coffee, but in my case id didn't work.

Best,
Stas

On Monday, March 30, 2020 at 11:59:27 PM UTC+2, Peter Donald wrote:
Sting is a fast, easy to use, compile-time dependency injection toolkit.
If you are familiar with Dagger, it is a replacement for Dagger that is
more optimized for the web context and GWT/J2CL.

We have been developing Sting for a while as we were not satisfied with
existing solutions but we have recently reached a point where we have
replaced all of our existing dependency injection solutions (GIN,
Dagger2 and some home-grown variants) with Sting and we think it is
ready for other people to give it a try. So we are looking for feedback
from anyone who is interested in giving it a try.

We have set up a documentation site at

  https://sting-ioc.github.io/docs/overview.html

But to get a feel for what the code looks like. A component is
defined by adding the @Injectable annotation to the class such as:

  @Injectable
  class MyFancyService { ... }

However, we also support a @Named annotation and @Typed annotation
that is similar in practice to the same-named annotations in CDI
applications that add a qualifier to a component or control the types
with which a component is published. We also support an @Eager
annotation to ensure a component is instantiated when the injector is
constructed.

We also have the equivalent of daggers modules in the form of
fragments where you can programmatically create components by writing
code such as GWT.create(MyBackendServiceAsync.class)

So why choose Sting over something like Dagger? We did write up a
comparison at

  https://sting-ioc.github.io/docs/dagger.html

However, it is a little blunt and I will probably soften the points in
it a little (it was written for an internal audience initially).
The main reason to adopt Sting is that it is easier to use and it
produces smaller, faster and easier to optimize code.

Anyhoo, if anyone is looking for a dependency injection framework,
here is another to try and we would really appreciate the feedback.

Thanks,

Peter Donald

--
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, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/5aa250b4-943b-4ae4-81f1-09a3a275bb53%40googlegroups.com.

Re: GWT project data grid double scroll issue in edge browser

But this is not working for me

On Wednesday, May 29, 2019 at 6:44:51 PM UTC+4, hy wrote:
This is a known issue, I have encountered it in past. See: https://groups.google.com/forum/#!topic/google-web-toolkit/xxeS6LETdBs

The way I fix it is by adding the following css to the page:

/*Fix for extra scroll bar in celltables*/
::-webkit-scrollbar {
    width
: 10px;
}

::-webkit-scrollbar-thumb {
    width
: 10px;
   
-webkit-border-radius:3px;
    border
-radius:3px;
    background
:rgba(0,0,0,0.3);
}
/*End Fix for extra scroll bar in celltables*/




On Wednesday, May 29, 2019 at 5:17:35 AM UTC-4, Thomas Broyer wrote:
As you can see in your screenshots, columns are not aligned with their headers. This is the reason GWT (tries to) hide the native scrollbars, and "replaces" them with translucent ones (the one you've hidden).


I don't remember how all of this is done, so can't tell if it's a bug in GWT (well, it is indeed, but possibly caused by:) or a bug in MSEdge; as it doesn't happen in Chrome or Firefox.

On Wednesday, May 29, 2019 at 10:27:23 AM UTC+2, Sanoob V wrote:
Hi All,

I am getting two scrollers in datagrid edge browser.

Two scroll.png


and when check inspect code i can see two GWT generated CSS if i remove that one scroll is hiding but I don't know from where it is coming 
please advice me.


css class.png




Hidind class.png







--
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, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/1ec0ecd4-e88e-43d6-933a-aa110c1c6b9b%40googlegroups.com.

Saturday, April 4, 2020

Re: When will development of GWT 3.0 /GWT 2.9 will start

Most of "GWT 3.0" is two distinct pieces - the build tooling, and the ecosystem/libraries. The build tooling starts with J2CL and Closure-Compiler, both produced by Google and shared via their github organization, and the community is building on this to produce a maven plugin which can run these as efficiently as possible (remembering of course that starting with "maven" means there's only so much you can do there). If you want to start with bazel, j2cl's hello world will get you started.

The second part is the ecosystem, the various libraries and frameworks that exist today that work in GWT2 that we know and love/hate. First, understand that both GWT2 and j2cl support the JsInterop spec, though there are a few small differences in how they deal with some of the particulars, mostly to do with how GWT2 is itself something of a build system, whereas J2cl is engineered to behave like javac, and live within a larger build system. So, many of the packages and classes found in gwt-user.jar have already been rewritten to use JsInterop instead of JSNI, and are in the process of being migrated to their own git repos at github.com/gwtproject/, and published to sonatype-snapshots, then maven central. Other ecosystem projects are either being updated or overhauled to be able to work outside of the world of GWT2 - here are too many examples to name briefly here.

Please note that almost all of these intend to be compatible with both GWT2 and J2CL at the same time, which blurs the line of "what is GWT3" - the goal is to make it as boring as possible to migrate from one to the other, as you aren't rewriting with an entirely new toolkit, just changing which compiler produces your highly optimized output. When you look at the migration headaches that are going to happen, our goal is to make almost all of them take place before adding J2CL to the mix, as com.google.gwt dependencies are removed and replaced with their org.gwtproject counterparts. The point here being, you can be "ready for j2cl" without moving to it, by adopting the updated versions of the classes that live in gwt-user.jar.

Similarly, GWT2 and J2CL share JRE emulation, with the exception of a few classes like Object, Class, Enum, Throwable.

Most of the GWT and J2CL discussions online today exists at https://gitter.im/gwtproject/gwt, https://gitter.im/vertispan/j2cl, or a few other rooms, or on stackoverflow.

-- 
  Colin Alworth
  colin@colinalworth.com



On Sat, Apr 4, 2020, at 12:33 PM, Käpt'n Körk wrote:
Hey there, as a GWT addict I am wondering, if GWT is finally dead? Any search for GWT 3.0 or similar results in ancient announcements of coming GWT versions - and that's it. Quite depressing, given that we are maintaining and further developing a couple of well designed GWT apps too conplex to re-implement in a recent technology. Any uplifting reply would be greatly appreciated.


--
You received this message because you are subscribed to a topic in the Google Groups "GWT Users" group.
To unsubscribe from this group and all its topics, send an email to google-web-toolkit+unsubscribe@googlegroups.com.

Re: When will development of GWT 3.0 /GWT 2.9 will start

Hey there, as a GWT addict I am wondering, if GWT is finally dead? Any search for GWT 3.0 or similar results in ancient announcements of coming GWT versions - and that's it. Quite depressing, given that we are maintaining and further developing a couple of well designed GWT apps too conplex to re-implement in a recent technology. Any uplifting reply would be greatly appreciated.

--
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, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/56e13072-b38c-4b6f-b253-f53ea32282c9%40googlegroups.com.