You make good points. The Express package is in its infancy. I packaged things together that were, I felt, the most common combinations, such as all Views and Container classes have data binding. This also means Containers have scrolling with the idea that you would use Group if you did not want scrolling. But Group does not support background and border.
I agree that more options on the Express components could be presented as well as allowing scrolling to be removed for a specific Express container or all Express containers. ‹peter On 8/6/17, 4:36 PM, "Harbs" <harbs.li...@gmail.com> wrote: >I¹m looking at the Express components for the first time, and I have some >observations/questions. > >1. Container adds a ScrollingViewport bead. I was kind of expecting the >bead to be added via CSS so it could be overridden in an app. What is an >express app client supposed to do if they don¹t want scrolling? > >2. ScrollingViewport does not have a way to specify horizontal/vertical >scrolling. I¹m wondering if there shouldn¹t be a more do-it-all bead >which has options to turn on and off horizontal and vertical scrolling >separately. > >3. The Express components do not have convenience methods for setting >bead properties. It would seem to me that convenience methods would be >very helpful. > >4. I seems like there¹s lots of additional compound components which >would be useful. I¹m going to try and add someŠ > >Harbs
