Re: [dev] Is it still worth to work on OpenOffice' gui toolkit?
Clemens Eisserer wrote: Hello, I am a long-term openoffice user and to some degree a bit of gui performance fanatic. I dislike UIs which show tearing effects and don't perform well and just very few toolkits really make me happy performance-feeling whise. I just can speak for OOo running on Linux, which shows some ugliness when working with menus and some other small performance glitches. I would like to work on it in my vacation, however does it still make sence to work on the currently used toolkit (vcl or however its called)? I read many articles that OOo will move to a self-written abstraction layer which uses underlaying widgets. In which timeframe will this happen, or is this still planned at all. VCL will still be our technology base for the GUI in the forseeable future as we don't expect to get enough developers to rewrite all the existing UI code in a short time frame, so working on improvements for VCL still makes a lot of sense. The only UI or graphics component in OOo that does not use VCL currently is the presentation engine (AFAIK). ATM we are extending the UNO API layer above VCL to enable the development of more feature rich components and Add-Ons that don't link against VCL and so can be implemented and deployed independently from our release and development cycles, but this layer still is on top of VCL. Wether we will replace the implementation of this API toolkit later on is still object of discussion but IMHO will not happen soon. If you are interested in improving VCL please join the dev@gsl.openoffice.org mailing list. The developers over there will be glad to get some help, I'm sure. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Is it still worth to work on OpenOffice' gui toolkit?
Hello Mathias, Well my personal opinion would be to better stick with QT or if this is not possible because of licensing reasons use wxwidgets. This way we'll re-invent the wheel another time. I know this has been discussed many times and I am not in a position to suggest anything, I am not very experienced at all ;) Thanks a lot for your suggestions, I'll register there. lg Clemens 2006/6/3, Mathias Bauer [EMAIL PROTECTED]: Clemens Eisserer wrote: Hello, I am a long-term openoffice user and to some degree a bit of gui performance fanatic. I dislike UIs which show tearing effects and don't perform well and just very few toolkits really make me happy performance-feeling whise. I just can speak for OOo running on Linux, which shows some ugliness when working with menus and some other small performance glitches. I would like to work on it in my vacation, however does it still make sence to work on the currently used toolkit (vcl or however its called)? I read many articles that OOo will move to a self-written abstraction layer which uses underlaying widgets. In which timeframe will this happen, or is this still planned at all. VCL will still be our technology base for the GUI in the forseeable future as we don't expect to get enough developers to rewrite all the existing UI code in a short time frame, so working on improvements for VCL still makes a lot of sense. The only UI or graphics component in OOo that does not use VCL currently is the presentation engine (AFAIK). ATM we are extending the UNO API layer above VCL to enable the development of more feature rich components and Add-Ons that don't link against VCL and so can be implemented and deployed independently from our release and development cycles, but this layer still is on top of VCL. Wether we will replace the implementation of this API toolkit later on is still object of discussion but IMHO will not happen soon. If you are interested in improving VCL please join the dev@gsl.openoffice.org mailing list. The developers over there will be glad to get some help, I'm sure. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Is it still worth to work on OpenOffice' gui toolkit?
Clemens Eisserer wrote: Hello Mathias, Well my personal opinion would be to better stick with QT or if this is not possible because of licensing reasons use wxwidgets. This way we'll re-invent the wheel another time. Well, VCL and its predecessor StarView are much older than QT and IIRC also older than wsWidgets. So the question remains who invented which wheels. :-) Honestly speaking, we would love to replace VCL with something that has all the features we need, supports the same platforms in the same quality, has all the features we currently not have but want (GUI editor, layout manager etc.) and has a bright future. But until now each of the candidates (XUL, Java, wxWidgets, QT) has some disadvantages and as I wrote we need a migration strategie for our current GUI code. However, questions like these are best discussed on the gsl mailing list. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Is it still worth to work on OpenOffice' gui toolkit?
Hello, I am a long-term openoffice user and to some degree a bit of gui performance fanatic. I dislike UIs which show tearing effects and don't perform well and just very few toolkits really make me happy performance-feeling whise. I just can speak for OOo running on Linux, which shows some ugliness when working with menus and some other small performance glitches. I would like to work on it in my vacation, however does it still make sence to work on the currently used toolkit (vcl or however its called)? I read many articles that OOo will move to a self-written abstraction layer which uses underlaying widgets. In which timeframe will this happen, or is this still planned at all. Thank you, lg Clemens - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
