From: Ralph T. <ra...@gm...> - 2006-02-15 20:53:06
|
On 2/15/06, Sean Parent <sp...@ad...> wrote: > Specifying the image through the Eve interface to this should be with > a URL - consider that in the design for the factory. Ideally what kind of URLs would you want to support? Obviously "file://" and perhaps "resource://" (for getting data from MacOS bundle, or directly from the executable's resource section on Windows). Ralph > > > >> If it is a button - mostly the same comments as above except it > >> should be part of button_t. > > > > I never had any intention of making it behave as if it were a > > button. It isn't intended to latch out to a command in any way. > > > >> If it is an image view (this would be the most ambitious widget) - > >> then it should bind to an image view. The widget should support at > >> least pan and zoom (these controls wouldn't need to be bind-able - > >> but allow them to be bound would let you attach them to the basic > >> sheet to preserve view state). I can envision all kinds of nice > >> UI's for this (transparent overlay that comes up when you mouse > >> over...) - could be slick - we can attempt to work with a UI > >> designer to design the _last_ preview widget... > > > > This was the foundation upon which we began when coming up with the > > design of the picture widget. I have no qualms about starting > > simple and working our way up. The reason I began thinking about > > the picture widget implementation is because I need icon support -- > > if we started there and worked our way forward, I would think it > > would be a good way to do it. > > No disagreement here. > > > > > Blessings, > > Foster > > > > > > -- > > Foster T. Brereton <}}}>< Romans 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 > > components but how to use them." -- Alexander Stepanov > > > > |