[haiku-3rdparty-dev] Re: Word Processor | Was: [HaikuPorts-dev] Abiwordport

  • From: Matthias Lindner <two4god@xxxxxxxxx>
  • To: haiku-3rdparty-dev@xxxxxxxxxxxxx
  • Date: Thu, 28 May 2015 14:05:55 +0200

H,
definitly from my side.. (again time is limited)
i just threw some ideas together... nothing professional just a collections
of thoughts and ideas:
but you can work on this as you wish.
https://docs.google.com/document/d/15UfXvOk95GaQqwZNOX2t5ph_TuuutWKVy974p07RXg0/edit?usp=sharing

blessings
Matthias

2015-05-28 13:35 GMT+02:00 Richie Nyhus-Smith <richienyhus@xxxxxxxxx>:

Is there still an intrest in this?

Hi,

Sorry to take so long to reply.

We should even think more "global"
eg. a systeme wide spellchecker, grammar checker or later even
a stylistic analysis[1] ( (maybe even used buy BTextView)

A general BOfficeDocument as a Basis for Spreadsheet, Presentation, Word
...

A general BOfficeLayout System wich can layout all "Objects"(rectangle
or splines and so on) like text, images. With the support for reference
line set from user but also calculated from the other objects in the Layout
System like the apple iPages one.

A genreal BPagedView - where all draw Operations are mapped to a
PagedView ( as configured eg. A4 landscape or A4 portrait and so on)

Agreed. There are many parts that could be reused in other projects.

It would be good to have full text indexing of documents and the automatic
creation of file attributes based on the top key words found in the
document file, which would be handy to have in other Haiku productivity
software such as DocumentViewer or DjVuViewer.

What document formats should supported for inport/export? Plus what
format should be used as the native format?

I would like to use a XML Format but not like the ODT where you split
the whole doucment in different sections... but maybe it is the best to use
a mature format. But personally, i never understood why you have to
seperate the styles from the document itself and so on.

There are a few open alternative specifications that could be used for a
native format, such as the Uniform Office Format [1], the abandoned Open
Document Architecture format [2] or the questionable OfficeOpen format
(based on MS office format) [3].

If a format was created from scratch, then possible mark up languages are
the Text Encoding Initiative language [4], Lout document language [5],
Heirloom troff [6], Xupl language [7], Simple Outline XML [8] or the
ZFormat document language [9].

Also a dream would be save on edit (like to append the changes.. maybe
also with some kind of autmated version control)

Proper version control would be an awesome feature for an office suite.

Where should the project be hosted? Bitbucket or Github?

Regards,
Richard.

[1] http://en.wikipedia.org/wiki/Uniform_Office_Format
[2] http://en.wikipedia.org/wiki/Open_Document_Architecture
[3] http://en.wikipedia.org/wiki/Office_Open_XML
[4] http://en.wikipedia.org/wiki/Text_Encoding_Initiative
[5] http://en.wikipedia.org/wiki/Lout_(software)
[6] http://heirloom.sourceforge.net/doctools.html
[7] http://en.wikipedia.org/wiki/Xupl
[8] http://en.wikipedia.org/wiki/Simple_Outline_XML
[9] http://z.departure.dk/index.html

Other related posts: