To comment on the following update, log in, then open the issue: http://www.openoffice.org/issues/show_bug.cgi?id=89713
------- Additional comments from r...@openoffice.org Tue Jan 6 14:28:38 +0000 2009 ------- > jcn: As I already wrote (#desc20) it does not work to have a basis layer > reference a brand layer. Hence, the attached gengal.sh-3layer.diff is not an > acceptable, clean solution. As long as it works... Clean is not always equivalent with "working". We can get a clean thing for 3.1 if you invest the time. We have a working solution now... > @rene: I am *still* not confident I do understand exactly the scenarios in > which gengal is supposed to be called. Then think. > If it is intended to be called by arbitrary clients of OOo to import gallery > data into an OOo installation (similarly to unopkg being called by arbitrary > clients to import extensions) then it should be moved to the brand layer > program directory (i.e., become part of the stable OOo interface, like unopkg > etc.). Yes, it basically does. It does not import them directly, though but just creates the files OOo expects and you can then put it into the dir. Like when you would create them out of the OOo UI: /. /usr /usr/lib /usr/lib/openoffice /usr/lib/openoffice/share /usr/lib/openoffice/share/gallery /usr/lib/openoffice/share/gallery/sg89.sdv [...] > If, on the other hand, gengal is only supposed to be called in certain > restricted scenarios that can be subsumed under the broad category of > producing OOo installations, then I would still argue to remove gengal from > the OOo installation set and instead making it available (in whatever form> > appropriate) during such production of OOo installations. E.g. the SDK. It's just additional .sgv/.thm/.sdv files. Again: the OOo install is the same, it's just additional files put there by whoever elese, like when the usert would create a new Gallery item via the UI. I dont argue for it staying in the main install, it also can be in the SDK (that's what I actually have in Debian), but it has to stay and be available (and work). --------------------------------------------------------------------- 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...@graphics.openoffice.org For additional commands, e-mail: issues-h...@graphics.openoffice.org --------------------------------------------------------------------- To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org For additional commands, e-mail: allbugs-h...@openoffice.org
