On 5/20/2017 1:43 PM, Raphael Bircher wrote:
Hi Patricia
Am .05.2017, 22:04 Uhr, schrieb Patricia Shanahan <p...@acm.org>:
...
A retired Sun or StarOffice person who understands how the code is
put together could save me a lot of time. My current low level
objective is to find where to put a break point to intercept a
double click on OLE substitute text. A few minutes of e-mail
response from someone who knows, or knows how to find out, might
save me hours or days. The same would apply to the professional
developers you want.
I don't think, that this people are already retired, they are not
old enough. And people from the pre SUN time bring not a load of
benefit. Most of the code has changed since 1998. AFAIK one of the
oldest part is the build in file picker (not the native one) He goes
back to 199x.
Hmmm. I distinctly remember Sun picking up StarOffice, and I was working
for Sun as a large server performance architect at the time. I retired
in 2002. I was able to retire early because of Sun stock options I sold
in 2000, something that happened to a lot of senior developers at Sun.
Even without that, I would be retired by now, age 68.
But what I want to say, we should not waste the time and try to
restore the old project. OpenOffice is old, in the IT world very old.
Things change from time to time. I don't say to scrap the old model
immediately. Maybe we should invite people from the whole ASF to
discuss how a modern Office Suite looks like. I believe we are to
strong focused on the old concept. Sometimes this blocks new ideas
and scares also companies with new ideas away.
That sounds sufficiently different that it should be run as a separate
project.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
