Hi all, Just my 2 cents...
I guess the point here is that as one of the flagship open-source desktop projects OOo must have top-notch core and UI frameworks. If it hasn't, it must become of the highest-level priority for the nearest release. Instead of implementing new features on top of the existing pile of code I think the core developers should concentrate on the core design. Once that is in place, 3rd-parties will join in and implement all features you can dream of. Until you remove most of the road-blocks for 3rd-party developers you will be stuck implementing all requested functionality yourselves with no external help. The Linux Kernel, Mozilla and Eclipse are two very good examples of projects doing it right in this respect. Related links: http://blog.thebehrens.net/2008/09/29/ooo-non-vision/ http://blogs.sun.com/GullFOSS/entry/chrome_again http://wiki.services.openoffice.org/wiki/Chrome_Again http://www.gnome.org/~michael/blog/ooo-commit-stats-2008.html - an analysis showing that most of the OOo contributors are Sun employees which is a good indicator that OOo fails to attract developers Thanks, Yegor 2008/11/17 Marcin Miłkowski <[EMAIL PROTECTED]>: > Juergen Schmidt pisze: >> >> Philipp Lohmann wrote: >>> >>> Marcin Miłkowski wrote: >>>> >>>> Hi, >>>> >>>> some 3 years ago, there were preliminary experiments with using XUL in >>>> OpenOffice.org, and XUL was supposed to replace VCL, eventually. What is >>>> the >>>> status of these plans? >>> >>> The plan was to embed XUL into a VCL window (thereby having teh capabilty >>> to use XUL dialogs in OOo. > > Yes, but that would be fair enough. > >>> >>>> VCL makes developing UI quite a tedious task, and is not extendable >>>> outside the core, so Java extension developers (like me) tend to use >>> >>> Agreed. >>> >>>> Java Swing which looks ugly but at least is extendable. With XUL, I >>>> could probably have more "native-looking" UI elements... >>> >>> The status of those plans is basically "on hold indefinitely". Currently >>> nobody has the time it seems. As far as I remember there were however plans >>> to make the basic dialog editor available as editing tool for XML files >>> (specifically aimed at extensions if I remember correctly) that would then >>> be executable by OOo's UNO toolkit. I don't know how far that is, but >>> probably someone on the list knows ? >> >> you can use the dialog editor in the office to create your own dialogs and >> can export this dialogs for example in your NetBeans project or anywhere >> else. Later on you can use this dialog from Java or any other UNO language >> in your own extension. It works but it's still not really satisfying. A lot >> of controls are missing, no layout manager until today (there is a layout >> manager project ongoing), ... We have a lot of space for improvements here. > > Well, I don't think that a dialog editor is that important. > > Much more important is the fact is that there is no way to extend the > existing UI, for example to have a tree with checkboxes (used in many > packages for configuration options). At least it's not doable in Java (or > nobody knows how to do it, which has roughly the same effect). So having > more controls is what is important for developers, actually. If it was > possible to extend the UI from Java, I wouldn't mind using the most verbose > AWT/UNO code to instantiate it. ;) > > That's the missing functionality #1 from my point of view... > > Regards > Marcin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
