On Friday 11 May 2007 23:31, Elvelind Grandin wrote: > Yes. I understand the problem. that's why I suggested doing the > resizing on the fly when the image is requested by the user. or am I > missing some key part of the app?
Well, let me try to explain again (sorry for my poor english :o/ ). Each page of an album will be displayed using a template. Each page can use a different template. The template mainly defines how many photos and text the page will contain, their size and position. To build the album, the user will first have to upload a set of photos, and for each page, choose the template, and assign text and photos (this part is far from being written). Then, once all informations are in the db (the model is already done, and quite good, I think), to display a page, I simply search the template to use for that page, retreive the photos and text the user has chosen, and display it. Or to be more precise, let the navigator display it! If positions can be ignored by the model (the navigator will do the job according to the CSS embedded in the template), the size of photos has to be known by the controler (at either editing time, to only resize them once, or at displaying time, with the mecanism you suggested), for the reasons we know. And except by parsing the template, I don't see how the controller can retreive the information... -- Frédéric http://www.gbiloba.org
pgpDhCriHGLD7.pgp
Description: PGP signature
