Hi Mike,
Both Kura and Kapua use GWT. GXT is a graphics library that was previously used by Kura and is still used by Kapua. Kura recently (v2.0.0) removed the GXT library and went with gwtbootstrap3. This took considerable effort and has no where near
the flexibility of GXT. Kapua has a much more complex UI and removing GXT would be a major effort. I also don’t know that gwtbootstrap3 will be feature rich enough for Kapua. I believe that is why the effort to replace GXT in Kapua is still in ongoing.
Thanks,
--Dave
I was under the impression that Kura has recently moved from GXT to GWT.
Is that correct?
If so, does that show the path forward for Kapua?
On 10/7/2016 9:44 AM, Morson, Stefano wrote:
Hi,
I confirm the same approach used for Kura: A flag in the maven
config that will make the build fully consume GXT in a non-EPL-compatible fashion and that this flag is always kept turned off at Eclipse.
I agree with the idea to look for more license-friendly alternative. Unfortunately the replacement was not possible for the first contribution that's why we asked for a works-with dependency.
Since GXT is not going to change his licensing model, we'll not consider it a long term solution and we already started planning concretely for an alternative.
Hope this answers your doubts,
Stefano
Stefano just joined the mailing list. This e-mail is his anchor to the discussion, so that he can reply in the same thread.
_______________________________________________
iot-pmc
mailing list
iot-pmc@xxxxxxxxxxx
To
change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-pmc
|