I agree with stefanski that it makes sense to put a lot of this into the model/behavior zone. I like to think of an imagefile as a piece of data, that I just happen to store in the filesystem rather than the database.
But as far as uploaders go, there are some limitations with PHP that will prevent us from ever having a truly mind-blowing uploader. Just look at Flickr, which certainly has it's fair share of PHP experts. For it's uploader application, they have turned to some pretty sophisticated compiled (I believe) server code, which connects to an executable file on your PC via an API. Their online uploader meanwhile remains pretty basic. I think Flickr's general strategy for image file management is fairly easy to replicate in CakePHP. I like how they produce 4 versions of every image you upload. I also like how they create randomized filenames as a way of protecting people from downloading large blocks of files outside of the interface. On Jun 6, 7:17 am, stefanski <[EMAIL PROTECTED]> wrote: > For a more general aproach regarding different requirements, I think > it makes more sense to split the tasks. For uploading i use > thishttp://labs.iamkoa.net/2007/10/23/image-upload-component-cakephp/ > which i modified to a behaviour because I see it more on the model- > side (happy to share code if wanted). And for Thumbnails I love > thehttp://bakery.cakephp.org/articles/view/image-resize-helperbecause it > offers great flexibilty with dynamic thumbnails and caching. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "CakePHP" 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/cake-php?hl=en -~----------~----~----~----~------~----~------~--~---
