To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=98680





------- Additional comments from r...@openoffice.org Tue Feb  3 17:05:04 +0000 
2009 -------
> ab->rene: Obviously I missed to block some of the outputs
> for the extension mode. Developing in Windows is not help-
> ful here as you never see stdout. :-( Anyway, easy to fix.

Yes, use Linux ;-)

> Pre-indexing is not so nice as it makes search support for
> extension help much more difficult for extension developers.
> Now they don't have to care at all, otherwise they would
> have to deal with the OOo build environment, makefiles etc.

I don't really think we should deal easiness for development with
a technical better solution, but...

> On the other hand I don't see the benefit of pre-indexing,
> as at runtime the search would fail anyway without Lucene.

Correct, but if they have lucene2 installed (I *do* have lucene, just
not depended on by -help-* or -wiki-publisher but the openoffice.org
metapackage, and anyone can install it. When it's installed search
works because it's pre-indexed and just the missing piece was lucene)

> So what do you think about silently ignoring a No-Lucene
> situation when deploying an extension. A little bit hacky,
> but I think acceptable as this does not hide errors in the
> help content itself. The situation afterwards would be the
> same as for the Office in general: Extension works and has
> help, but help cannot be searched.

As I said above, the situation would be different. For the office, the
searching just will work if you install liblucene2-java. For the extension
case it won't - unless you deregister/register the extension again
(means: re-install/install the package)

> What do you think concerning the target? Do you consider 
> this to be a 3.1 showstopper? The fix should be easy, but
> we would have to discuss this with mh.

Yes, I do. :)

Regards,

Rene

---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@framework.openoffice.org
For additional commands, e-mail: issues-h...@framework.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to