Hi Niklas, On 1/25/06, Niklas Nebel <[EMAIL PROTECTED]> wrote:
> With modifying files in other modules, you're leaving the path of a > "pure" component that can be added to any existing OOo installation. Yes, I'm aware of this. At this point, my focus is to figure out how best to approach future integration issue, and also to get some exposure to the users by including it into ooo-build. I will look into building an independent component once this integration task is done so that those interested users can still download a separate solver package as an add-on. A > component can bring its own configuration entries, but as far as I know, > it can't add a menu entry at a specific position (why "Data" anyway, > shouldn't this go under "Tools", near "Goal Seek"?). I agree. Tools near Goal Seek makes more sense. Again, the current location of Solver is just temporary: it may be moved somewhere else later (and probably will). > > The labels for the built-in menu entries are in officecfg, under > registry/data/org/openoffice/Office/UI. Thanks. I'll look into this file. This is probably the information I was looking for. But once we start putting parts > into the "sc" module, one might also imagine moving the whole dialog > into Calc, taking advantage of the better interaction with reference > input (in a built-in dialog, reference input can be started without > pressing a button first). This makes sense. Since this "quick reference input" (or whatever this is called officially) does not seem possible via UNO, to get this functionality we have to create a built-in dialog. On the other hand, I also think that it would make more sense to keep the dialog in the component, not in Calc so that if this solver component becomes optional the app will not have to load the dialog for Solver. This would of course require this "quick reference input" to be made available via UNO, if that's something we can expect in future. We would then have to define a UNO service > interface for the solver core, and could allow several implementations > of that service, accessed from the single dialog. On the other hand, > that might be too much work for now. Yeah, this is probably too much for what we are trying to achieve for now. But eventually we will come to this. > Generally, details about a component's integration are better discussed > on the api-dev list, because that's not specific to Calc, and others who > are not so much interested in Calc might have ideas, too. Ok. If there is any more add-on integration issue, I'll poke at that list. Thanks, Kohei -- Kohei Yoshida OpenOffice.org Calc Hacker http://kohei.us/ooo/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
