To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=64717
User as changed the following:
What |Old value |New value
================================================================================
Status|NEW |STARTED
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Thu May 11 06:26:13 -0700
2006 -------
a) You should not rename openTarget() ... you should use the existing method
openPreset() and move your code from openTarget() to openPreset().
And it's not a question if it's possible that openTarget() can return readonly
storages. It's
designed that storages returned by openTarget() MUST(!) be opened in read/write
mode
and openPreset() returns readonly storages. Please move the code and everything
is
fine.
b) Copying / Storing all informations to the user layer isnt realy a bug. Not
in my
implementation nor in your patch. No discussion about it .-)
c) It's not realy a huge task. I think 1-2 weeks. But there is one problem:
migration of
real user defined shortcuts from OOo 2.0.x to OOo 2.0.4. For an OOo 3.0 version
there
is no such problem. Because there we support an explicit migration of such user
settings. But that's not possible for a normal product patch. So we have to
find a
solution to migrate user defined keys on demand ... or we have to ignore it.
That's why we dont started an implementation till now. Because this question
isnt
answered till today .-)
d) No problem. Of course this patch has to be verified by our QA so we dont
kill the
feature. That can be a disaster e.g. for the writer module. The cursor
traveling of the
writer base on shortcuts ...
e) Sorry for setting this task to INVALID. Of course we can find another way to
communicate ... but adding some comments without sending the issue back will
have
the risk, that you dont read my comments and wait for completion of this issue
.-)
May be we can communicate further via email ... ?
f) Yes - I allow to add this patch to OOo ... in case it works as aspected and
do not
break the feature. So if you make the mentioned changes and our QA shows us no
problems - you can integrate it into OOo.
Regards
Andreas
PS: further comments via email ?
---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
