Concerning the explanation by Jim about Mozilla+Flash's problem, what
follows is the translation of the explanation by a guy on the LUG Rome mailing
list about what a visual is.  Just for those curious enough to want to know.




  Sandro



|From: ***** ********** <********@********.***>
|To: [EMAIL PROTECTED]
|Date: 01 Jul 2002 12:43:29 +0200
|Subject: Re: [lugroma-tech] I flash su Mozilla
|


  "Visual" is the name that in X Window is given the set of informations
concerning a given visualization mode and consequently the image data
packing.

  If you issue the xdpyinfo command you'll see at the bottom of the screen a
list of visuals: this list is passed to X applications to let them know what
internal graphic formats are supported by the server.

  When an application must pass some images to the X server, it selects one of
the available visuals and it uses the appropriate X functions to convert its
images into the right choosen visual fot their visualization.

  Note that some visual can imply further image conversions, if you're using
say 16 bit colors, that is, 65536 colors, and you try using an indexed
PSEUDOCOLOR visual, that is 8 bit colors (256 colors), then when the server
will get your image it will convert it into 16 bit colors prior to displaying,
using an appropriate lookup table the application provides it with in the same
function it called.



|From: [EMAIL PROTECTED]
|Date: Fri, 28 Jun 2002 10:42:37 -0400 (EDT)
|Subject: Re: [Ltsp-discuss] moz-flash
|
|The way I understand the Mozilla/Flash problem, it is really
|3 different problems working together to really make things bad.
|
|1) with real Mozilla, plug-ins are run in the same process space
|   as mozilla itself.  So, if a plug-in crashes, it takes the browser
|   down with it.
|
|2) Mozilla is passing the wrong "visual" to the plug-in.  I'm not
|   sure what that means, but the flash plug-in has a hard time with
|   it.
|
|3) The flash plug-in can't handle the incorrect visual, and dies,
|   taking the browser with it.
|
|I think the problem is probably a whole lot more complex than what
|I show above, but that is what I've learned from the bugzilla report.
|
|There are reports that if your browser window is 800x600 or less, then
|flash will work.  I've not noticed whether this is tru.
|
|Other browsers, such as Galeon and Opera probably don't run the plug-in
|in the same process space as the browser, so if the plug-in dies, the
|browser keeps running.  I think that the older netscape also runs the
|plug-in as a separate process.
|
|There is a guy in the mozilla team who says he'll fix #2 above.  Also,
|there is talk of changing Mozilla to run plug-ins as a separate process,
|but I don't know how soon that will be.
|


-- 
Bellum se ipsum alet.
       La guerra nutre se stessa.

Livio, "Ab urbe condita", XXXIV,9







-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
We have stuff for geeks like you.
http://thinkgeek.com/sf
_____________________________________________________________________
Ltsp-discuss mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-discuss
For additional LTSP help,   try #ltsp channel on irc.openprojects.net

Reply via email to