You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "SuichII, Christopher" <Ch...@netapp.com> on 2013/07/31 17:26:38 UTC
UI Plugin Feature Discussion
I have a couple UI Plugin related features I'm close to wrapping up and I'd like to throw them out to take some feedback:
(I realize this is bad form to discuss the feature after implementation, so I apologize for that. However, everything here provides an optional feature for plugin developers and shouldn't pose any problem to the existing UI.)
UI Internationalization:
This would allow UI Plugins to contribute their own internationalized strings to the global js dictionary. Each plugin would define a dictionary.js and several dictionary_<locale>.js files. As each plugin is loaded, the appropriate plugin dictionary is loaded into the global js dictionary (with the global dictionary taking precedence in the event of a conflict).
Re-usable Zone Chart:
I have extended some functions in zoneChart.js to allow plugins to create charts by simply defining their own function which assembles the chart itself rather than having to define the chart in zoneChart.js
Dialog value field:
Currently, the identifying value of json objects is assumed to be 'id' or 'name' (if 'id' doesn't exist). I have added the option of allowing fields to specify which json property should be the identifying value of an object.
Default value functions:
Currently, the default value for a UI field must be a constant. I have extended the dialog forms to allow default value functions which are given the standard 'args' allowing default values to be determined at run time.
has_units field:
I have added a new dialog field type called 'has_units'. This field has an input box side by side with a select box. The select box is populated with predefined units (MB, GB, TB, for example) and uses (also predefined) conversion functions to allow automatic updating of the input box value when the units select box is changed.
Please let me know what the proper course of action is from here. Should I go ahead and submit diffs to reviewers or is there any discussion to be had before I do that?
Thanks,
Chris
Re: UI Plugin Feature Discussion
Posted by "SuichII, Christopher" <Ch...@netapp.com>.
require.js only requires the appropriate dictionary, depending on the locale, so…kind of =)
I have submitted one review request for each of these features on ReviewBoard. Let me know if anything isn't right (this is my first time using ReviewBoard).
Chris
On Jul 31, 2013, at 6:03 PM, Jessica Wang <Je...@citrix.com> wrote:
> Chris,
>
>> UI Internationalization:
>> This would allow UI Plugins to contribute their own internationalized strings to the global js dictionary. Each plugin would define a dictionary.js and several dictionary_<locale>.js files.
>
> So, the translation will be done on client-side?
>
>
>> Default value functions:
>> Currently, the default value for a UI field must be a constant. I have extended the dialog forms to allow default value functions which are given the standard 'args' allowing default values to be determined at run time.
>
> sounds good
>
>> has_units field:
>> I have added a new dialog field type called 'has_units'. This field has an input box side by side with a select box. The select box is populated with predefined units (MB, GB, TB, for example) and uses (also predefined) conversion functions to allow automatic updating of the input box value when the units select box is changed.
>
> Cool
>
>
> Jessica
>
> -----Original Message-----
> From: SuichII, Christopher [mailto:Chris.Suich@netapp.com]
> Sent: Wednesday, July 31, 2013 8:27 AM
> To: <de...@cloudstack.apache.org>
> Subject: UI Plugin Feature Discussion
>
> I have a couple UI Plugin related features I'm close to wrapping up and I'd like to throw them out to take some feedback:
>
> (I realize this is bad form to discuss the feature after implementation, so I apologize for that. However, everything here provides an optional feature for plugin developers and shouldn't pose any problem to the existing UI.)
>
> UI Internationalization:
> This would allow UI Plugins to contribute their own internationalized strings to the global js dictionary. Each plugin would define a dictionary.js and several dictionary_<locale>.js files. As each plugin is loaded, the appropriate plugin dictionary is loaded into the global js dictionary (with the global dictionary taking precedence in the event of a conflict).
>
> Re-usable Zone Chart:
> I have extended some functions in zoneChart.js to allow plugins to create charts by simply defining their own function which assembles the chart itself rather than having to define the chart in zoneChart.js
>
> Dialog value field:
> Currently, the identifying value of json objects is assumed to be 'id' or 'name' (if 'id' doesn't exist). I have added the option of allowing fields to specify which json property should be the identifying value of an object.
>
> Default value functions:
> Currently, the default value for a UI field must be a constant. I have extended the dialog forms to allow default value functions which are given the standard 'args' allowing default values to be determined at run time.
>
> has_units field:
> I have added a new dialog field type called 'has_units'. This field has an input box side by side with a select box. The select box is populated with predefined units (MB, GB, TB, for example) and uses (also predefined) conversion functions to allow automatic updating of the input box value when the units select box is changed.
>
> Please let me know what the proper course of action is from here. Should I go ahead and submit diffs to reviewers or is there any discussion to be had before I do that?
>
> Thanks,
> Chris
RE: UI Plugin Feature Discussion
Posted by Jessica Wang <Je...@citrix.com>.
Chris,
> UI Internationalization:
> This would allow UI Plugins to contribute their own internationalized strings to the global js dictionary. Each plugin would define a dictionary.js and several dictionary_<locale>.js files.
So, the translation will be done on client-side?
> Default value functions:
> Currently, the default value for a UI field must be a constant. I have extended the dialog forms to allow default value functions which are given the standard 'args' allowing default values to be determined at run time.
sounds good
> has_units field:
> I have added a new dialog field type called 'has_units'. This field has an input box side by side with a select box. The select box is populated with predefined units (MB, GB, TB, for example) and uses (also predefined) conversion functions to allow automatic updating of the input box value when the units select box is changed.
Cool
Jessica
-----Original Message-----
From: SuichII, Christopher [mailto:Chris.Suich@netapp.com]
Sent: Wednesday, July 31, 2013 8:27 AM
To: <de...@cloudstack.apache.org>
Subject: UI Plugin Feature Discussion
I have a couple UI Plugin related features I'm close to wrapping up and I'd like to throw them out to take some feedback:
(I realize this is bad form to discuss the feature after implementation, so I apologize for that. However, everything here provides an optional feature for plugin developers and shouldn't pose any problem to the existing UI.)
UI Internationalization:
This would allow UI Plugins to contribute their own internationalized strings to the global js dictionary. Each plugin would define a dictionary.js and several dictionary_<locale>.js files. As each plugin is loaded, the appropriate plugin dictionary is loaded into the global js dictionary (with the global dictionary taking precedence in the event of a conflict).
Re-usable Zone Chart:
I have extended some functions in zoneChart.js to allow plugins to create charts by simply defining their own function which assembles the chart itself rather than having to define the chart in zoneChart.js
Dialog value field:
Currently, the identifying value of json objects is assumed to be 'id' or 'name' (if 'id' doesn't exist). I have added the option of allowing fields to specify which json property should be the identifying value of an object.
Default value functions:
Currently, the default value for a UI field must be a constant. I have extended the dialog forms to allow default value functions which are given the standard 'args' allowing default values to be determined at run time.
has_units field:
I have added a new dialog field type called 'has_units'. This field has an input box side by side with a select box. The select box is populated with predefined units (MB, GB, TB, for example) and uses (also predefined) conversion functions to allow automatic updating of the input box value when the units select box is changed.
Please let me know what the proper course of action is from here. Should I go ahead and submit diffs to reviewers or is there any discussion to be had before I do that?
Thanks,
Chris
RE: UI Plugin Feature Discussion
Posted by Jessica Wang <Je...@citrix.com>.
> I would suggest you to submit multiple patches for each category because that way it will be easier to review and merge your changes.
+1
-----Original Message-----
From: Pranav Saxena [mailto:psbits@gmail.com]
Sent: Wednesday, July 31, 2013 10:30 AM
To: dev@cloudstack.apache.org; Brian Federle; Jessica Wang; Sonny Chhen
Subject: Re: UI Plugin Feature Discussion
Hey Chris ,
I think whatever proposals you have mentioned here make a lot of sense and
should help in a better user experience. I would suggest that you submit a
patch/multiple patches as per your convenience for the above mentioned
categories and then we can take it forward from there . I would suggest you
to submit multiple patches for each category because that way it will be
easier to review and merge your changes. A little explanation of the
functionality with each patch you submit would be much appreciated.
Copying Brian and Jessica to further help in facilitating this process
quickly . Thanks for your work.
On Wed, Jul 31, 2013 at 8:56 PM, SuichII, Christopher <
Chris.Suich@netapp.com> wrote:
> I have a couple UI Plugin related features I'm close to wrapping up and
> I'd like to throw them out to take some feedback:
>
> (I realize this is bad form to discuss the feature after implementation,
> so I apologize for that. However, everything here provides an optional
> feature for plugin developers and shouldn't pose any problem to the
> existing UI.)
>
> UI Internationalization:
> This would allow UI Plugins to contribute their own internationalized
> strings to the global js dictionary. Each plugin would define a
> dictionary.js and several dictionary_<locale>.js files. As each plugin is
> loaded, the appropriate plugin dictionary is loaded into the global js
> dictionary (with the global dictionary taking precedence in the event of a
> conflict).
>
> Re-usable Zone Chart:
> I have extended some functions in zoneChart.js to allow plugins to create
> charts by simply defining their own function which assembles the chart
> itself rather than having to define the chart in zoneChart.js
>
> Dialog value field:
> Currently, the identifying value of json objects is assumed to be 'id' or
> 'name' (if 'id' doesn't exist). I have added the option of allowing fields
> to specify which json property should be the identifying value of an object.
>
> Default value functions:
> Currently, the default value for a UI field must be a constant. I have
> extended the dialog forms to allow default value functions which are given
> the standard 'args' allowing default values to be determined at run time.
>
> has_units field:
> I have added a new dialog field type called 'has_units'. This field has an
> input box side by side with a select box. The select box is populated with
> predefined units (MB, GB, TB, for example) and uses (also predefined)
> conversion functions to allow automatic updating of the input box value
> when the units select box is changed.
>
> Please let me know what the proper course of action is from here. Should I
> go ahead and submit diffs to reviewers or is there any discussion to be had
> before I do that?
>
> Thanks,
> Chris
>
Re: UI Plugin Feature Discussion
Posted by Chip Childers <ch...@sungard.com>.
Never mind - Alex handled it.
On Wed, Jul 31, 2013 at 03:41:06PM -0400, Chip Childers wrote:
> Chris,
>
> It doesn't appear that that account exists. What email address does
> your account use?
>
> On Wed, Jul 31, 2013 at 11:57:18PM +0530, Pranav Saxena wrote:
> > Hi Chip ,
> >
> > Just a reminder in case you didn't happen to see this thread . Could you
> > please help out Chris here by granting him access to JIRA ?
> >
> > Thanks,
> > Pranav
> >
> >
> > On Wed, Jul 31, 2013 at 11:31 PM, SuichII, Christopher <
> > Chris.Suich@netapp.com> wrote:
> >
> > > I'll work on the patches and get them into ReviewBoard shortly. There is,
> > > however, a Jira issue open for the UI Plugin Internationalization. Could
> > > someone please grant me access to assign that issue to me. My Jira username
> > > is 'csuich2'.
> > >
> > > Thanks,
> > > Chris
> > >
> > > On Jul 31, 2013, at 1:30 PM, Pranav Saxena <ps...@gmail.com> wrote:
> > >
> > > > Hey Chris ,
> > > >
> > > > I think whatever proposals you have mentioned here make a lot of sense
> > > and
> > > > should help in a better user experience. I would suggest that you submit
> > > a
> > > > patch/multiple patches as per your convenience for the above mentioned
> > > > categories and then we can take it forward from there . I would suggest
> > > you
> > > > to submit multiple patches for each category because that way it will be
> > > > easier to review and merge your changes. A little explanation of the
> > > > functionality with each patch you submit would be much appreciated.
> > > >
> > > > Copying Brian and Jessica to further help in facilitating this process
> > > > quickly . Thanks for your work.
> > > >
> > > >
> > > > On Wed, Jul 31, 2013 at 8:56 PM, SuichII, Christopher <
> > > > Chris.Suich@netapp.com> wrote:
> > > >
> > > >> I have a couple UI Plugin related features I'm close to wrapping up and
> > > >> I'd like to throw them out to take some feedback:
> > > >>
> > > >> (I realize this is bad form to discuss the feature after implementation,
> > > >> so I apologize for that. However, everything here provides an optional
> > > >> feature for plugin developers and shouldn't pose any problem to the
> > > >> existing UI.)
> > > >>
> > > >> UI Internationalization:
> > > >> This would allow UI Plugins to contribute their own internationalized
> > > >> strings to the global js dictionary. Each plugin would define a
> > > >> dictionary.js and several dictionary_<locale>.js files. As each plugin
> > > is
> > > >> loaded, the appropriate plugin dictionary is loaded into the global js
> > > >> dictionary (with the global dictionary taking precedence in the event
> > > of a
> > > >> conflict).
> > > >>
> > > >> Re-usable Zone Chart:
> > > >> I have extended some functions in zoneChart.js to allow plugins to
> > > create
> > > >> charts by simply defining their own function which assembles the chart
> > > >> itself rather than having to define the chart in zoneChart.js
> > > >>
> > > >> Dialog value field:
> > > >> Currently, the identifying value of json objects is assumed to be 'id'
> > > or
> > > >> 'name' (if 'id' doesn't exist). I have added the option of allowing
> > > fields
> > > >> to specify which json property should be the identifying value of an
> > > object.
> > > >>
> > > >> Default value functions:
> > > >> Currently, the default value for a UI field must be a constant. I have
> > > >> extended the dialog forms to allow default value functions which are
> > > given
> > > >> the standard 'args' allowing default values to be determined at run
> > > time.
> > > >>
> > > >> has_units field:
> > > >> I have added a new dialog field type called 'has_units'. This field has
> > > an
> > > >> input box side by side with a select box. The select box is populated
> > > with
> > > >> predefined units (MB, GB, TB, for example) and uses (also predefined)
> > > >> conversion functions to allow automatic updating of the input box value
> > > >> when the units select box is changed.
> > > >>
> > > >> Please let me know what the proper course of action is from here.
> > > Should I
> > > >> go ahead and submit diffs to reviewers or is there any discussion to be
> > > had
> > > >> before I do that?
> > > >>
> > > >> Thanks,
> > > >> Chris
> > > >>
> > >
> > >
Re: UI Plugin Feature Discussion
Posted by Chip Childers <ch...@sungard.com>.
Chris,
It doesn't appear that that account exists. What email address does
your account use?
On Wed, Jul 31, 2013 at 11:57:18PM +0530, Pranav Saxena wrote:
> Hi Chip ,
>
> Just a reminder in case you didn't happen to see this thread . Could you
> please help out Chris here by granting him access to JIRA ?
>
> Thanks,
> Pranav
>
>
> On Wed, Jul 31, 2013 at 11:31 PM, SuichII, Christopher <
> Chris.Suich@netapp.com> wrote:
>
> > I'll work on the patches and get them into ReviewBoard shortly. There is,
> > however, a Jira issue open for the UI Plugin Internationalization. Could
> > someone please grant me access to assign that issue to me. My Jira username
> > is 'csuich2'.
> >
> > Thanks,
> > Chris
> >
> > On Jul 31, 2013, at 1:30 PM, Pranav Saxena <ps...@gmail.com> wrote:
> >
> > > Hey Chris ,
> > >
> > > I think whatever proposals you have mentioned here make a lot of sense
> > and
> > > should help in a better user experience. I would suggest that you submit
> > a
> > > patch/multiple patches as per your convenience for the above mentioned
> > > categories and then we can take it forward from there . I would suggest
> > you
> > > to submit multiple patches for each category because that way it will be
> > > easier to review and merge your changes. A little explanation of the
> > > functionality with each patch you submit would be much appreciated.
> > >
> > > Copying Brian and Jessica to further help in facilitating this process
> > > quickly . Thanks for your work.
> > >
> > >
> > > On Wed, Jul 31, 2013 at 8:56 PM, SuichII, Christopher <
> > > Chris.Suich@netapp.com> wrote:
> > >
> > >> I have a couple UI Plugin related features I'm close to wrapping up and
> > >> I'd like to throw them out to take some feedback:
> > >>
> > >> (I realize this is bad form to discuss the feature after implementation,
> > >> so I apologize for that. However, everything here provides an optional
> > >> feature for plugin developers and shouldn't pose any problem to the
> > >> existing UI.)
> > >>
> > >> UI Internationalization:
> > >> This would allow UI Plugins to contribute their own internationalized
> > >> strings to the global js dictionary. Each plugin would define a
> > >> dictionary.js and several dictionary_<locale>.js files. As each plugin
> > is
> > >> loaded, the appropriate plugin dictionary is loaded into the global js
> > >> dictionary (with the global dictionary taking precedence in the event
> > of a
> > >> conflict).
> > >>
> > >> Re-usable Zone Chart:
> > >> I have extended some functions in zoneChart.js to allow plugins to
> > create
> > >> charts by simply defining their own function which assembles the chart
> > >> itself rather than having to define the chart in zoneChart.js
> > >>
> > >> Dialog value field:
> > >> Currently, the identifying value of json objects is assumed to be 'id'
> > or
> > >> 'name' (if 'id' doesn't exist). I have added the option of allowing
> > fields
> > >> to specify which json property should be the identifying value of an
> > object.
> > >>
> > >> Default value functions:
> > >> Currently, the default value for a UI field must be a constant. I have
> > >> extended the dialog forms to allow default value functions which are
> > given
> > >> the standard 'args' allowing default values to be determined at run
> > time.
> > >>
> > >> has_units field:
> > >> I have added a new dialog field type called 'has_units'. This field has
> > an
> > >> input box side by side with a select box. The select box is populated
> > with
> > >> predefined units (MB, GB, TB, for example) and uses (also predefined)
> > >> conversion functions to allow automatic updating of the input box value
> > >> when the units select box is changed.
> > >>
> > >> Please let me know what the proper course of action is from here.
> > Should I
> > >> go ahead and submit diffs to reviewers or is there any discussion to be
> > had
> > >> before I do that?
> > >>
> > >> Thanks,
> > >> Chris
> > >>
> >
> >
RE: UI Plugin Feature Discussion
Posted by Alex Huang <Al...@citrix.com>.
Done.
--alex
> -----Original Message-----
> From: Pranav Saxena [mailto:psbits@gmail.com]
> Sent: Wednesday, July 31, 2013 11:27 AM
> To: dev@cloudstack.apache.org; chip.childers@sungard.com
> Cc: Brian Federle; Jessica Wang; Sonny Chhen
> Subject: Re: UI Plugin Feature Discussion
>
> Hi Chip ,
>
> Just a reminder in case you didn't happen to see this thread . Could you
> please help out Chris here by granting him access to JIRA ?
>
> Thanks,
> Pranav
>
>
> On Wed, Jul 31, 2013 at 11:31 PM, SuichII, Christopher <
> Chris.Suich@netapp.com> wrote:
>
> > I'll work on the patches and get them into ReviewBoard shortly. There
> > is, however, a Jira issue open for the UI Plugin Internationalization.
> > Could someone please grant me access to assign that issue to me. My
> > Jira username is 'csuich2'.
> >
> > Thanks,
> > Chris
> >
> > On Jul 31, 2013, at 1:30 PM, Pranav Saxena <ps...@gmail.com> wrote:
> >
> > > Hey Chris ,
> > >
> > > I think whatever proposals you have mentioned here make a lot of
> > > sense
> > and
> > > should help in a better user experience. I would suggest that you
> > > submit
> > a
> > > patch/multiple patches as per your convenience for the above
> > > mentioned categories and then we can take it forward from there . I
> > > would suggest
> > you
> > > to submit multiple patches for each category because that way it
> > > will be easier to review and merge your changes. A little
> > > explanation of the functionality with each patch you submit would be
> much appreciated.
> > >
> > > Copying Brian and Jessica to further help in facilitating this
> > > process quickly . Thanks for your work.
> > >
> > >
> > > On Wed, Jul 31, 2013 at 8:56 PM, SuichII, Christopher <
> > > Chris.Suich@netapp.com> wrote:
> > >
> > >> I have a couple UI Plugin related features I'm close to wrapping up
> > >> and I'd like to throw them out to take some feedback:
> > >>
> > >> (I realize this is bad form to discuss the feature after
> > >> implementation, so I apologize for that. However, everything here
> > >> provides an optional feature for plugin developers and shouldn't
> > >> pose any problem to the existing UI.)
> > >>
> > >> UI Internationalization:
> > >> This would allow UI Plugins to contribute their own
> > >> internationalized strings to the global js dictionary. Each plugin
> > >> would define a dictionary.js and several dictionary_<locale>.js
> > >> files. As each plugin
> > is
> > >> loaded, the appropriate plugin dictionary is loaded into the global
> > >> js dictionary (with the global dictionary taking precedence in the
> > >> event
> > of a
> > >> conflict).
> > >>
> > >> Re-usable Zone Chart:
> > >> I have extended some functions in zoneChart.js to allow plugins to
> > create
> > >> charts by simply defining their own function which assembles the
> > >> chart itself rather than having to define the chart in zoneChart.js
> > >>
> > >> Dialog value field:
> > >> Currently, the identifying value of json objects is assumed to be 'id'
> > or
> > >> 'name' (if 'id' doesn't exist). I have added the option of allowing
> > fields
> > >> to specify which json property should be the identifying value of
> > >> an
> > object.
> > >>
> > >> Default value functions:
> > >> Currently, the default value for a UI field must be a constant. I
> > >> have extended the dialog forms to allow default value functions
> > >> which are
> > given
> > >> the standard 'args' allowing default values to be determined at run
> > time.
> > >>
> > >> has_units field:
> > >> I have added a new dialog field type called 'has_units'. This field
> > >> has
> > an
> > >> input box side by side with a select box. The select box is
> > >> populated
> > with
> > >> predefined units (MB, GB, TB, for example) and uses (also
> > >> predefined) conversion functions to allow automatic updating of the
> > >> input box value when the units select box is changed.
> > >>
> > >> Please let me know what the proper course of action is from here.
> > Should I
> > >> go ahead and submit diffs to reviewers or is there any discussion
> > >> to be
> > had
> > >> before I do that?
> > >>
> > >> Thanks,
> > >> Chris
> > >>
> >
> >
Re: UI Plugin Feature Discussion
Posted by Pranav Saxena <ps...@gmail.com>.
Hi Chip ,
Just a reminder in case you didn't happen to see this thread . Could you
please help out Chris here by granting him access to JIRA ?
Thanks,
Pranav
On Wed, Jul 31, 2013 at 11:31 PM, SuichII, Christopher <
Chris.Suich@netapp.com> wrote:
> I'll work on the patches and get them into ReviewBoard shortly. There is,
> however, a Jira issue open for the UI Plugin Internationalization. Could
> someone please grant me access to assign that issue to me. My Jira username
> is 'csuich2'.
>
> Thanks,
> Chris
>
> On Jul 31, 2013, at 1:30 PM, Pranav Saxena <ps...@gmail.com> wrote:
>
> > Hey Chris ,
> >
> > I think whatever proposals you have mentioned here make a lot of sense
> and
> > should help in a better user experience. I would suggest that you submit
> a
> > patch/multiple patches as per your convenience for the above mentioned
> > categories and then we can take it forward from there . I would suggest
> you
> > to submit multiple patches for each category because that way it will be
> > easier to review and merge your changes. A little explanation of the
> > functionality with each patch you submit would be much appreciated.
> >
> > Copying Brian and Jessica to further help in facilitating this process
> > quickly . Thanks for your work.
> >
> >
> > On Wed, Jul 31, 2013 at 8:56 PM, SuichII, Christopher <
> > Chris.Suich@netapp.com> wrote:
> >
> >> I have a couple UI Plugin related features I'm close to wrapping up and
> >> I'd like to throw them out to take some feedback:
> >>
> >> (I realize this is bad form to discuss the feature after implementation,
> >> so I apologize for that. However, everything here provides an optional
> >> feature for plugin developers and shouldn't pose any problem to the
> >> existing UI.)
> >>
> >> UI Internationalization:
> >> This would allow UI Plugins to contribute their own internationalized
> >> strings to the global js dictionary. Each plugin would define a
> >> dictionary.js and several dictionary_<locale>.js files. As each plugin
> is
> >> loaded, the appropriate plugin dictionary is loaded into the global js
> >> dictionary (with the global dictionary taking precedence in the event
> of a
> >> conflict).
> >>
> >> Re-usable Zone Chart:
> >> I have extended some functions in zoneChart.js to allow plugins to
> create
> >> charts by simply defining their own function which assembles the chart
> >> itself rather than having to define the chart in zoneChart.js
> >>
> >> Dialog value field:
> >> Currently, the identifying value of json objects is assumed to be 'id'
> or
> >> 'name' (if 'id' doesn't exist). I have added the option of allowing
> fields
> >> to specify which json property should be the identifying value of an
> object.
> >>
> >> Default value functions:
> >> Currently, the default value for a UI field must be a constant. I have
> >> extended the dialog forms to allow default value functions which are
> given
> >> the standard 'args' allowing default values to be determined at run
> time.
> >>
> >> has_units field:
> >> I have added a new dialog field type called 'has_units'. This field has
> an
> >> input box side by side with a select box. The select box is populated
> with
> >> predefined units (MB, GB, TB, for example) and uses (also predefined)
> >> conversion functions to allow automatic updating of the input box value
> >> when the units select box is changed.
> >>
> >> Please let me know what the proper course of action is from here.
> Should I
> >> go ahead and submit diffs to reviewers or is there any discussion to be
> had
> >> before I do that?
> >>
> >> Thanks,
> >> Chris
> >>
>
>
Re: UI Plugin Feature Discussion
Posted by "SuichII, Christopher" <Ch...@netapp.com>.
I'll work on the patches and get them into ReviewBoard shortly. There is, however, a Jira issue open for the UI Plugin Internationalization. Could someone please grant me access to assign that issue to me. My Jira username is 'csuich2'.
Thanks,
Chris
On Jul 31, 2013, at 1:30 PM, Pranav Saxena <ps...@gmail.com> wrote:
> Hey Chris ,
>
> I think whatever proposals you have mentioned here make a lot of sense and
> should help in a better user experience. I would suggest that you submit a
> patch/multiple patches as per your convenience for the above mentioned
> categories and then we can take it forward from there . I would suggest you
> to submit multiple patches for each category because that way it will be
> easier to review and merge your changes. A little explanation of the
> functionality with each patch you submit would be much appreciated.
>
> Copying Brian and Jessica to further help in facilitating this process
> quickly . Thanks for your work.
>
>
> On Wed, Jul 31, 2013 at 8:56 PM, SuichII, Christopher <
> Chris.Suich@netapp.com> wrote:
>
>> I have a couple UI Plugin related features I'm close to wrapping up and
>> I'd like to throw them out to take some feedback:
>>
>> (I realize this is bad form to discuss the feature after implementation,
>> so I apologize for that. However, everything here provides an optional
>> feature for plugin developers and shouldn't pose any problem to the
>> existing UI.)
>>
>> UI Internationalization:
>> This would allow UI Plugins to contribute their own internationalized
>> strings to the global js dictionary. Each plugin would define a
>> dictionary.js and several dictionary_<locale>.js files. As each plugin is
>> loaded, the appropriate plugin dictionary is loaded into the global js
>> dictionary (with the global dictionary taking precedence in the event of a
>> conflict).
>>
>> Re-usable Zone Chart:
>> I have extended some functions in zoneChart.js to allow plugins to create
>> charts by simply defining their own function which assembles the chart
>> itself rather than having to define the chart in zoneChart.js
>>
>> Dialog value field:
>> Currently, the identifying value of json objects is assumed to be 'id' or
>> 'name' (if 'id' doesn't exist). I have added the option of allowing fields
>> to specify which json property should be the identifying value of an object.
>>
>> Default value functions:
>> Currently, the default value for a UI field must be a constant. I have
>> extended the dialog forms to allow default value functions which are given
>> the standard 'args' allowing default values to be determined at run time.
>>
>> has_units field:
>> I have added a new dialog field type called 'has_units'. This field has an
>> input box side by side with a select box. The select box is populated with
>> predefined units (MB, GB, TB, for example) and uses (also predefined)
>> conversion functions to allow automatic updating of the input box value
>> when the units select box is changed.
>>
>> Please let me know what the proper course of action is from here. Should I
>> go ahead and submit diffs to reviewers or is there any discussion to be had
>> before I do that?
>>
>> Thanks,
>> Chris
>>
Re: UI Plugin Feature Discussion
Posted by Pranav Saxena <ps...@gmail.com>.
Hey Chris ,
I think whatever proposals you have mentioned here make a lot of sense and
should help in a better user experience. I would suggest that you submit a
patch/multiple patches as per your convenience for the above mentioned
categories and then we can take it forward from there . I would suggest you
to submit multiple patches for each category because that way it will be
easier to review and merge your changes. A little explanation of the
functionality with each patch you submit would be much appreciated.
Copying Brian and Jessica to further help in facilitating this process
quickly . Thanks for your work.
On Wed, Jul 31, 2013 at 8:56 PM, SuichII, Christopher <
Chris.Suich@netapp.com> wrote:
> I have a couple UI Plugin related features I'm close to wrapping up and
> I'd like to throw them out to take some feedback:
>
> (I realize this is bad form to discuss the feature after implementation,
> so I apologize for that. However, everything here provides an optional
> feature for plugin developers and shouldn't pose any problem to the
> existing UI.)
>
> UI Internationalization:
> This would allow UI Plugins to contribute their own internationalized
> strings to the global js dictionary. Each plugin would define a
> dictionary.js and several dictionary_<locale>.js files. As each plugin is
> loaded, the appropriate plugin dictionary is loaded into the global js
> dictionary (with the global dictionary taking precedence in the event of a
> conflict).
>
> Re-usable Zone Chart:
> I have extended some functions in zoneChart.js to allow plugins to create
> charts by simply defining their own function which assembles the chart
> itself rather than having to define the chart in zoneChart.js
>
> Dialog value field:
> Currently, the identifying value of json objects is assumed to be 'id' or
> 'name' (if 'id' doesn't exist). I have added the option of allowing fields
> to specify which json property should be the identifying value of an object.
>
> Default value functions:
> Currently, the default value for a UI field must be a constant. I have
> extended the dialog forms to allow default value functions which are given
> the standard 'args' allowing default values to be determined at run time.
>
> has_units field:
> I have added a new dialog field type called 'has_units'. This field has an
> input box side by side with a select box. The select box is populated with
> predefined units (MB, GB, TB, for example) and uses (also predefined)
> conversion functions to allow automatic updating of the input box value
> when the units select box is changed.
>
> Please let me know what the proper course of action is from here. Should I
> go ahead and submit diffs to reviewers or is there any discussion to be had
> before I do that?
>
> Thanks,
> Chris
>