|
| |
Structured Authoring/ Editing
Project Goals : Structured
Editing : Overview
09-Sep-2002/09-Jan-06
Overview
One of the Primary Goals of The Tark
is to enable the Information Architect or Web Site
Designer rather than the Web Page Designer to structure, create
and manage complex websites. Structured Authoring/ Editing means
also the Separation of logical structure and Layout.
Since HTML is a SGML DTD, all approaches trying to imitate a DTP-like
page layout are doomed to fail; The Tark will use a different way
based on ideas proven to work by structured editing environments like
LyX,
Klyx, and
GNU TeXmacs.
About WYSIWYG and Strctured Editing
I like WYSIWYG
because it lightens the burden of dealing with the most terrible thing:
code; I like the possibility of editing code, but I hate being forced to
athor documents with markup and code; that's stuff I want to get rid
off, when I write, but it has to be there to correct or enhance it, if
necessary. That's possible in old versions of Word Perfect (press
<Alt><F3> and it's there), in any version of Frontpage, but not in
(Win-) Word, Lyx or Frame.
And I hate WYSIWYG
because it usually lies to me or gives me at least just a rough
approximation af what I would need to see. My screen resolution
(currently 1600x1200 with 24 bpp) can't even show me exactly how my
digital photos will look after printing on my printer; fonts are being
substituted by almost any Windows application, and the screen resolution
isn't even close to being able to display the differences. This might be
different with Display Postscript (hello again, GNUstep! ;) and when I
can afford the IBM T221 22.2-inch LCD monitor with 204 pixels per inch
and 3840 x 2400 pixels, but at the moment
WYSIWYG is some kind
of a necessary workaround and a de-facto standard.
And that's the point where I think, that it must be possible to
design an authoring environment where I don't have to write code or
markup which distracts me from my writing (as in Emacs), but can move
quickly in the document (as in Emacs), structure and format the document
(as in any good outliner) and get good printouts (as in Word or LaTeX).
Frontpage is quite good in structuring and managing huge amounts of
content (e.g., my site kefk.net currently consists of 152.000 documents
or 5,14 GB of data; I thought It would be less ;), but it is lame in
designing and printing letters, or automatically hyperlink information
(as in Vanilla). I can mix a dozen of applications, all being
incopmpatible with each other, and solve the "problems", but the data is
somehow dead: I can't query it. That's where XML and tools like
 Conglomerate
become interesting.
References
Conglomerate.org: Structured data and the death of WYSIWYG,
by Joakim Ziegler,
www.conglomerate.org/docs/death_of_wysiwyg.html.
Annotations
| |
Login |
Logout
Name: Visitor
Online: 2 active users.
|
|
Project
»Tark« |
About
