Meeting Michal Ceresna about MozSwing
Attendees:
- Peter Zavadsky
- Sandip Chitale
- Joelle Lam
- Michal Ceresna
Agenda
- Introductions
- Status and Direction of MozSwing
- What Sun is trying to do with Embedded Browser
- Issues with MozSwing
- Requirements for us to use MozSwing
- XulRunner Branched
- Contracting
Issues with MozSwing -
- Inside an Applet, window freezes
- Linux Stability - Event loop issues
- The current implementation was the fastest to implement but the least stable.
- There are other implementations that would take longer to implement but will be more stable.
Requirements for us to use MozSwing
- We need to be able to build this on Solaris.
- Mozilla using xlib has not been tried yet, because in Michal's experience using not standard Mozilla builds are not stable because they have not been tested.
- Sandip expressed concerns that XLIB and GTK may not work well together.
- This is something Sandip and Joelle need to look into further.
- Resources for Bug Fix.
- When we have a bug fix, there may be some delay since Michal is contracting.
- Commit Access
XulRunner Branched
- Why don't you use xulrunner binaries?
- Michal has found it difficult to get patches committed since JavaXPCOM is a small division of Mozilla and not high priority.
- Allows for quick patches and modifications as necessary.
- Having a binary would be ideal, but more difficult to make changes.
- For now the patches are in sourceforge.
GFX ( to have a true Swing implementation )
- Michal does not think this will be easy since it is going to require it's own rendering.
- The output may look different than the browser rendering.
- He has done a little bit of work with GFX.
- Sandip will send an email with further details.
Commit Access
- It is possible to get commit access as we become more involved.