The UI seems to be a major feature of Kapua, so leaving the non-GPL version of it without an UI, feels awkward and I doubt that anyone in practice really considers this option.
Nonetheless, I accept that the rest of Kapua is standalone and working; thus it fullfils the requirements for a works-with dependency. Thanks for all the background infos and +1 from me - and good luck for finding alternative UI frameworks in the future :-)
Regards, Kai
The acronyms are a bit unfortunate, GWT is the Google library used to create _javascript_ sites from Java. GXT is a separate library that supplies UI elements and other features. GWT has been fully approved for both projects by Eclipse. GXT is the problem due
to the GPL license. Kura replaced GXT with gwtbootstrap3, but this will not be possible for Kapua.
While the Kapua team tries to find an alternative, they are requesting the same “workswith” dependency that Kura used prior to v2.0.0. Kapua will be completely functional without GXT, but will not have a UI. Having the workswith dependency will
allow users of Kapua to either:
1. Use a completely EPL friendly version with no UI
2. Use a version with the workswith dependency that has the UI and is distributed outside of the Eclipse channels
--Dave
Now I am bit confused ...
David said : "Both Kura and Kapua use GWT." ... So is there any need then for a GXT CQ then?
If we still do need GXT, is there any timeline then for a replacement of GXT?
_______________________________________________
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
_______________________________________________ iot-pmc mailing list iot-pmc@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/iot-pmc
|