Hi Martijn, > Yep, I was wondering why not create your own ShockWaveComponent that > exposes the parameters using some API, and renders them using a > repeating view?
yes, I think there's no other clean way. The problem with <object></object> is, that it allows nested/alternative content which the browsers show if the object's content-type isn't supported (e.g. an alternative image). Second, that different browsers need different attributes within <object> and as <param name...>. I thought I could just concentrate on the last aspect and apply only the needed changes... (i.e. move an attribute to a <param name...>). Best regards, --- Jan. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
