|
List Info
Thread: UNO based toolkit API
|
|
| UNO based toolkit API |

|
2007-05-25 04:48:16 |
Hi,
our IRC meeting in the morning was to confusing for me, i
would suggest
to focus on some topics in this specific time slot.
Everything else can
be discussed in separate slots. What do you think?
Anway, as i mentioned in the morning our focus is a UNO
based toolkit
API where we want to reuse as much as possible from the
existing code
base. The advantages are obvious and already documented on
the
odftookit.openoffice.org hoempage.
I would like to evaluate the already collected use cases and
do some
example implementation with the current office API. In a
second step i
would like to analyze the used API's to check how we can
improve them or
how we can make use of the UNO ease of use features to
make these
API's more intuitive and usable if necessary. That means not
that we
automatically will change existing API's incompatible but it
is might be
possible. It has to be analyzed in detail. For missing
features it is
necessary to define new UNO API's and provide an appropriate
implementation.
The important part is to use only core API's and don't make
use of any
view oriented API's (like view cursors for example).
It might be also interesting to compare the results with
AODL or odfj
solutions and take this analysis into account when thinking
about
improvements.
That are tasks which can be done in parallel to the ongoing
modularization tasks which are important for future usage of
the code
base as a toolkit.
The example implementations can be implemented in Java and
Java UNO and
for example NetBeans to make the development much smarter
than.
I am personally behind my own schedule because of some other
important
and longer scheduled task but i am looking forward to work
with
interested people together on this task.
If you are interested please feel free to contact me or
better
communicate on this mailing list and let us think about
concrete steps.
Juergen
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe odftoolkit.openoffice.org
For additional commands, e-mail: dev-help odftoolkit.openoffice.org
|
|
| Re: UNO based toolkit API |

|
2007-05-25 05:07:38 |
Hai Juergen,
We have developed 'e-Administration', a J2EE application for
communication
management (http://ll2b.blogspot.com
). We have used FCK editor. We would
like to integrate open office for ODF.
Can you please advise us how we go about it?
Regards,
Kris Dev
e-Gov Consultant
India.
On 5/25/07, Juergen Schmidt <juergen.schmidt sun.com> wrote:
>
> Hi,
>
> our IRC meeting in the morning was to confusing for me,
i would suggest
> to focus on some topics in this specific time slot.
Everything else can
> be discussed in separate slots. What do you think?
>
> Anway, as i mentioned in the morning our focus is a UNO
based toolkit
> API where we want to reuse as much as possible from the
existing code
> base. The advantages are obvious and already documented
on the
> odftookit.openoffice.org hoempage.
>
> I would like to evaluate the already collected use
cases and do some
> example implementation with the current office API. In
a second step i
> would like to analyze the used API's to check how we
can improve them or
> how we can make use of the UNO ease of use features
to make these
> API's more intuitive and usable if necessary. That
means not that we
> automatically will change existing API's incompatible
but it is might be
> possible. It has to be analyzed in detail. For missing
features it is
> necessary to define new UNO API's and provide an
appropriate
> implementation.
>
> The important part is to use only core API's and don't
make use of any
> view oriented API's (like view cursors for example).
>
> It might be also interesting to compare the results
with AODL or odfj
> solutions and take this analysis into account when
thinking about
> improvements.
>
> That are tasks which can be done in parallel to the
ongoing
> modularization tasks which are important for future
usage of the code
> base as a toolkit.
>
> The example implementations can be implemented in Java
and Java UNO and
> for example NetBeans to make the development much
smarter than.
>
> I am personally behind my own schedule because of some
other important
> and longer scheduled task but i am looking forward to
work with
> interested people together on this task.
>
> If you are interested please feel free to contact me or
better
> communicate on this mailing list and let us think about
concrete steps.
>
> Juergen
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribe odftoolkit.openoffice.org
> For additional commands, e-mail: dev-help odftoolkit.openoffice.org
>
>
|
|
| Re: UNO based toolkit API |

