Hi,

- I thought starting a new thread would be a better idea, this is more or less in reply to Kay Ramme's last e-mail in reply to me in the thread "[website-dev] direct links to 'project' pages on main page"

Working on a new project page proposal will for me be a nogo this week... too busy. Anyone else wants to give it a try already?

I believe http://wiki.services.openoffice.org/wiki/Architecturecan be transformed into a new project page, with some adjustments. It can then both communicate structure of the project, how projects relate, and what OOo actually is _all_ about.

See for more information the thread Re: [website-dev] direct links to 'project' pages on main page

Some explanations of the abbreviations:
- CUI == Command line User Interface - e.g. /usr/bin/soffice myDocument
- FWK == FrameworK
- VCL == Visual Component Library - the basic GUI toolkit (buttons, list boxes, windows, ...) - UCB == Universal Content Broker - the abstraction for file or http access (e.g. like Gnome VFS (Virtual File System)) - GSL == Graphics System Layer - VCL and more, like system integration (Drag&Drop, Clipboard)
- I18N == Internationalization, which enables  L10N (English, German, Dutch)
- L10N == Localizations (e.g. CTL (Complex Text Layout) or BiDi (Bi-directional writing))

The things placed on top (GUI, CUI, etc) are 'imports and exports'

About XML Kay notes: "XML may be misplaced here, either being the XML project (which would belong to the mid layer), or XML in general, which would be an import."

I don't think a simple image map will do for a project page. It should be more complete (it should feature at least all the accepted projects). Of course not all projects need to fit into the same diagram. This diagram is how the software works, not how e.g. management works, or marketing etc.

g.,


Maarten




--
Maarten Brouwers (murb)
http://www.murb.nl

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

Reply via email to