Kiril Angov wrote: > > Think about flickr, amazon, etc where you get the image src as a URL > (using their APIs) so it makes sense for me for the sfThumbnailPlugin to > support that out of the box and not have the user do any other work in > order to handle those cases. I am using the URL as as source with > Amazon, for example, just to avoid comments like who will do that at all :) > > Best, > Kupo > > I believe it depends in the implementation scope of the plugin and its a classic tricky object oriented case where you need to decide what your class should do. So here are some of the cases that can be implemented
case1: Thumbnail Creation : sfThumbnail API access: sfThumbnal URL file loader: sfThumbnail case2: Thumbnail Creation : sfThumbnail API access: *sfApiAccess URL file loader: *sfThumbnail case3: Thumbnail Creation : sfThumbnail API access: *sfApiAccess URL file loader: *sfApiAccess case4: Thumbnail Creation : sfThumbnail API access: *sfApiAccess URL file loader: sfWebBrowser although the first case would be much easier in use, case4 is the most powerful in my opinion. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en -~----------~----~----~----~------~----~------~--~---
