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:
>>
>> > > I see your point, but the decision to break out of being a UNO package
>> > > was made a long time ago, and the reason was the need to use OO.o's
>> > > internal string translation API. This was not availabe to UNO package
>> > > back then, and still isn't today (I know there is one in the works,
>> > > but I can't afford to wait for that).
>> >
>> > >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.
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.
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.
Kohei
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
