You tell him, Philip :) I wish you all the best for 2010. - and for the guy who keeps on showing doesnt understand anything about SWFObject and it's features that free creativity for a lot of developers... I know something that could be a something to try and do oncoming year: .. Read a Fine Manual or two of and to unsubscribe from this group, send email to [email protected]<swfobject%[email protected]> .
peace, Xander On Mon, Dec 28, 2009 at 7:53 PM, Philip Hutchison <[email protected]>wrote: > So it seems to me that if you are going to support a different approach you >> should also cover the general features of the products that use the code >> that you are trying to make more compliant. >> > > We are not part of Adobe, and are volunteers doing this completely free as > a community service. You can't seriously expect us to find every product > that outputs SWF files and add support for their proprietary skinning and > flashvar usage. That's daft. It's up to the creators/vendors of those > products to adapt their publishing system to fit their needs. They're free > to use SWFObject to that end, if they wish. Adobe has begun adapting > SWFObject as its default publishing technique in its newer products, but > Adobe does not own SWFObject and we are not affiliated with Adobe in any > way. > > >> A huge feature of the adobe flash detection kit is that it immediately >> adds functionality for the skins - no questions asked. > > > This statement tells me that you need to learn more about this project > before making pronouncements about our faults. It's clear you don't > understand what's going on here. > > >> And if you are trying to replace something that is known to work I would >> think you would create something that has the same functionality only >> better. >> > > As Kyle said, what SWFObject does is make embedding SWFs as easy as > possible using code that validates against the W3C specs. Something that > Adobe's old kit didn't do. Something that <embed> doesn't do. We also try > to ensure that developers are given as much flexibility as possible when > embedding their SWFs, hence the dynamic and static publishing approaches, > and the SWFObject API. SWFObject improves upon the old Flash Detection Kit > in many ways, and is much more powerful. Otherwise, why would Adobe be > switching to SWFObject? > > You should really learn more about a product before you start telling its > developers how bad it is. That's bad form and completely uncalled for. > > Also, this SWFObject Google Group is for people seeking help. Multiple > people have offered advice to you and you seem to completely disregard them > in favor of making ignorant complaints. If you're not really looking for > help and don't have anything constructive to add to our discussions, please > stop posting. > > Thank you > - philip > > > On Mon, Dec 28, 2009 at 12:01 AM, X.Smalbil <[email protected]>wrote: > >> Hi, >> >> My remark would be to read more on the website en use the code generator >> to embed the flash files. Further more there is no support for the things >> you are asking. And please let me argue the FACT that >> you should READ more. >> >> >> - "The really stupid thing is that the embed tag has not become a part of >> the html standard. It worked for years, it was flawless." >> >> The embed TAG works in HTML 4.01 and you can use it when you are using >> XHTML. It is also possible to validate. >> If you would READ the HTML 5 reference on W3C then you could find that the >> embed tag has not gone away. http://www.w3schools.com/html5/tag_embed.asp >> >> >> - "But the fact is, this component was created to make the adobe html code >> compliant and a big part of that issue is that people use the skins in both >> flash and dreamweaver to quickly add play controls to their flv files." >> The adobe detecton kit is just to detect what flash version you have got >> and display content. >> >> - ClientSideDetection.html >> Contains the JavaScript and VBScript logic for client-side Flash >> Player detection >> - AC_OETags.js >> JavaScript source file; used by ClientSideDetection.html to detect and >> embed the Flash Player >> - example.swf >> Flash movie to test your implementation of the Express Install process >> >> ActionScript-based Detection sample files >> >> These files are used to detect the end user's Flash Player version, and to >> display Flash content if the correct version was detected or to prompt the >> user to install the correct version of the Flash Player. >> >> - "Without the skins you have to include it in your swf and it is bulky, >> plus it has to reload each time you flip to another movie." >> >> This is totally not true. When you embed, you will have to save the >> controls sfw as a seperate file which you upload. The reloading is not a >> problem.. it goes more quickly >> than loading another movie... btw evertime you flip top another movie.. it >> will reload another movie. :p >> >> >> - "it seems to me that if you are going to support a different approach >> you should also cover the general features of the products that use the code >> that you are trying to make more compliant" >> >> Nope, and there isn't minimal support for other software as well. >> >> -"And if you are trying to replace something that is known to work I would >> think you would create something that has the same functionality only >> better." >> >> Ignorance is bliss. >> >> >> >> Well Best Wishes for 2010, >> >> >> Xander >> >> >> >> On Mon, Dec 28, 2009 at 1:01 AM, Nologic420 <[email protected]> wrote: >> >>> swfobject is unrelated to skins. I hear that a lot from this group. But >>> the fact is, this component was created to make the adobe html code >>> compliant and a big part of that issue is that people use the skins in both >>> flash and dreamweaver to quickly add play controls to their flv files. >>> Without the skins you have to include it in your swf and it is bulky, plus >>> it has to reload each time you flip to another movie. So it seems to me that >>> if you are going to support a different approach you should also cover the >>> general features of the products that use the code that you are trying to >>> make more compliant. A huge feature of the adobe flash detection kit is that >>> it immediately adds functionality for the skins - no questions asked. And if >>> you are trying to replace something that is known to work I would think you >>> would create something that has the same functionality only better. >>> >>> The really stupid thing is that the embed tag has not become a part of >>> the html standard. It worked for years, it was flawless. >>> ------------------------------ >>> *From:* Philip Hutchison <[email protected]> >>> *To:* [email protected] >>> *Sent:* Sat, December 26, 2009 8:04:26 PM >>> *Subject:* Re: I don't speak Geek. >>> >>> SWFObject is unrelated to the use of skins. All SWFObject does is embed >>> a SWF into an HTML page. This is why you will probably not find any >>> SWFObject-related discussions of skins. >>> >>> Regardless of what method you use to embed a SWF into your HTML, you will >>> encounter the same problems with skins, such as 'what file path should be >>> used when loading the other elements into the skin SWF?' and 'what flashvars >>> are required for this project?'. >>> >>> RE: paths, the easiest solution is to use absolute paths for all >>> elements. ("http://domain.com/movie.swf"; instead of "../movie.swf") >>> >>> RE: Flashvars, it depends on your project. The Adobe embed code you >>> provided below lists the following flashvars: >>> >>> MM_ComponentVersion=1 >>> skinName=Halo_Skin_3 >>> streamName=shotover >>> autoPlay=false >>> autoRewind=false >>> >>> You can learn more about flashvars on Adobe's site, and our SWFObject >>> documentation >>> site<http://code.google.com/p/swfobject/wiki/documentation>describes how to >>> specify flashvars using SWFObject. >>> >>> As for the particulars of how a skin works with its other files, there's >>> no way we can possibly know, because there are a ton of custom projects out >>> there that all use their own approaches/mechanisms. We focus purely on >>> embedding a SWF into an HTML page and leave other details (such as skinning >>> and other internal mechanisms) to the developers that created the SWFs. >>> >>> In your case, it appears you're trying to specify skin details for Adobe >>> Flash's FLV Player component. That means you need to go to Adobe's site to >>> get details on how their FLV Player component works and what flashvars it >>> accepts. >>> >>> As for embedding, the easiest thing for you would be to go to the SWFObject >>> code >>> generator<http://www.bobbyvandersluis.com/swfobject/generator/index.html>and >>> type in the details for your files. The generator will handle the >>> rest. If you're playing the FLVs in an iframe, the SWFObject code needs to >>> be in that iframe and not the parent HTML file. >>> >>> - philip >>> >>> >>> >>> >>> On Sat, Dec 26, 2009 at 11:20 AM, Nologic420 <[email protected]>wrote: >>> >>>> Haha.. No. I don't think you are all geeks. I just think the information >>>> available for the swfobject is too convoluted. I have searched the net for >>>> good answers about the script and using it with skins, fla and a >>>> progressive >>>> down loader packaged with adobe CS3 Flash and Dreamweaver - none of the >>>> answers were clear. Sorry if you were offended. Not intended. >>>> >>>> ------------------------------ >>>> *From:* X.Smalbil <[email protected]> >>>> *To:* [email protected] >>>> *Sent:* Fri, December 25, 2009 10:35:51 PM >>>> *Subject:* Re: I don't speak Geek. >>>> >>>> So what do you think.. that we're geeks ? >>>> You are lucky Im happy today or else I would have fully flamed you so >>>> you would shit all over you keyboard. >>>> You should stop using google for porn and use your brain for other >>>> things than analyzing titties. It's like your email >>>> adress says.. no logic. >>>> >>>> >>>> >>>> On Thu, Dec 24, 2009 at 2:31 PM, Nologic420 <[email protected]>wrote: >>>> >>>>> This is all geek to me man. I try to keep my site nice and tidy. But I >>>>> have been using the Adobe detection Kit to set up the skin I use for >>>>> my progressive videos and then I play them in an iframe. The question >>>>> is how do I turn this code into the correct code for SWFObject so it >>>>> plays with the skin. >>>>> >>>>> <script type="text/javascript"> >>>>> AC_FL_RunContent( 'codebase',' >>>>> http://download.macromedia.com/pub/%0Ashockwave/cabs/flash/%0Aswflash.cab#version=8,0,0,0 >>>>> >>>>> >>>>> www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash >>>>> ','movie','FLVPlayer_Progressive' >>>>> ); //end AC code >>>>> </script> >>>>> <noscript> >>>>> <object classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" >>>>> codebase=" >>>>> http://download.macromedia.com/pub/shockwave/cabs/flash/%0Aswflash.cab#version=8,0,0,0"; >>>>> width="562" height="411" id="FLVPlayer"> >>>>> >>>>> <param name="movie" value="FLVPlayer_Progressive.swf" /> >>>>> <param name="salign" value="lt" /> >>>>> <param name="quality" value="high" /> >>>>> <param name="scale" value="noscale" /> >>>>> <param name="FlashVars" >>>>> value="&MM_ComponentVersion=1&skinName=Halo_Skin_3&streamName=shotover&autoPlay=false&autoRewind=false" >>>>> / >>>>> > >>>>> <embed src="FLVPlayer_Progressive.swf" >>>>> >>>>> flashvars="&MM_ComponentVersion=1&skinName=Halo_Skin_3&streamName=shotover&autoPlay=false&autoRewind=false" >>>>> quality="high" scale="noscale" width="562" height="411" >>>>> name="FLVPlayer" salign="LT" type="application/x-shockwave-flash" >>>>> pluginspage="http://www.adobe.com/shockwave/download/download.cgi? >>>>> P1_Prod_Version=ShockwaveFlash<http://www.adobe.com/shockwave/download/download.cgi?%0AP1_Prod_Version=ShockwaveFlash>" >>>>> /> >>>>> </object> >>>>> </noscript> >>>>> >>>>> Thanks .. I only need this code writen once and can use it with all of >>>>> my movies since they all have the same player controls. Millions of >>>>> thank yous !!!! >>>>> >>>>> -- >>>>> >>>>> You received this message because you are subscribed to the Google >>>>> Groups "SWFObject" group. >>>>> To post to this group, send email to [email protected]. >>>>> To unsubscribe from this group, send email to >>>>> [email protected]. >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/swfobject?hl=en. >>>>> >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "SWFObject" group. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]<swfobject%[email protected]> >>>> . >>>> For more options, visit this group at >>>> http://groups.google.com/group/swfobject?hl=en. >>>> >>>> -- >>>> You received this message because you are subscribed to the Google >>>> Groups "SWFObject" group. >>>> To post to this group, send email to [email protected]. >>>> To unsubscribe from this group, send email to >>>> [email protected]<swfobject%[email protected]> >>>> . >>>> For more options, visit this group at >>>> http://groups.google.com/group/swfobject?hl=en. >>>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "SWFObject" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<swfobject%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/swfobject?hl=en. >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "SWFObject" group. >>> To post to this group, send email to [email protected]. >>> To unsubscribe from this group, send email to >>> [email protected]<swfobject%[email protected]> >>> . >>> For more options, visit this group at >>> http://groups.google.com/group/swfobject?hl=en. >>> >> >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "SWFObject" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]<swfobject%[email protected]> >> . >> For more options, visit this group at >> http://groups.google.com/group/swfobject?hl=en. >> > > -- > You received this message because you are subscribed to the Google Groups > "SWFObject" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<swfobject%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/swfobject?hl=en. > -- You received this message because you are subscribed to the Google Groups "SWFObject" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/swfobject?hl=en.
