Hi Andrew,
"Client code" is basically anything in 2D, AWT, i18n, beans, a11y,
ImageIO, Sound, or Swing. I.e., anything related to GUI/desktop.
In this particular case Omair is changing the SplashScreen code which
belongs to AWT, hence the choice of the client repo for integration.
--
best r
On 21/02/2014 11:43, Anthony Petrov wrote:
Hi Andrew,
"Client code" is basically anything in 2D, AWT, i18n, beans, a11y,
ImageIO, Sound, or Swing. I.e., anything related to GUI/desktop.
In this particular case Omair is changing the SplashScreen code which
belongs to AWT, hence the choice of
Hello, Alexander.
The fix looks good.
With best regards. Petr.
On 10.02.2014, at 14:48, Sergey Bylokhov wrote:
> Hi, Alexander.
> The fix looks good.
>
> On 10.02.2014 14:35, Alexander Zvegintsev wrote:
>> Hi Sergey,
>>
>> thanks for the review, updated test is located here:
>> http://cr.ope
Added 2D
Victor
On 21.02.2014 16:00, Alan Bateman wrote:
On 21/02/2014 11:43, Anthony Petrov wrote:
Hi Andrew,
"Client code" is basically anything in 2D, AWT, i18n, beans, a11y,
ImageIO, Sound, or Swing. I.e., anything related to GUI/desktop.
In this particular case Omair is changing the S
Hi Alexandr,
On 2/18/14 7:33 AM, Alexander Scherbatiy wrote:
Hi Jim,
Let's divide the discussion into two part.
1. Where it is better to hold resolution variants?
Putting resolution variants in Image class brings some questions like:
- Some type of images do not need to have reso
