Hi Andreas,
Thanks for your feed back ...
Andreas Martens wrote:
> It's no problem to submit a draft to issue tracker,
don't hesitate to
> attach your first draft to issue 20386.
OK, I'll do this.
> Let's clarify these things later. The first and most
important questions
> are:
> 1. Do we want this feature?
> 2. Do we have a developer for implementation?
> I think your spec. draft is precise enough to discuss
these questions.
> If we have answered both question with yes, we should
spend more work to
> the specification to get it perfect.
That's what I think. Good.
> Okay, first question:
> Do we want these feature?
> On the one hand it has been on our wish list for OOo2.0
but on the other
> hand it got a low priority (5). Why? It's a known
feature and would help
> us to improve our interoperability with other office
suites. But I've
> seen only few documents which make use of this feature.
The request for
> it has been low.
> This changed a little bit because you showed your
interest and spent
> your time to create this specification, so there must
be a request for
> this feature at least from your side. Even I will not
implement it by
> myself, I will support anyone who volunteers for it.
My interest mainly grew from a discussion on users . And I
think that
interoperability is a good thing. Especially when more users
come.
OTOH, the feature is more on the fancy-side, than on the
business-one,
as I see it.
I understood (from the issue or a post in the thread on
users ?) that we
could make a first start with the specs...
When I started, I stumbled over the need for a developer
right away, but
decided to make a first draft anyway.
Nevertheless, I've no trouble in respecting the situation
that developer
capacity is limited, and that this issue isn't on the top
of the list.
> Second question:
> Do we have a developer for implementation?
> I don't, but I'm very interested to attract
developers for our word
> processing engine. If a volunteer has overcome the
obstacles of
> compiling and building our source code I will be
pleased with showing
> him the secrets of the Writer code
I don't have one either (at the moment my own experience
and agenda
don't allow me to step in). I do know two 'candidates'
that I try to get
interested, but also with other wishes on my mind...
[skiped most of the specs-issues]
>> 7 - Not known yet if the ODF file format supports
this page property.
>
> No, but if we implement it, we will sent a proposal to
the OASIS committee.
Looks as in interesting argument to me, to start the
implementation.
> If we find a developer we will step deeper into the
specification. There
> are some lacks of clarity e.g. what happens with
objects.
Ah I
thought I considered this aspect with looking at the
anchoring,
but we'll see that later.
I'll keep it in mind and see when there is a reason or
possibility to
pick it up more active.
Kindest regards,
& greetings,
Cor
--
Cor Nouws
Done a test ride and want to keep the car?
See http://why.openoffice.org/
------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribe specs.openoffice.org
For additional commands, e-mail: dev-help specs.openoffice.org
|