Re: HTML for Flash movies

[torcaza]

First posting- to this mailer


I wanted to clarify between the smart update code and aftershock utility. 

 I might clarify or confuse and if someone has more insight then please 

let me know.


I wonder if the problem your are having with a slow first page is related 

to specifically to the Aftershock utility.  The Aftershock utility with 

java player seems to make java the number one choice for robust java or 

all java browsers (user choice).  This tremendously slows down all 

browsers (except ie4 on a wintel machine since java is enhanced there 

(ironically)).  If you turn off java on your browsers with the plugin it 

will get the first page much faster (test it to see if this swill make 

the page work faster).  


I suggest reordering the scripts in the aftershock html to make the 

pluging mode work first and try to avoid getting java to kick in which 

makes everything especially on Netscape and a Mac work slower.  You might 

have already done this.  I have not yet tried to work around it.  But I 

have seen the java version work well in one scene movies with streaming 

sound.


Later,


Kai Janson

Conscious Foods, Inc.  

estatecafe.com

kaiser7aol [dot] com

 >I should clarify...

>

>I was responding to mail sent by Tommy Rainwater about Aftershock and how

>slow it was.

>

>Here's the story:

>

>I found that Aftershock by itself did not allow me a complete solution to

>the plugin problem, though it does generate some useful javascript code... I

>used carefully selected & revised chunks of this code together with the

>"Smart Button" concept. I spent *hours* over it, trying to make a foolproof

>way to ensure that people who did not have the Flash plugin would be

>detected correctly & have the minimum hassle downloading it.

>

>The entire result worked perfectly, except that it was unacceptably slow. On

>accessing the first page, a grey page appeared for 20-30 seconds (with a

>33600 connection ). I put this down to the fact that the browser had to call

>MM *as well as* our site -every time- regardless of whether the user had the

>plugin or not...

>

>Perhaps I should have been more specific and referred to the "Smart Button"

>aspect of things, which is where the holdup was caused; specifically,

>accessing MM... So apologies for that.

>

>My impatience comes from the fact that I feel that I have wasted a great

>deal of time, on and off, redoing the intro's for our Flashed sites purely

>because of the plugin problem... And then to feel mislead by MM over the

>"Smart Button" issue just sent me over the top.

>

>I now have a mainly home-grown system which seems to work well (using a mix

>of server-side perl, client-side javascript & a trick with a Flash movie)

>

>That said, I sincerely feel that Flash2 is the greatest single thing to

>happen to web site developers. Which is why I care so much about making sure

>technicalities don't get in the way for those who browse Flashed sites.

>

>I'm looking forward to Flash3...

>

>

>Ben Rogers

>Pepper Head Design (Hot Ideas) Ltd

>http://www.pepperhead.co.uk

>

>Email Disclaimer

>The information in this email is confidential and may be legally privileged.

>It is intended solely for the addressee. Access to this email by anyone else

>is unauthorised.

>If you are not the intended recipient, any disclosure, copying, distribution

>or any action taken or omitted to be taken in reliance on it, is prohibited

>and may be unlawful. When addressed to our clients any opinions or advice

>contained in this email are subject to the terms and conditions expressed in

>the governing Pepper Head Design client engagement letter.

>

benpepperhead [dot] co [dot] uk

>-----Original Message-----

>

From: John Dowdell <jdowdellmacromedia [dot] com>

>

To: flashershocker [dot] com <flashershocker [dot] com>

>Date: Tuesday, February 17, 1998 11:30 PM

>Subject: Re: HTML for Flash movies

>

>

>>At 9:22 AM 2/17/98, Ben Rogers wrote:

>>>It *is* too slow...

>>>It's a bit much, IMNSHO, that MM did not warn of this when they

>>>enthusiastically announced these two methods.

>>

>>

>>What, specifically, is slow for you?

>>

>>Is it the browser detection? The browser dynamic writes? The retrieval of

>>the external .JS archive for implementation? Is it the actual one-time

>>process of creating the HTML?

>>

>>Right now I'm not well able to scan the comment... what specific piece of

>>the process do you find slower than what you expect?

>>

>>jd

>>

>>

>>John Dowdell, Macromedia Tech Support, San Francisco CA US

>>

>>Private email options: http://www.macromedia.com/support/priority.html

>>Search technotes: http://www.macromedia.com/support/search/

>>Search DIRECT-L: http://www.mcli.dist.maricopa.edu/director/digest/

>>Online savvy: http://search.yahoo.com/bin/search?p=netiquette

>>Cross-browser scripting resources: http://www.dhtmlzone.com/

>>

>>

>>

>

>




          ___________________                               

\\\\\\\\\\  ~~~~~~~~~~~~~~~~     //////////                          

\\\\\\\\\\\     La Torcaza   ///  ////////

\\\\\\\\\\\\     Estate     ///  /////////    

\\\\\\\\\\\\\    coffee        ///////////

\\\\\\\\\\\\\\ ``````````` ////////////////

//////////////////////////////////////////

 http://www.estatecafe.com

torcazaix [dot] netcom [dot] com