"in particular lots of reuseable code in the form of includes, functions and tags, and a general attempt to separate logic from display as much as possible" Absolutely agree. As for the presentation and layout, I believe CSS is extremely useful and the application framework is very convenient for any re-touching of the interface as well.
>While the house on the sand analogy is appropriate, I think it's also >good to remember that if you're in the business of selling houses, >even the best lot will be difficult to sell if the house built on it >is generally considered to be ugly. > >I know that the Fusebox Lifecycle Process (FLiP), which I've not used >to date, insists on all of the UI being well established as part of >the wireframe before any code is written. I'm neither married to nor >entirely opposed to this idea. I know others like it a lot because >theoretically it means never having to completely recode a redesigned >UI or being stuck with a poor UI because the client doesn't want to >pay to rewrite the code. > >When I do my own work I tend to do them both simultaneously, but I >also take a long time to formulate my thoughts about both the logic >and the interface. Once I've envisioned an interface that seems >reasonably intuitive and works well with good solid logic on the back >end, then I start writing actual code. I also don't perceive large >amounts of time lost in redesigning interfaces, although this may have >a lot to do with my coding habbits (in particular lots of reuseable >code in the form of includes, functions and tags, and a general >attempt to separate logic from display as much as possible). > >hth > >Isaac > >Original Message ----------------------- >Hi, > >The subject matter is new to me and I'll make it short >and "sweet?". So, I'll just throw out something raw, >and pls help me to chew it. >Major premise: I think it's more about Interface >Usability Assessment, rather than functionality >assessment. > >The way to tackle it is first to decompose all the >components of the Interface, then each screen under >each component. Question, would compoment A weigh more >than component B? Would screen A weigh more than >screen B? Yes? depending on each's contribution to >system/application functionality? Consult with the >client as well? What's the usual practice here? > >Secondly, what's the value of Interface Assessment if >it is done without correlation to Functionality >Assessment? A nice-looking house built on sand won't >stand. > >Thanks. > > >Li, Chunshen (Don) >http://68.32.61.40/datadata/DataMan.cfm > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
