Is there any "OpenOffice.org Look&Feel" for extensions in Java?

[Konstantin Tokarev]

Is there any "OpenOffice.org Look&Feel" for extensions in Java?
--
Regards,
Konstantin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Marcin Miłkowski]

Konstantin Tokarev pisze:
> Is there any "OpenOffice.org Look&Feel" for extensions in Java?

As far as I know, there is none. If you want to have the native look
(which is different under different OSes and graphical managers), use
the AWT via UNO. However, this is a bit cumbersome if you display
something more complex than a message box. And you cannot really
implement anything new in the UI (no new UI elements by overriding
classes, as far as I know). No wonder most extension developers don't
use it...

Regards
Marcin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Juergen Schmidt-3]

Marcin Miłkowski wrote:

> Konstantin Tokarev pisze:
>> Is there any "OpenOffice.org Look&Feel" for extensions in Java?
>
> As far as I know, there is none. If you want to have the native look
> (which is different under different OSes and graphical managers), use
> the AWT via UNO. However, this is a bit cumbersome if you display
> something more complex than a message box. And you cannot really
> implement anything new in the UI (no new UI elements by overriding
> classes, as far as I know). No wonder most extension developers don't
> use it...

it is correct that the UNO awt toolkit has limitations but it is the
best way to integrate in the office and to avoid problems.

You can use the dialog editor in the office to do the initial design.
Export the dialog description in your extensions Java project and use
via dialog provider ... Appropriate handler have to be implemented and
registered to handle the different events. See the SDK samples and the
DevGuide docu.
With OOo 3.2 it is also possible to import dialog descriptions and
modify it again with the dialog editor.

There is still a lot of space for improvements and volunteers are always
welcome ;-)

Juergen

>
> Regards
> Marcin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Marcin Miłkowski]

Juergen Schmidt pisze:

> Marcin Miłkowski wrote:
>> Konstantin Tokarev pisze:
>>> Is there any "OpenOffice.org Look&Feel" for extensions in Java?
>>
>> As far as I know, there is none. If you want to have the native look
>> (which is different under different OSes and graphical managers), use
>> the AWT via UNO. However, this is a bit cumbersome if you display
>> something more complex than a message box. And you cannot really
>> implement anything new in the UI (no new UI elements by overriding
>> classes, as far as I know). No wonder most extension developers don't
>> use it...
> it is correct that the UNO awt toolkit has limitations but it is the
> best way to integrate in the office and to avoid problems.

Well, the problem is that Java/Swing programmers are used to create
their own user interface elements, so these limitations are quite serious.

> You can use the dialog editor in the office to do the initial design.
> Export the dialog description in your extensions Java project and use
> via dialog provider ... Appropriate handler have to be implemented and
> registered to handle the different events. See the SDK samples and the
> DevGuide docu.
> With OOo 3.2 it is also possible to import dialog descriptions and
> modify it again with the dialog editor.
>
> There is still a lot of space for improvements and volunteers are always
> welcome ;-)

I've heard that RedOffice 4.5 will support deep and custom changes of UI
using extensions, so if their code gets to the core (someday), then it
should be easier to persuade people to do the switch.

Regards
  Marcin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...

[Juergen Schmidt-3]

Marcin Miłkowski wrote:

> Juergen Schmidt pisze:
>> Marcin Miłkowski wrote:
>>> Konstantin Tokarev pisze:
>>>> Is there any "OpenOffice.org Look&Feel" for extensions in Java?
>>>
>>> As far as I know, there is none. If you want to have the native look
>>> (which is different under different OSes and graphical managers), use
>>> the AWT via UNO. However, this is a bit cumbersome if you display
>>> something more complex than a message box. And you cannot really
>>> implement anything new in the UI (no new UI elements by overriding
>>> classes, as far as I know). No wonder most extension developers don't
>>> use it...
>> it is correct that the UNO awt toolkit has limitations but it is the
>> best way to integrate in the office and to avoid problems.
>
> Well, the problem is that Java/Swing programmers are used to create
> their own user interface elements, so these limitations are quite serious.

sure i totally agree but it is as it is at the moment. I don't see that
we be able to make the big shot. The only thing we can do is to improve
the available controls step by step and can try to improve the overall
usability. This includes hopefully a layout manager some day ;-)

>
>> You can use the dialog editor in the office to do the initial design.
>> Export the dialog description in your extensions Java project and use
>> via dialog provider ... Appropriate handler have to be implemented and
>> registered to handle the different events. See the SDK samples and the
>> DevGuide docu.
>> With OOo 3.2 it is also possible to import dialog descriptions and
>> modify it again with the dialog editor.
>>
>> There is still a lot of space for improvements and volunteers are
>> always welcome ;-)
>
> I've heard that RedOffice 4.5 will support deep and custom changes of UI
> using extensions, so if their code gets to the core (someday), then it
> should be easier to persuade people to do the switch.
>

the hope will never die ;-)

Juergen

> Regards
>  Marcin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@...
> For additional commands, e-mail: dev-help@...
>


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@...
For additional commands, e-mail: dev-help@...