Hello, we are using gtkmozembed to develop the OLPC browser. We recently upgraded to the trunk because the resolution independence features are essential on a 200 dpi screen.
Mozilla 1.9 is looking pretty good but we have been hitting several bugs specific to gtkmozembed. We had to apply several patches to comment out the new code and that's not a good sign. We are interested in contributing bug reports and patches but we are deeply concerned about the direction the gtkmozembed development has taken on the trunk: * A lot of new code has been committed in big chunks, without any apparent review process. * The API is growing without control. The additions doesn't appear to be well thought and the result is really messy. * We are duplicating a lot of code. Global history for example or text selection. * We are breaking working features, for example file pickers and text selection. * Bug reports about the new code are assigned to nobody and ignored. * The approach seem to wrap most of the embedding API in C. I think we should rather keep gtkmozembed a simple widget exposing the basic functionality and allow embedders to use the full xpcom API in C++, pyxpcom or whatever. Can we revert to 1.8 state, discuss the direction and restore the review process for patches that goes in? I don't want to sound blunt but... that's the only way I see to restore sanity. Marco _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
