Hi Sweet Coffee, (A Realname would be nice)
you can find information about the spec process for OOo on
http://specs.openoffice.org/
There is a link for a spec template and also a guide.
Regards,
Christian
Sweet Coffee wrote:
Hi Kai!
I would be happy to contribute.
This would be my first attempt at something like this so I may need a
"little" mentoring so it comes out correct with the proper formatting.
-- How should the white paper be structured/formatted?
-- What should be the heading, categories, sub-categories or sections,
sub-sections I should cover?
Any suggestions on where or how I should begin research about this?
SC
On 6/29/05, Kai Ahrens <[EMAIL PROTECTED]> wrote:
Hi Sweet Coffee,
Sweet Coffee wrote:
Hello!
I hope you can help me with this.
I have written the Impress Project Managers about this but have not
received a response.
first of all I'd like to apologize for my late answer, but we were
very busy with development issues for OOo 2.0 the last weeks so
that I've got a huge mail backlog at the moment.
I am not a programmer, but I am trying to see if it is possible for me
to learn enough to attempt to create something like MS Producer for
OOo v 2.0 as an Impress add-on.. I have placed some links below to
demonstrate what I am referring to.
Producer 2003 Product Information
http://www.microsoft.com/office/powerpoint/producer/prodinfo/default.mspx
Producer 2003 Demos and Samples
http://www.microsoft.com/office/powerpoint/producer/prodinfo/demos.mspx
Many thanks for your offer to actively participate in the OOo project.
This feature is indeed one that we already considered for our future
development of Impress. MS producer is for sure a very good starting
point for this to be evaluated.
What kind of coding skills would it take to do something like that for
OOo v2.0 as an Impress add-on. I was thinking the "Ogg" and "Theora"
could be used for the audio and video components. These both come
from Xiph (http://www.xiph.org/)
http://www.vorbis.com/
http://www.theora.org/
I must admit that we didn't think of a possible feature set in detail
for this until now, so that it would be a good idea to start with a
whitepaper describing the feature set we want to achieve. This
whitepaper should contain all aspects of the new feature but doesn't
have to be a full spec in the first run. After agreeing on the feature
set, it would be easier to define how this can be implemented, via
API or in the application code itself.
Would it be possible for you to work on this whitepaper?
Regards
Kai
---------------------------------------------------------------------
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]
