Re: Color coded labels for editable fields
"Roger Binns" <[email protected]>
| Newsgroups | gmane.comp.mobile.bitpim.devel |
|---|---|
| Message-ID | <09ec01c62fb1$fdb0ff30$3501a8c0@rogersqyvr14d3> |
> How about also going with a few settings that would toggle the handling > of unsupported fields: I am generally against multiple modes of operation as it is just more ways for things to go wrong, more confusing for the user, more code paths and interactions. I keep thinking there must be a better way of doing this. What is the harm in BitPim accurately storing more information than the current phone can take? How does it actually affect someone when a subset is written to the phone? How can we alleviate that? Read this article: http://cooper.com/articles/art_goal_directed_design.htm Something that would be nice is working out how to get the display stuff out of the code. That would allow for easy translations, as well as text mode and command line operation. If we had that, then multiple modes of operation would be a lot less brittle and many different variations could be experimented with. Roger ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642