Hi Michael, Michael Meeks wrote:
> Well, it's clear we need to go out and evangelise. This is the > difference between passive and pro-active :-) There are also more > telling issues such as control, ownership, timeline & RCS of shared code > that tend to be problematic - but that aside ... Yes, please. Let's not spoil our interesting dicussion. > one of the first things > I tried to work on (back in 2001) was using autotools for sal / cppu > etc. such that we could re-use UNO elsewhere in the Gnome desktop: Thanks for bringing this up. For me UNO is the key point. If we don't get others to use UNO we can't share much of what we have, especially not the interesting pieces like e.g. filters. As UNO is very versatile, it can be adapted to different other component technologies (as it already does as we both know). So basically I see a good chance that UNO could be made acceptable from a pure technical POV - good will provided. Unfortunately I already had too many frustrating discussions with developers that don't want to touch UNO because it's "proprietary" and "not a standard" to be very optimistic about that. But there's still hope, so I definitely opt for bringing the URE into a shape that makes it usable separately. > that > met with resounding loathing from the build.pl / dmake lovers - and was > one of the things that killed that co-operation (AFAIR). [ and I was > doing the work and trying to contribute it (even in parallel with dmake > foo) ]. Strangely, not the first time that our passion for our (frankly > unbelievable) build-system has substantially hindered useful > co-operation with others ;-) I don't know what exactly was/is the problem, but I hope that this obstacle can be removed some time in the future. But as I'm not a build system expert, I hesitate to elaborate here and jump to conclusions. Something for ESC? > Of course, there is a lot for others to dislike in UNO - the > UCS-2/UTF-16 Win32 heritage of all strings, the appalling intrinsic > threading / granularity problems ( un-addressed by apartments ), My personal POV here is that we should be open for discussing even larger changes of UNO if that could help to make it more popular. Regards, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to "[EMAIL PROTECTED]". I use it for the OOo lists and only rarely read other mails sent to it. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
