Language support

!!

I get the idea there are more people using Drupal + flash node / SWF Tools for more and more clever things, as the feature requests are getting a lot more interesting (= challenging!)

I've never used multi-language sites, so can you elaborate a bit what you mean, and in what respect flash node doesn't work with it!

The issues queues are getting very busy so I have to admit that things that require significant work will make on to my "To do" list, but I can't promise when they will get to the top!!

I am starting to think I need to write these requests down on a proper plan...

First of all: I'm just starting to use flashnode, flash, and drupal...
That being said, here's my comment:
The first use case for i18n flashnode would be to translate the alternate text to be displayed when flash is not available.
The second use case would be language-specific parameters (flashvars or other basic parameters).
How?
The easiest I think would be to allow the reuse of the same flash file for creating several flash nodes. Then each node could have its own language, alternate text, and parameters.
This is not possible at present because 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.
I don't know what's the rationale behind such constraints and what it would take to remove it?

The general model for i18n integration is that when the user clicks "create node" in a new language on a node's "Translate" tab, they are presented with a node editing(/creation) form that is already populated with all the details from the existing node. The idea is that they can then translate whatever needs translating, leave whatever doesn't, and hit "Save".

In most cases this has been assumed to include uploaded files (eg CCK File/Image Field), though this has not always been implemented smoothly and has caused some problems as the same system file reference is applied to both nodes, with the result that when the file is edited/deleted in one node it leaves a broken link in the remaining translations.

That said, even prepopulating with the basic/advanced flash node settings would be a boost.

For what it's worth, the translate tab literally links to the 'node/add/xxx' page with an extra query string of 'translation=[NID]&language=[LANG]'. You'd just have to node_load($_GET['translation']) and prepop the strings from there.

hi kingandy,
>You'd just have to node_load($_GET['translation']) and prepop the strings from there.
Is this comment destined to the flashnode module developer, or is it some php content hack?
My guess is the first, but being new here...

Definitely the flashnode developer :D

I've not looked into the code but I believe there's a stage during the node edit/create form building process where they will be adding the form elements for the flash movie. It should be easy enough to load the information from the original node at that stage. Whether that would allow you to share a file - and indeed whether it's wise to do so - is debatable, but grabbing the width/height/alt/etc should be straightforward...

Just understood how statuses affect the patch queue, so removing 'needs review' status because there's no patch attached here.
Hope this request still gets noticed ;)