I wouldn't use mozswing for each question in a step at this point. Hopefully in the future we can use it that way, but not yet. I also would not count on mozswing becoming a lightweight component anytime soon. We would like to make that happen but I think it is lower priority than some other improvements we want to make to it.
Any handling of Quicktime will have to be done with a heavyweight component. To solve your current problem Tony, I would suggest embedding mozswing inside of xhtmlrender to handle the flash. Last time I worked with xhtmlrender it was possible to embed swing components inside. So mozswing could be embedded that way inside. I don't remember the details of doing this embedding, and I think it has been changed anyhow. Scott Stephen Bannasch wrote: > At 3:50 PM -0800 1/31/08, Anthony Perritano wrote: > >> you mean for every question? say a self test step has 4 questions. >> that would be 4 mozswing browsers imbed in the step? do you think this >> is practical? >> > > I don't know. It was certainly the goal of the work to be able to do this. > > >> mozswing is a heavy component right? it doesn't mix well with light >> weight components in the container? >> > > Yes, mozswing is a heavyweight component -- you are right about the UI > problems. This should be fixed at some point also. > > For more info on how and when these fixes will be implemented Scott will need > to add to this thread. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SAIL-Dev" 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/SAIL-Dev?hl=en -~----------~----~----~----~------~----~------~--~---
