On 9/22/08, Marcus Moeller <mm at gcug.de> wrote: > 2008/9/22 Alain Reguera Delgado <alain.reguera at gmail.com>: >> On 9/22/08, Alain Reguera Delgado <alain.reguera at gmail.com> wrote: >> >> Maybe we could do a local render and tag it ... then use the tagged >> version of that render to display images in Trac, and other web sites. >> If so, which part of the artwork we tag ? Would it be too much space >> to store ? > > Why don't you just display the latest from Trunk so that users are > informed about the current release state. Initially the environment was conceived to render artwork locally by selection ... there was no imminent need to version rendered images. They could be created at any time. Now, that we are planning to add rendered images in svn repo for Trac wiki (and maybe in other web sites) use ... someone will need to render the images and do upload them ... if we do it in trunk, each time the template change we'll need to update the imgs trunk too. Don't know if it is correct but personally I would like to have a place where the images do no change each time the template change. I know we don't have to upload the new rendered result if we don't want it to, but in that case the content of imgs trunk wouldn't be reflecting templates as they are. So in that point, and if we end up using the rendered images inside svn, is why I suggested to use some kind tag mechanism that let us keep a somehow static image for that use, something stable for a while, until the next modifications in trunk get ready to be referred to. Maybe it is time to define the life cycle of artwork rendering. Of course, that first tagged version is inexistent at this moment ... so maybe that's what we need to solve. > Otherwise import rendered images to Trunk on demand. Again trunk doesn't seems to me to be the place for something relative stable we should refer to... at this moment it doesn't change to much but in a future it may do. I would like to know your opinions, suggestions guys, Cheers, al.