since the topic should be discussed in public. You provided helpful links and made the presentation at OOoCon2004, which really looks good...
Now the bootstrap mechanism works just fine, so we get 1 line of code instead of approx. 10 as it used to be.
But what about the super-interfaces concept? I only read documentation about the concept (thus only abstract stuff), but nowhere can I find anything *real*, meaning: any working example for 680 builds that doesn't use queryInterface and instead uses the mentioned .create() on new-style services.
Has this concept not been applied to some API parts so that commonly used things can be written in much shorter code in Java? What is state of this process?
2004/11/24, Stephan Bergmann <[EMAIL PROTECTED]>:
Mathias Bauer wrote:
> Stephan Bergmann wrote:
>
>
>>It is not planned to duplicate the existing OOo UNO API in new style
>>wholesale. Rather, new functionality that is now added to the OOo UNO
>>API uses the new style (e.g., the functionality at com.sun.star.uri),
>>and if some part of the existing API is considered in urgent need of a
>>redesigned replacement, such a replacement would use the new style,too.
>> (However, any heroic efforts to actually do duplicate the existing OOo
>>UNO API wholesale are nevertheless very welcome.) :)
>
>
> So the question remains how an "urgent need" could be detected. IMHO
> this should be done by putting feature requests into Issuezilla, the
> same way as you would treat "end user features".
I thought more about urgent needs resulting from realizing that a
specific part of the API is broken, so that a redesign is necessary,
anyway. But, of course, if someone thinks that a part of the API could
be replaced with something that is drastically more usable, that's worth
an issue.
-Stephan
> Best regards,
> Mathias
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Best Regards
Christian Junker
