From: Foster T. B. <fbr...@ad...> - 2006-10-18 00:38:19
|
Hi Eric, On Oct 17, 2006, at 5:00p, Eric Berdahl wrote: > [snip] > > Other scenarios are similarly easy to describe where the view may =20 > wish/need to display "as much useful information as can be inferred =20= > from the input" while also providing feedback that "the input =20 > cannot be accurately represented in this view". I think this makes a ton of sense. In all the cases I had considered, =20= there was no way the widget would be able to display something =20 reasonable with the invalid data. Your example of a graph-like widget =20= made a lot of sense, as well as the notion of extracting as much =20 worthwhile information as possible and putting it up for display. So, =20= in light of that, I'd propose add a view concept API to something like: void singleton(const model_type& value); We might also want to have a nullary singleton function for the case =20 when the widget is asked to display something it can't decipher. For =20 example, an edit text field being asked to display an icon: void singleton(); Thoughts? Blessings, Foster -- Foster T. Brereton <=E1=BC=B0=CF=87=CE=B8=CF=8D=CF=82>< = Romans =20 3:21-26 A d o b e S o f t w a r e T e c h n o l o g y L a b "What 99 percent of programmers need to know is not how to build =20 components but how to use them." -- Alexander Stepanov "Now we have very simple code and the meaning is perfectly clear. =20 Drink the Kool-Aid" -- Sean Parent |