By the way, when I said, "I fixed the "No Thanks" radio-button issue in both 4.4 and master," I meant I fixed the issue where the custom compute and/or custom storage QoS controls were not disappearing when you clicked on the "No Thanks" radio button.
On Sat, Mar 22, 2014 at 7:45 PM, Mike Tutkowski < mike.tutkow...@solidfire.com> wrote: > FYI that I fixed the "No Thanks" radio-button issue in both 4.4 and master. > > > On Sat, Mar 22, 2014 at 5:38 PM, Mike Tutkowski < > mike.tutkow...@solidfire.com> wrote: > >> I actually think it has to do with the CSS. >> >> It looks like the "No Thanks" radio button's height is not taken into >> consideration when we shrink the height of the Disk Offering container to >> fit in the custom compute and custom storage QoS controls. >> >> I also noticed that if you select a custom Disk Offering and - as >> expected - it displays custom controls at the bottom and then you click on >> the "No Thanks" radio button that the custom fields don't disappear. >> >> >> On Sat, Mar 22, 2014 at 5:27 PM, Mike Tutkowski < >> mike.tutkow...@solidfire.com> wrote: >> >>> Hi, >>> >>> I have a JavaScript question. Of course, feel free anyone to answer it, >>> but I CCed Brian, Jessica, and Alena since they seem to do a lot of our GUI >>> work. >>> >>> While testing a feature of mine for 4.4, I came across a minor GUI issue. >>> >>> For 4.4 I added the ability for Compute Offerings to support Storage >>> Quality of Service (Qos). >>> >>> From a visual perspective, this partly entailed adding Min IOPS and Max >>> IOPS as options when a user selects a Compute or Disk Offering in the >>> process of creating a VM. >>> >>> Here is how this looks for a Compute Offering: >>> >>> http://i.imgur.com/2HNZ6Ta.png >>> >>> For Compute Offerings, this works great as you can scroll the list of >>> Compute Offerings and - for the selected Compute Offering, if applicable - >>> you can scroll its custom compute options (Number of CPU cores, MHz, and >>> memory) and its storage QoS options. If storage QoS is not enabled on the >>> Compute Offering (or if its values are configured by the admin on the >>> Compute Offering), you won't see these options here (just like if custom >>> compute options like number of CPU cores isn't enabled for users to >>> configure on the Compute Offering, you won't see those options here either). >>> >>> The moral of the story here is that this scrolling works great. >>> >>> I noticed a minor GUI issue, however, with the equivalent functionality >>> on Disk Offerings: >>> >>> http://i.imgur.com/HJsAhdU.png >>> >>> As you can see here, the scrolling doesn't work. >>> >>> I was hoping a GUI person could take a look at this for me. Nothing >>> obvious stuck out when I looked at index.jsp and I don't have nearly the >>> JavaScript experience as I have Java experience. >>> >>> Thanks! >>> Mike >>> >>> -- >>> *Mike Tutkowski* >>> *Senior CloudStack Developer, SolidFire Inc.* >>> e: mike.tutkow...@solidfire.com >>> o: 303.746.7302 >>> Advancing the way the world uses the >>> cloud<http://solidfire.com/solution/overview/?video=play> >>> *(tm)* >>> >> >> >> >> -- >> *Mike Tutkowski* >> *Senior CloudStack Developer, SolidFire Inc.* >> e: mike.tutkow...@solidfire.com >> o: 303.746.7302 >> Advancing the way the world uses the >> cloud<http://solidfire.com/solution/overview/?video=play> >> *(tm)* >> > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: mike.tutkow...@solidfire.com > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *(tm)* > -- *Mike Tutkowski* *Senior CloudStack Developer, SolidFire Inc.* e: mike.tutkow...@solidfire.com o: 303.746.7302 Advancing the way the world uses the cloud<http://solidfire.com/solution/overview/?video=play> *(tm)*
