I can host it during development - if everybody is ok with that.
I'd like to svn it and cowork on it with the crowd - but it can be kept discreet if required (so far it's just a bunch of concepts,
random experiments, and valuable links).
Contact me at argo.navis / yahoo or icq, check my profile.
Misunderstanding. I meant : the Flash standard "embed/object" combination for embedding swf is not web standards friendly.
As much as I hated it when it was "vector graphics only", I love Flash now that it is a full framework that even includes physics.
Flash "Satay" (ala invention) is a way to do the same with object tag only, that has a few drawbacks but is pretty ok
and suitable here.
SWFobject is the "slick javascript" approach, but you get to add two [ script /script ] tags each time you want a Flash movie.
More details about this project and more recent notes are in the multimedia forum (linked from my summary page, above, in case they sink at some point).
Satay I think, and if it is so I completely second your views
For an extensive discussion of these technical things,
I recommend you check the "Rockin' the walls" thread in the multimedia forum where they have been documented, but for the time
being, what I am hoping for is someone to tell me "officially" that it WILL happen once I am done with the swf container,
that the thing WILL go through a test phase as discussed.
In support processes, and change management, my self assigned Work Order is waiting for approval from long fingers
I personally like to use SWFObject it makes embedding flash very quick and easy, and although it uses embed tags (for Netscape architecture browsers only) it only creates these tags onLoad and this isn't reflected in the code so the page will validate.
At least it has solid browser and plugin detection, is stream-friendly and is accessible unlike Flash Satay.
Accessible? How is it more accesible than Satay? What happens when you want to include, say, 5 movies on the same page?
In my understanding, what happens is I have to put five pairs of script tags and the code in between.
From a truly accessible point of view, screen readers such as Jaws can have problems working with the externally loaded swf.
If you want 5 movies you have 2 choices, you _don't_ need 5 scripts tags, just a few more lines one for each div you plan to replace with your flash movie, represented by a new var. Then a line to write it to the document.
The other choice is to write your own script the will load in an array of Div id's to replace, this works best if each movie shares the same properties and perhaps flashvars, but it can all be customisable with the correct arguments sent through.
I've done this before on a couple of projects already.
Ok, my bad as far as static pages are concerned : but what happens when you have dynamic pages
generated using php? For example, for THIS case, a BB Flash tag - we'd have to have a unique id generated for each div,
avoid mixing up two divs when generating the container, and so on and so forth.
Items here don't really have a distinct id on the client side and it's easier - SWFObject is great for static pages, I agree,
but I have difficulties seeing this added here for core functionality like embedding outer SWF files.
What's your preferred method of embedding Flash reisio?
The markup part of what is often called flash satay.
quote:Blaise said:
it uses embed tags (for Netscape architecture browsers only) it only creates these tags onLoad and this isn't reflected in the code so the page will validate
It is reflected in the code, the w3.org validator just doesn't interpret JS. Just because the validator doesn't see it doesn't make it valid (standard).
Yes Reisio, I don't disagree, but it's a compromise I'm willing to accept for the ease and consistency.
Tyberius Prime
Maniac (V) Mad Scientist with Finglongers
From: Germany Insane since: Sep 2001
posted 01-16-2008 09:53
argo: I will implement a flash solution,
once I have another spare half day.
I will look at your work then, and if fits,
it will be integreated.
Please make sure that I can compile the 'flash-proxy-script'
with one of the open source flash compilers - I won't be buying
flash just for this (and I won't tolerate code that I can't modify).
Have you thought about using google code instead of Sourceforge? I was recently involved with a new OS project and we found Google code to be excellent, if it's a question of coverage, I don't believe that will be an issue.