[Adobe-source-devel] Re: asl-users: Request for Comments: ASL Picture Widget

[Tony V. E. <to...@ad...>]

Tony Van Eerd
Adobe Waterloo
-via Thunderbird-

Foster T. Brereton wrote:
> On Feb 14, 2006, at 04:22p, Tony Van Eerd wrote:
> 
>> I have a ProportionalFit<number_type> template that might help with  
>> the proportional resizing.  I can email it to you.
> 
> 
> Ah, this is interesting. Would it make a good addition to ASL as a  
> generic algorithm? GIL might have something like this in it already,  
> too, I'm not sure (sadly I haven't looked over the API as thoroughly  as 
> I ought).
> 

I think it, or some other generic prop-fit solution, should be in ASL - 
I wrote mine because I saw prop-fit code being rewritten (with bugs) 
over and over.  I've sent it to you in another email.  Do as you please.

>> I did a image view control once that also implemented the image  
>> interface - ie acxted like an image in that you could call CopyImage 
>> (view, image) (which takes 2 image * params) to put an image into  it, 
>> etc.  Interesting idea, anyhow.
> 
> 
> Interesting. Are you familiar with Lubomir and Hailin's work on GIL?  
> How would what you are describing compare to what it has to offer?
> 

Looking more closely at GIL is on my todo list, but it is a really long 
list.  Without a closer look, I would guess that what I was doing was 
more bassed on a abstract base class model of an image, and GIL is 
template based.

The interface class I was using has interesting things like 
BeginAccess(region) ... EndAccess() for accessing the pixels.  The 
EndAccess was particularly interesting because you could then chain 
actions to the end of the write (ie update the UI in the case of an 
image widget, or use this image as the middle layer of a 3 layer 
composite in a paint program, with the composite result image chained to 
an action that updated part of the UI, etc).


>> The import/export procs will eventually need to handle options.  Do  
>> you expect the import/export procs to bring up UI, or should you  pass 
>> in a dictionary_t of params to the export funcs, or something  like that?
> 
> 
> This is a good question. I'd expect the functions to be able to run  
> without user intervention (so scripting parameters should be able to  be 
> passed), but the possibility of popping a UI to detail further  command 
> parameters is not out of the question. I'll have to think a  bit more 
> about this one. Incidentally we have recently released a  modal dialog 
> interface API that accomplishes this very task pretty  handily, so 
> leveraging that might be good.
> 

'leveraging' but not depending on, right? :-)


>> Tony Van Eerd
>> Adobe Waterloo
>> -via Thunderbird-
>>
>> Foster T. Brereton wrote:
>>
>>> All,
>>> Ralph Thomas and I have begun designing a picture widget for ASL.   
>>> This widget will cover icons in a generic way as well. The in-  
>>> development design is posted at:
>>>     <http://opensource.adobe.com/twiki/bin/view/AdobeSource/ 
>>> PictureView>
>>> We would welcome any commentary, feedback, and/or refinement on  the  
>>> design or the documentation. If anyone would like to  contribute  
>>> please provide it either by email to the ASL mailing  list or on the  
>>> Wiki page directly. If you do not have write  access to the Wiki 
>>> page  yet please create a Wiki account; once  that is done email me 
>>> and I  will authorize you.
>>> Thanks in advance for any time you can give to the effort.
>>> 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
> 
> 
> -- 
> 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
> 
> 
>