On Thu, Jan 19, 2012 at 12:21 PM, Ian Mulvany <[email protected]> wrote:
... > From the perspective of Mendeley the main use case we are getting is > to support styles that users don't have access to. To be more specific on the use case, I take the "users don't have access to" phrase to mean: User needs a style for Journal X, but there is no such style available. They need such a style. Is that what we're talking about? The details are really important, because there are a couple of nuances here, each suggesting potentially different paths to an outcome. In user-oriented language: 1) "is there an existing style that looks like what I need, but is called something else?" A variation is "what style is closest to what I need, and how can I edit it to do what I need?" 2) "The journal style guide gives me these examples. How can I get a style that produces these results?" (which is really the crux of the matter for most users, it seems to me) I think it would help to get into this kind of detail on use cases, as it will help designers, and also make it easier to assess which approach is likely to work best. You might say Simon's proof-of-concept, for example, is designed for #2. Bruce ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ xbiblio-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xbiblio-devel
