Kohei Yoshida wrote: > On 10/17/06, Mathias Bauer <[EMAIL PROTECTED]> wrote: >> Kohei Yoshida wrote: >> >>> On 10/17/06, Kohei Yoshida <[EMAIL PROTECTED]> wrote: >>>> On 10/17/06, Mathias Bauer <[EMAIL PROTECTED]> wrote: >>>> >>>> From what I understood I also assumed that you are using some calc C++ >>>> classes. Correct? Or are you using only the UNO API? >>>> >>>> No, but I use resmgr API. >>> >>> I meant, I'm only using the UNO API plus the resmgr API (something >>> similarly called in the tools module, sorry I don't have access to the >>> source right now), which is not UNO as far as I know. As I mentioned, >>> the only change in the 'sc' module is with the menu. >> >> Sorry for my last mail, I sent it before I retrieved new mail. :-) >> So if we had access to resources via UNO in the future you could put >> your module into a UNO package, that's fine. > > Correct. The resource manager is the only non-UNO dependency I have > currently.
Do you use only string resources? As you told you are not using code from sc. Do you have dependencies to other C++ libraries except those in the SDK? Typical candidates would be vcl, tools (other stuff than resmgr), svtools, svx, sfx2, xmloff, ...? > Another issue with UNO package was that the menu item always goes > under Tools > Add-Ons. But if Carsten's solution does solve this > issue (haven't tested it yet), then I won't have this issue. Yes, Carsten's solutions allows to put menu items anywhere you want. > Although Niklas once mentioned that (on [EMAIL PROTECTED]), eventually, we may > need to redo the dialogs using the native VCL, instead of the current > UNO AWT to take advantage of VCL's advanced range selection > capability. So, that may be another constraint down the road if we > decide to go the UNO route. As we are currently redesigning (extending) our UNO AWT toolkit your use case would be a welcome addition to our new concept. As this is also Carsten's job I'm sure he will be eager to learn what VCL has to offer here and the toolkit doesn't so we can add it to the concept. Implementing support for this in the toolkit will enable you to stay with UNO AWT even if you wanted to use range selection. At the end VCL and the UNO AWT toolkit are only two facets of the same thing. There is no fundamental reason that something you find in VCL can not be made available in the toolkit. Best regards, Mathias -- Mathias Bauer - OpenOffice.org Application Framework Project Lead Please reply to the list only, [EMAIL PROTECTED] is a spam sink. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
