lkpoff.blogg.se

Microsoft webmatrix boilerplate
Microsoft webmatrix boilerplate









It relies on usability studies, which means that while some may find it annoying, most people like it better this way.Īs you have an easily discoverable designer option to make non-visual controls appear and disappear at will, I don't think there's much more we can do.Twitter came out with a Bootstrap toolkit "designed to kickstart development of webapps and sites. This kind of choice is not made whimsically. Having the non visual controls in the flow is really annoying. Personally, I would rather just see the non-visual controls down in the tray. My point was that rendering the non-visual controls inline in the page forces the page designer to be aware of and accomodate those issues. To make a control non-visual, just mark it with the attribute.īertrand: Yes, I realize that. Kevin: It doesn't matter where you put a data source on a page as long as you don't need it inside some container, so I'd put them at the end of the page so that they don't disturb the rest of the visual layout. Side question - how does one flag a control as non-visual in Whidbey? I do see your point about the data-source-in-a-template case, although it seems like there could be another solution. Where should they go? Does it matter where they live on a page? Where do you shove them so they don't interfere with your visual layout (especially in a flow layout, where they occupy space in the flow and change the layout of the page)? Fortunately, I see that Whidbey has an option to hide non-Visual controls - but of course then it's not obvious that they exist at all, and if you unhide them, it reflows your page. Putting them on the visual design surface strikes me as potentially confusing. Personally, I think that the notion of a separate area where non-visual elements are displayed (even if they actually 'live' as markup on the page) is a useful one. So, when are you getting a blog?īertrand: The way I see it, there's actually two separate issues here: 1) does the control persist as markup on the page, and 2) is the control displayed on the visual design surface, along with 'visual' controls. Thank you so much for this comment, Alister, I really appreciate.











Microsoft webmatrix boilerplate