Hi,

I'm new here, so allow me to introduce my self first.

>  Who you are
I'm 38, live in Bavaria, am recently married and have a little son

>  A few words on your background;
I've been working for 15 years in the IT busines, the last 5 years as
a free lance IT consultant in software testing.
I've done programming, system design, GUI design, project management,
documentation, testing. I have developed for Linux and Windows and
can code in Basic, Pascal, C, C++, Java, Perl, Python, TCL/TK

> Your interest in OpenOffice.org; and what you would like to see happen with 
> OpenOffice.org.
I've been working with DOORS a lot and found it horribly painfull.
After I learned about OpenOffice I think I can implement a new
approach of how to work with documents in a team. I think this could
very much help to shift the balance between MSOffice and OpenOffice
and I would be very happy if it would happen that way.


I would be very happy to receive your comments on this proposal.


====================================================================
= OO::EasyTracker  – A blend of Writer, Eclipse, Mind Map and Wiki =
====================================================================

MOTIVATION
I'm working in an environment, where I have to handle lots of specification 
documents, test code real source code, ... .
My specifications tend to be extensive, complicated and hard to comprehend.
Within the project life time I receive specification updates on a regular basis.
The project team produces many summary's, analysis, specifications, 
documentations together with many test
code and source code. Identifying the product requirements, keeping track of 
changes and knowing where they
are implemented and tested is vital for the projects success. It is also very 
important to keep information
easily accessible for new team members and to prevent loss of information when 
people leave the project. 
As now there is no tool on the market that offers a good and easy to follow 
approach to information management
in a team.

SOLUTION
Extending OpenOffice by following features and blending it together with 
Eclipse would solve the problem.

SHELL
OpenOffice will be embedded in an Eclipse shell that offers following 
functionality:
- User rights management (authentication, access, logging).
- Definition of projects and adding documents to the projects.
- Client/Server functionality.
- Text editors for source code.

SERVER
The server will hold the master version of all documents.

CLIENT
A client can register to a project and can request a document. If he wants to 
edit a part of the document
he can block that part, edit it and publish what he has edited. The client 
never writes to the file system,
but gets the documents via TCP/IP and also sends the changes via this channel.
Information enrichment
The users can add tags (plain text) to any section (character, word, paragraph, 
picture, column) of a document.
He can filter for this tags. He can also define clusters, consisting of tags 
and other clusters.
Elements within a cluster can have an order. The user can add a notification 
request to a tag.
If the tagged text changes he gets notified. A graph shows which tags overlap 
and to what degree.
All changes will be logged and are presented in a table like history form. Tags 
in source code will be
implemented as comments.

IMPORT FILTER
An import filter plug in (implemented in Pearl) will merge documents that has 
been changed outside the system,
on top of the document versions inside the system in a way that the text will 
be updated but the tags will not be lost.

INFORMATION ENRICHMENT
The users can add tags (plain text) to any section (character, word, paragraph, 
picture, column) of a document.
He can filter for this tags. He can also define clusters, consisting of tags 
and other clusters. Elements within
a cluster can have an order. The user can add a notification request to a tag. 
If the tagged text changes he gets
notified. A graph shows which tags overlap and to what degree. All changes will 
be logged and are presented in a
table like history form. Tags in source code will be implemented as comments.
Import filter
An import filter plug in (implemented in Pearl) will merge documents that has 
been changed outside the system,
on top of the document versions inside the system in a way that the text will 
be updated but the tags will not be lost.





-- 
Liebe Grüße / Best regards
Schuster Gerhard
mailto:[EMAIL PROTECTED]

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to