Posted by crikos on April 29, 2008 at 12:57pm
Jump to:
| Project: | Flash Node |
| Version: | 6.x-3.1 |
| Component: | User interface |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
I would like to use the same Flash Application in different nodes. The Control for the Flash application is done through Flashvars. Now I have to maintain for each node different files. For example to embed "myflash.swf" in different nodes, I have to upload for each node an own swf File, named "myflash.swf_0","myflash.swf_1","myflash.swf_2", etc...
How can I manage this - maybe it is not a new feature Request.
Thanks and regards.
Comments
#1
The best way to do this is via a flash node macro. Macros were specifically written to let you re-use flash content on other pages, particularly with "player" type movies in mind. You can pass flash vars via the macro format, so you can have a "master" flash node with a generic player in it, and then call it up on other pages and use flash vars to refer to a video, audio or sub-movie.
Setting to fixed as I think macros will answer this query, but change back and post again if not.
#2
Automatically closed -- issue fixed for two weeks with no activity.
#3
I have a similar issue. I cannot use the flash node macro because I need to use php to in my flashvars code. The flashnode filter precludes using php.
What I would like to do is to create many flashnodes using the same .swf file. I wish to place each of these flashnodes in a gmap view (adding locative data) to each.
#4
If you want to refer to a flash node via PHP the best way is to call the
flashnode_content($args)function.$argsis an array where each key is a parameter as you'd use in the flash node filter. As a minimum you would write something likeprint flashnode_content(array('nid' => 10));To pass some flashvars you'd write something like
print flashnode_content(array('nid' => 10, 'flashvars' => 'var1=someValue'));The comments in
flashnode.moduledescribe the available keys.#5
Thanks, I will give it a whirl. It is a beautiful module.
#6
I'd like to add another rationale for such feature: i18n.
See my comment at #318221: Language support.
In a word, for the same file we can have several flashnode each having its own language, alternate text, and parameters.
#7
#8
At present flashnode implements and enforces a one-to-one relationship between file and flashnode. The flashnode creation screen does not allow the use of an existing file on the server, and the flash import screen does not list files for which a flashnode already exists.
So what's the rationale behind such constraints and what would it take to remove it?
How about having the flashnode creation screen include the possibility to select an already existing file on the server (maybe reusing parts of the import screen)?