An other thing that just came to my mind: Accessibility implications on different platforms have to be considered....
There is much work in progress with ATK and switching to D-BUS, so that non-gnome environments can use ATK. That will take some time. And I am also not sure about the status of Qt's IAccessible2 implementation on Windows - which then would also mean that all OOo UAA implementations would need to be bridged to IA2 then, instead of to Java Accessibility APIs. Without Accessibility issues solved/solvable, every toolkit change is a no-go. Malte. Malte Timmermann wrote, On 01/16/09 16:44: > When reading the announcement, I also though that Qt would be a valid > option now :) > > The reason that I didn't post it here was that I didn't want to discuss > it when nobody would work on a VCL replacement now. > > Sun Team in Hamburg not working on it of course doesn't mean that not > somebody else could do, but: > > I think it's reasonable to wait what the project renaissances > (http://wiki.services.openoffice.org/wiki/Renaissance) will bring us. > > If the outcome of that project is that almost all UI would be created > from scratch, than changing the toolkit is not so much (extra) work > compared to "just" switching to a new toolkit. > > And just for clarification: Qt could be something for the _widget_ part > of VCL. Exchanging the output device part of VCL probably wouldn't be > very reasonable, because a lot of magic for CTL, RTL, Font stuff, meta > file recording etc. is built in there. At least it would be a (very) big > additional chunk of work. > > Malte. > > Éric Bischoff wrote, On 01/16/09 16:31: >> Le vendredi 16 janvier 2009 16:08:40 eric b, vous avez écrit : >>> I don't know the API, but I got several questions : >> The API is really a programmer's relief. Simple, straightforward, clean. >> >>> - I know the Linux/ Mac side could be ok, but how does it work on >>> windows ? >> Short answer: very well. >> >> BTW, one of the advantages of such a change would be that all widgets would >> have the "native" look and feel of the platform. >> >>> - vcl has a lot of deep roots in OOo, land this will be a long and >>> difficult task to change. >> Yes. But it's been years that VCL replacement is discussed, now OOo has an >> opportunity to delegate the graphical lowest layers to a rock-solid, C++, >> toolbox. >> >> There's of course the intermediary solution to have a VCL-Qt driver >> (vclplug) >> that would do the job in the intermediary phase. >> >> > > --------------------------------------------------------------------- > 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]
