Guys,
I totally dropped the ball on setting up a meeting on March 23rd, my
apologies.
We should meet on March 30 (this Friday)
To discuss actual quality status of your functionality area and decide
which 3 bugs can be marked with BLOCKER tag (if any) and which blocker bugs
can be waived for
Hi Luca,
I've fixed it :)
On March 25, 2018 11:47:39 AM GMT+02:00, Luca Mambretti
wrote:
>Hi,
>
>tried that again today and it works, weird since before posting I got
>the same problem on a different system where I hadn't touched Synergy
>before, will be filling a new
Well there is better beans binding LGPL license so relatively safe, it's
actually a fork of the original JSR with a couple of improvements and fixes
https://www.openhub.net/p/BetterBeansBinding
also available on maven central
One obvious solution should be to create your own library wrapper module
for "beansbinding-1.2.1.jar" (download, or take it from an 8.2
installation) - works for me. The non-obvious question is the licence. I
couldn't find it anywhere. Does anybody know about the licensing provisions
for this jar?
Really a shame, I'd have to revert to old style binding in the few swing forms
I still use.
Maybe something to prompt the user to download the missing bits similar to what
was done when another swing component I do not remember now was removed??
Also for platform applications how is binding