Here’s another Flex annoyance – though I can see that from some users’ perspectives, this might be more of a feature than a bug.
The problem arose for me (as with most of my problems with Flex) in trying to apply a basically CSS/XHTML style workflow to a Flex application. I’m guessing most people who have done much fiddling about with CSS/XHTML design will have gotten used to creating graphics and texture files that are, say, maybe twice as large as they will generally need to be in order to accommodate different browsers and display resolutions: you can then size whatever component (probably a tab or a button) the graphic is for by percentage, confident that the background graphics file will be large enough for whatever platform the site visitor happens to be using. Other reasons for making an image larger than the area to be displayed might also include creating multiple states in a single file and then displaying them using positioning to save on bandwidth.
Unfortunately for this workflow, Flex has a peculiar behaviour when it comes to sizing and skins. Normally, it is possible to create a skin file larger than the component it skins – but only if the sizing is done in pixels (or rather, given that we’re talking about Flex, if the sizing is done without units). If the sizing is done using percentages, the component displays with the dimensions of the skin file instead.
I suppose a die-hard Flexhead would reply that one of the advantages of Flex and Flash is that you don’t have to worry as much about creating fluid layouts using these tools: you can set everything to be pixel-perfect, and the swf compiler does the magic for you. In addition, there’s no reason to be compiling excessively large graphics resources into the finished product. As with everything Flex, though, the (much appreciated!) close similarity to other web-technology workflows can lead to the assumption that they’re identical …
Filed under: Flex | Leave a Comment
Tags: Flex, Flex Bugs
Elaine Toms on Information Genre
Looking over Toms’ article – admittedly written in 2001, when things looked a lot different – I’m underwhelmed. Toms nicely demonstrates that people parse documents in terms both of form and content, and that form is processed more quickly than is content. Given the speed with which people parse webpages, this is important. But Toms’ idea of what constitutes ‘genre’ seems curiously old-fashioned: she seems to be thinking predominantly in terms of layout and typography. This utterly fails to take into account,
- the interactive nature of the web. Could it perhaps be argued that ‘genre’ on the web consists primarily of what a visitor can do on a site (in a button-pushing, strictly interactive sense), rather than what the site looks like? When I think of digital genres, I think not so much of “news sites” vs. “entertainment sites”, say, but in terms of wikis vs. e-commerce vs. blogs. The question of layout and typography might be more important in terms of alerting visitors to what is expected of them interactively rather than denoting what kind of information is found where on a page.
- the temporal nature of media generally. Toms appears to be thinking of the business letter of one or two pages as the archetypal document. But most documents are longer (or take more memory, to put it another way), and so are ‘navigated’ temporally as well as spatially: one doesn’t read a book or make a purchase on Amazon all on one page, and tools have to exist to guide and orient the user of either through the experience.
Filed under: Uncategorized | Leave a Comment
In a fascinating 2003 paper, David R. Danielson of Stanford University discusses web navigation in terms of ‘transitional volatility’ – that is to say, the extent to which pages change in both navigation display and content within a site.
In Danielson’s conceptual schema, visitors navigation and orientation is the result of three factors:
- Habituation to a particular navigational and layout schema through exposure to a particular ‘patch’ of a website (this seems to correspond well to the ‘hub and spoke’ navigation pattern identified by Andrew Cockburn and Bruce McKenzie).
- Prediction of the structure and nature of content based on this habituation when clicking on a link
- Reorientation based on the content actually rendered
- Full Overview (with, essentially, a site map constantly displayed on every page)
- Partial Overview (hyperlinks to five top-level pages and all pages within subsite of current node)
- Local Context (links to top-level pages and all siblings and children of current node)
- disoriented users tend to return to the Home page to start all over again, rather than using horizontal subsection links (as I would have anticipated)
- Local Context design was perceived as less volatile than Partial Overview design: local context navigation makes numerous small and incremental changes, as opposed to the occasional and sweeping character of partial overview models
- Navigational volatility increases the perceived size of a site, but not its complexity
- breadth-first exploration leads to a more accurate mental mapping of a site than approach in depth
- Unexpectedly, high navigational volatility in the local context model led to an increase in the perceived over-all coherence of a site. Danielson’s explanation of this is intriguing: extensive differences in navigational support between distal pages led users to discover connections for themselves (!)
- The page overview model did not cause users to underestimate actual page volatility through predictability. This may, however, have been the result of the extremely high level of predictability the overview model allows in many situations.
Filed under: Uncategorized | Leave a Comment
Recent Entries
- Kalbach, Chapter 2: The Take-Home message
- Affect and Navigation
- Andrew Dillon and Misha Vaughn on Information Shape
- Choo, Detlor, and Turnbull: a model for browsing behaviour
- Sizing using percentage in Flex applications
- Donna Maurer on Information Seeking
- Elaine Toms on Information Genre
- Information scent and information shape
- David R. Danielson on web navigation and orientation
- Navigation and Credibility
- Navigation, location, information
Categories
- Flex (2)
- Uncategorized (16)