Bernhard Dippold wrote: > Mathias Bauer schrieb: >> KAMI wrote: >> > That' what I wrote ;-): >>>> Gallery and template extensions are easy to be integrated in OOo (just >>>> click on "Add" in "Tools - Extension manager" and search for the .oxt >>>> files), but there should be a hint somewhere to close OOo before you >>>> search for the newly installed extensions. >>> Yes you are right. Or are there any way to reinitialize the list of >>> gallery and templates? It would be a very user friendly feature. >> >> Are you sure that you need a restart in case of templates? I thought it >> already works for templates, never tested it for galleries. > > It does work for the gallery too, if the galleries are *not* shown while > installing the extension.
OK, that's still something that needs fixing. What about templates? Did it work for you without restart? >> Please also make sure that you create issues for all the problems you >> discover when working with "non-code" extensions. We are very interested >> in them. > > I don't have enough programming knowledge to know if a problem occurs > because of the extension's code or it's implementation in OOo. Well, I was talking about *non-code* extensions, so everything not working should be point to a problem in OOo's code. ;-) > With KAMIs package [1] I discovered a strange behavior of the > progressing bar: The package loaded in about 10 seconds, but the bar > just started to move after eight seconds (WinXP, Intel Pentium 1,66GHz, > Core Duo, 2 GB RAM / OOo2.1.rc1). I assume that this isn't a real bug, the progress bar is only a guess - at the end the extension manager doesn't know about the time needed to install each part of the extension. >> It would be nice if you could send me a comprehensive list of all found >> issues (even those you created already) to my OOo account (my user name >> is mba) so that can add it to the documentation mentioned above. > > I could file an issue (component framework, subcomponent UI or > extensions/www ?), if you want me to. I was talking about all the issues about non-code extensions that you or Kami might have found and reported. I would like to collect them so that we have an overview about the state. > Perhaps we should think of a central repository containing additions to > OOo directly downloadable from the program. These additions should not > only be extensions and packages, but single items as well directly to be > loaded into the galleries or template folders. There already plans made in the extensions project. Downloading single items of course isn't planned their (nomen est omen!) and I dount that this will become very popular as it must be implemented for each and every kind of items individually. I doubt that this will happen. I think extensions (formerly known as packages - EFKAP ;-)) are the way to go. The overhead created by them is minimal. Ciao, 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]
