Monday 07 May 2007 11:33:13 am
If I understand what Anthony is looking for, I may have some tips: 1) When (multiple) flash files are displayed or server by some more complex flash clips, then we can speak of a flash module/content scenario, in which a complex movie serves as a module (don't mistake it for eZ module) and then the rest of flash-digestible files (*.swf, *.flv or non-progressive *.jpg) make up the content. 2) A flash module serves multiple purposes so it might be a good idea to make it part of our template, which also means we will have to embed it for good in our design and upload the file manually (a more flexible managed solution would be possible, but it would be more difficult and complex, too). 3) Whenever we store files, images or media as content, eZ publish provides us with a way to learn the path to the file, no matter how deep it is stored. That means it would be possible to pass information to flash module regarding the exact location of all resources wanted (either with JavaScript, XML interface file, URL-like variable notation or whatever else). So I guess it's enough to teach our flash module template to pass the right parameters (based on -say- child flash-readable content objects) to the flash module and then implement desired logic within the flash module. 4) Remember, that both flash module and content should use consistent addressing method for the clips to be able to see each other. Usually 'path/to/flash_file.swf'|ezurl() does the trick for me. That way the flash content served by flash module is fully managed via eZ publish interface with no further file/template work :) Hope this helps.
--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu
|