|
2007-05-29 06:19:12 |
Hi Kris,
Kris Dev wrote:
> Hai Juergen,
>
> We have developed 'e-Administration', a J2EE
application for communication
> management (http://ll2b.blogspot.com
). We have used FCK editor. We would
> like to integrate open office for ODF.
>
> Can you please advise us how we go about it?
currently you would have to run OO.org in some kind of
server mode
without UI. But this solution still requires a X server on
your server.
Not optimal, but you can contact Sun and can ask for their
StarOffice
Server solution.
Anyway, we are currently not in the situation that an UNO
based ODF
toolkit without OO.org/StarOffice in the background exists.
Juergen
>
> Regards,
>
> Kris Dev
> e-Gov Consultant
> India.
>
> On 5/25/07, Juergen Schmidt <juergen.schmidt sun.com> wrote:
>>
>> Hi,
>>
>> our IRC meeting in the morning was to confusing for
me, i would suggest
>> to focus on some topics in this specific time slot.
Everything else can
>> be discussed in separate slots. What do you think?
>>
>> Anway, as i mentioned in the morning our focus is a
UNO based toolkit
>> API where we want to reuse as much as possible from
the existing code
>> base. The advantages are obvious and already
documented on the
>> odftookit.openoffice.org hoempage.
>>
>> I would like to evaluate the already collected use
cases and do some
>> example implementation with the current office API.
In a second step i
>> would like to analyze the used API's to check how
we can improve them or
>> how we can make use of the UNO ease of use
features to make these
>> API's more intuitive and usable if necessary. That
means not that we
>> automatically will change existing API's
incompatible but it is might be
>> possible. It has to be analyzed in detail. For
missing features it is
>> necessary to define new UNO API's and provide an
appropriate
>> implementation.
>>
>> The important part is to use only core API's and
don't make use of any
>> view oriented API's (like view cursors for
example).
>>
>> It might be also interesting to compare the results
with AODL or odfj
>> solutions and take this analysis into account when
thinking about
>> improvements.
>>
>> That are tasks which can be done in parallel to the
ongoing
>> modularization tasks which are important for future
usage of the code
>> base as a toolkit.
>>
>> The example implementations can be implemented in
Java and Java UNO and
>> for example NetBeans to make the development much
smarter than.
>>
>> I am personally behind my own schedule because of
some other important
>> and longer scheduled task but i am looking forward
to work with
>> interested people together on this task.
>>
>> If you are interested please feel free to contact
me or better
>> communicate on this mailing list and let us think
about concrete steps.
>>
>> Juergen
>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribe odftoolkit.openoffice.org
>> For additional commands, e-mail: dev-help odftoolkit.openoffice.org
>>
>>
>
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe odftoolkit.openoffice.org
For additional commands, e-mail: dev-help odftoolkit.openoffice.org
|
|
| Re: UNO based toolkit API |

|
2007-05-29 06:29:43 |
Hai Juergen,
Thanks for the feedback.
Can OO / SO run in the server and we access it from the
clients within our
application?
Regards,
kris.
On 5/29/07, Juergen Schmidt <juergen.schmidt sun.com> wrote:
>
> Hi Kris,
>
> Kris Dev wrote:
> > Hai Juergen,
> >
> > We have developed 'e-Administration', a J2EE
application for
> communication
> > management (http://ll2b.blogspot.com
). We have used FCK editor. We would
> > like to integrate open office for ODF.
> >
> > Can you please advise us how we go about it?
>
> currently you would have to run OO.org in some kind of
server mode
> without UI. But this solution still requires a X server
on your server.
> Not optimal, but you can contact Sun and can ask for
their StarOffice
> Server solution.
>
> Anyway, we are currently not in the situation that an
UNO based ODF
> toolkit without OO.org/StarOffice in the background
exists.
>
> Juergen
>
>
> >
> > Regards,
> >
> > Kris Dev
> > e-Gov Consultant
> > India.
> >
> > On 5/25/07, Juergen Schmidt
<juergen.schmidt sun.com> wrote:
> >>
> >> Hi,
> >>
> >> our IRC meeting in the morning was to
confusing for me, i would suggest
> >> to focus on some topics in this specific time
slot. Everything else can
> >> be discussed in separate slots. What do you
think?
> >>
> >> Anway, as i mentioned in the morning our focus
is a UNO based toolkit
> >> API where we want to reuse as much as possible
from the existing code
> >> base. The advantages are obvious and already
documented on the
> >> odftookit.openoffice.org hoempage.
> >>
> >> I would like to evaluate the already collected
use cases and do some
> >> example implementation with the current office
API. In a second step i
> >> would like to analyze the used API's to check
how we can improve them
> or
> >> how we can make use of the UNO ease of use
features to make these
> >> API's more intuitive and usable if necessary.
That means not that we
> >> automatically will change existing API's
incompatible but it is might
> be
> >> possible. It has to be analyzed in detail. For
missing features it is
> >> necessary to define new UNO API's and provide
an appropriate
> >> implementation.
> >>
> >> The important part is to use only core API's
and don't make use of any
> >> view oriented API's (like view cursors for
example).
> >>
> >> It might be also interesting to compare the
results with AODL or odfj
> >> solutions and take this analysis into account
when thinking about
> >> improvements.
> >>
> >> That are tasks which can be done in parallel
to the ongoing
> >> modularization tasks which are important for
future usage of the code
> >> base as a toolkit.
> >>
> >> The example implementations can be implemented
in Java and Java UNO and
> >> for example NetBeans to make the development
much smarter than.
> >>
> >> I am personally behind my own schedule because
of some other important
> >> and longer scheduled task but i am looking
forward to work with
> >> interested people together on this task.
> >>
> >> If you are interested please feel free to
contact me or better
> >> communicate on this mailing list and let us
think about concrete steps.
> >>
> >> Juergen
> >>
> >>
------------------------------------------------------------
---------
> >> To unsubscribe, e-mail: dev-unsubscribe odftoolkit.openoffice.org
> >> For additional commands, e-mail: dev-help odftoolkit.openoffice.org
> >>
> >>
> >
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribe odftoolkit.openoffice.org
> For additional commands, e-mail: dev-help odftoolkit.openoffice.org
>
>
|
|
[1-4]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|