Hello,
I've proposed to work on a public API for binding.When that adds
capabilities for dynamic evaluation of the 'then' and 'otherwise'
arguments. Any comments?
https://bugs.openjdk.java.net/browse/JDK-8199560
- Nir
That will be a question for Gluon.
-- Kevin
Michael Paus wrote:
How will these changes then be synchronized with the work Gluon is
doing for the version
distributed by them? Do they work on the same repo?
Am 12.03.18 um 23:25 schrieb Kevin Rushforth:
Hi Florian,
By way of update, after
How will these changes then be synchronized with the work Gluon is doing
for the version
distributed by them? Do they work on the same repo?
Am 12.03.18 um 23:25 schrieb Kevin Rushforth:
Hi Florian,
By way of update, after thinking about this for a week (and getting
some offline feedback), I
Nir Lisker wrote:
As I understand it, you have added this as a possible refactoring
for BooleanConditionBuilder (but left the original in for
comparison), right?
Yes. I took Boolean as an example to demonstrate the approach.
Since this would constitute a public API change,
>
> As I understand it, you have added this as a possible refactoring for
> BooleanConditionBuilder (but left the original in for comparison), right?
Yes. I took Boolean as an example to demonstrate the approach.
Since this would constitute a public API change, I don't think it should be
> done
I took a quick look and had one comment:
public class BooleanConditionBuilder2 extends
ConditionBuilder { ... }
As I understand it, you have added this as a possible refactoring for
BooleanConditionBuilder (but left the original in for comparison),
right? Since
Hi,
Please review preliminary fix for:
https://bugs.openjdk.java.net/browse/JDK-8199514
http://cr.openjdk.java.net/~nlisker/8199514/webrev.00/
Thanks,
Nir
Nir Lisker wrote:
Solved the configuration issues, so I'm continuing with this.
I submitted https://bugs.openjdk.java.net/browse/JDK-8199514 for the
refactoring part.
As mentioned before, this seems OK long as the refactoring is
behavior-neutral and limited in scope.
As for
Solved the configuration issues, so I'm continuing with this.
I submitted https://bugs.openjdk.java.net/browse/JDK-8199514 for the
refactoring part.
As for https://bugs.openjdk.java.net/browse/JDK-8089579, should it be
closed as Not an Issue and a new issue created for the new API propasal, or
Thanks. We'll take a look. It's possible this is related to other bugs
with initial sizing that were introduced with HiDPI spuport (although
that wouldn't explain the continued failure at 175%).
-- Kevin
Chris Nahr wrote:
OK, I filed a bug report with internal review ID 9052971.
10 matches
Mail list logo