Le 22/05/15 19:34, Stefan Seelmann a écrit :
On 05/21/2015 10:59 AM, Emmanuel Lécharny wrote:
Le 21/05/15 10:55, Emmanuel Lécharny a écrit :
Hi,
there are two class named BrowserWidget in ldapbrowser.common :
org.apache.directory.studio.ldapbrowser.common.widgets.BrowserWidget
Hi Stefan,
what's the best strategy for error reporting ? More specifically, whn
you expose a dialog box to get some user's input, we do check some of
the values. If one of them is invalid, we currently change the font to
red, but there is no place we say what's wrong, and that would be
On 05/22/2015 05:09 PM, Emmanuel Lécharny wrote:
Hi Stefan,
what's the best strategy for error reporting ? More specifically, whn
you expose a dialog box to get some user's input, we do check some of
the values. If one of them is invalid, we currently change the font to
red, but there is no
On Fri, May 22, 2015 at 11:09 PM, Emmanuel Lécharny elecha...@gmail.com
wrote:
Hi Stefan,
what's the best strategy for error reporting ? More specifically, whn
you expose a dialog box to get some user's input, we do check some of
the values. If one of them is invalid, we currently change the
On 05/21/2015 10:59 AM, Emmanuel Lécharny wrote:
Le 21/05/15 10:55, Emmanuel Lécharny a écrit :
Hi,
there are two class named BrowserWidget in ldapbrowser.common :
org.apache.directory.studio.ldapbrowser.common.widgets.BrowserWidget
