Web control center: generate or not properties with default values.

[Alexey Kuznetsov-2]

Igniters,

I'm working on Ignite Web Control Center (IGNITE-843
https://issues.apache.org/jira/browse/IGNITE-843).

One of its features is a XML / java code generation.
User select in UI different properties and get generated XML or java code
for cluster configuration.

So the question: should I generate property that user select in UI if user
select default value for that property?

For example. User select in combobox cache mode: PARTITIONED.
This is default mode for cache and could be omitted.
But somehow I feel that this will confuse users...

What do you think?

May be I should add an option on summary screen "Omit defaults"?

--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[Sergey Evdokimov]

Cache mode combobox may have default option "Default (PARTITIONED)". That
option should be selected by default and have gray color to differ from
other.
IMHO radio buttons are more appropriate to select cache mode, because user
can see all options at same time, without mouse click.

On Thu, Jul 30, 2015 at 6:21 PM, Alexey Kuznetsov <[hidden email]>
wrote:

> Igniters,
>
> I'm working on Ignite Web Control Center (IGNITE-843
> https://issues.apache.org/jira/browse/IGNITE-843).
>
> One of its features is a XML / java code generation.
> User select in UI different properties and get generated XML or java code
> for cluster configuration.
>
> So the question: should I generate property that user select in UI if user
> select default value for that property?
>
> For example. User select in combobox cache mode: PARTITIONED.
> This is default mode for cache and could be omitted.
> But somehow I feel that this will confuse users...
>
> What do you think?
>
> May be I should add an option on summary screen "Omit defaults"?
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

[dsetrakyan]

Alexey,

I think what you are really asking is whether the generated configuration
should have the default values (if user didn't select them). Right?

My intuition would be mostly No - we do not need to include all of the
default values into configuration, as you would have to include 100s of
redundant properties there. However, I think that for the main
configuration properties, e.g. cache-mode, atomicity, number of backups,
etc. you should still generate them even if the values are defaults.

Would be interesting to see what others think.

Also, do we have a test instance for the web-control-center running
somewhere? If so, it would be useful to provide a link here, so others
could play with it and provide feedback.

D.

On Thu, Jul 30, 2015 at 8:21 AM, Alexey Kuznetsov <[hidden email]>
wrote:

> Igniters,
>
> I'm working on Ignite Web Control Center (IGNITE-843
> https://issues.apache.org/jira/browse/IGNITE-843).
>
> One of its features is a XML / java code generation.
> User select in UI different properties and get generated XML or java code
> for cluster configuration.
>
> So the question: should I generate property that user select in UI if user
> select default value for that property?
>
> For example. User select in combobox cache mode: PARTITIONED.
> This is default mode for cache and could be omitted.
> But somehow I feel that this will confuse users...
>
> What do you think?
>
> May be I should add an option on summary screen "Omit defaults"?
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>

[Alexey Kuznetsov-2]

Dmitry,

Yes, exactly.

I'm not going to generate all 100500 properties. :)
I'm talking about some subset of "main" properties.


Sergey,

1) Radio buttons will occupy much more space than a combobox.
2) Making default value gray in combobox will looks ugly (IMHO).




On Thu, Jul 30, 2015 at 10:58 PM, Dmitriy Setrakyan <[hidden email]>
wrote:

> Alexey,
>
> I think what you are really asking is whether the generated configuration
> should have the default values (if user didn't select them). Right?
>
> My intuition would be mostly No - we do not need to include all of the
> default values into configuration, as you would have to include 100s of
> redundant properties there. However, I think that for the main
> configuration properties, e.g. cache-mode, atomicity, number of backups,
> etc. you should still generate them even if the values are defaults.
>
> Would be interesting to see what others think.
>
> Also, do we have a test instance for the web-control-center running
> somewhere? If so, it would be useful to provide a link here, so others
> could play with it and provide feedback.
>
> D.
>
> On Thu, Jul 30, 2015 at 8:21 AM, Alexey Kuznetsov <[hidden email]
> >
> wrote:
>
> > Igniters,
> >
> > I'm working on Ignite Web Control Center (IGNITE-843
> > https://issues.apache.org/jira/browse/IGNITE-843).
> >
> > One of its features is a XML / java code generation.
> > User select in UI different properties and get generated XML or java code
> > for cluster configuration.
> >
> > So the question: should I generate property that user select in UI if
> user
> > select default value for that property?
> >
> > For example. User select in combobox cache mode: PARTITIONED.
> > This is default mode for cache and could be omitted.
> > But somehow I feel that this will confuse users...
> >
> > What do you think?
> >
> > May be I should add an option on summary screen "Omit defaults"?
> >
> > --
> > Alexey Kuznetsov
> > GridGain Systems
> > www.gridgain.com
> >
>

--
Alexey Kuznetsov
GridGain Systems
www.gridgain.com

[Sergey Evdokimov]

Alexey,

2.) You understand me incorrectly, combobox will have 4 options: "Default
(PARTITIONED)" , "PARTITIONED", "REPLICATIED", "LOCAL". First option will
be gray, another option (include "PARTITIONED") of course should be black.

On Thu, Jul 30, 2015 at 7:26 PM, Alexey Kuznetsov <[hidden email]>
wrote:

> Dmitry,
>
> Yes, exactly.
>
> I'm not going to generate all 100500 properties. :)
> I'm talking about some subset of "main" properties.
>
>
> Sergey,
>
> 1) Radio buttons will occupy much more space than a combobox.
> 2) Making default value gray in combobox will looks ugly (IMHO).
>
>
>
>
> On Thu, Jul 30, 2015 at 10:58 PM, Dmitriy Setrakyan <[hidden email]
> >
> wrote:
>
> > Alexey,
> >
> > I think what you are really asking is whether the generated configuration
> > should have the default values (if user didn't select them). Right?
> >
> > My intuition would be mostly No - we do not need to include all of the
> > default values into configuration, as you would have to include 100s of
> > redundant properties there. However, I think that for the main
> > configuration properties, e.g. cache-mode, atomicity, number of backups,
> > etc. you should still generate them even if the values are defaults.
> >
> > Would be interesting to see what others think.
> >
> > Also, do we have a test instance for the web-control-center running
> > somewhere? If so, it would be useful to provide a link here, so others
> > could play with it and provide feedback.
> >
> > D.
> >
> > On Thu, Jul 30, 2015 at 8:21 AM, Alexey Kuznetsov <
> [hidden email]
> > >
> > wrote:
> >
> > > Igniters,
> > >
> > > I'm working on Ignite Web Control Center (IGNITE-843
> > > https://issues.apache.org/jira/browse/IGNITE-843).
> > >
> > > One of its features is a XML / java code generation.
> > > User select in UI different properties and get generated XML or java
> code
> > > for cluster configuration.
> > >
> > > So the question: should I generate property that user select in UI if
> > user
> > > select default value for that property?
> > >
> > > For example. User select in combobox cache mode: PARTITIONED.
> > > This is default mode for cache and could be omitted.
> > > But somehow I feel that this will confuse users...
> > >
> > > What do you think?
> > >
> > > May be I should add an option on summary screen "Omit defaults"?
> > >
> > > --
> > > Alexey Kuznetsov
> > > GridGain Systems
> > > www.gridgain.com
> > >
> >
>
>
>
> --
> Alexey Kuznetsov
> GridGain Systems
> www.gridgain.com
>