twingle/doc/teps tep-0100.txt,NONE,1.1

[email protected] Thu, 6 Mar 2003 05:49:16 -0700 (MST)
Newsgroups gmane.comp.cms.oscom.twingle.cvs
Message-ID <[email protected]>
Update of /cvs/root/twingle/doc/teps
In directory alpha.oscom.org:/tmp/cvs-serv12198

Added Files:
	tep-0100.txt 
Log Message:
First checkin.


--- NEW FILE: tep-0100.txt ---

TEP: 100
Title: Basic XUL wireframe for Twingle
Version: $Id: tep-0100.txt,v 1.1 2003/03/06 12:49:14 paul Exp $
Last-Modified: $Date: 2003/03/06 12:49:14 $
Author: Paul Everitt
Status: Active
Type: Standards Track
Content-Type: text/plain
Created: 06-Mar-2003

Abstract

  The UI for Twingle is organized by user goals and developer
  architecture.  This TEP proposes the organization, describes each
  component, and discusses the code layout.

Major UI Components

  The Twingle UI and code are organized into the following parts:

    1) Menu.

    2) Toolbar.

    3) Navigation. On the left, this is a multi-mode monster.  The
    normal-est mode is the tree, like a file browser.  The better
    modes are: "Recent", "People", "Find".  For now, pretend the modes
    are organized the way Mozilla's Sidebar panel works, kinda like
    stacking tabs.  All of this is driven by the underlying RDF model.

    3) Workspace.  The big part of the screen on the right.  Open tabs
    for each piece of content you have double-clicked on.

    4) Footer.  Not currently used and robably unnecessary.  Could be
    used for: a "panel" like GNOME, with common content types at easy
    disposal, or perhaps a log window to find problems.

XUL Package Layout

  Each of these UI components in the Twingle wireframe are reflected
  in the structure of the chrome package.

  The entry point is the 'twingle.xul' file in 'twingle/content'.
  This lays out the wireframe and includes the rest of the interface
  using XUL's overlay facility.

  Each of the UI components has a subdirectory in 'twingle/content',
  and each subdirectory has an overlay file.  Thus::

    twingle/content/
	twingle.xul
	menu/menuoverlay.xul
	toolbar/toolbaroverlay.xul
	navigation/navigationoverlay.xul
	workspace/workspaceoverlay.xul

Menu

  More to follow.

Toolbar

  More to follow.

Workspace

  The workspace is the main content area.  Each time you double-click
  to open a resource, a new tab appears in the workspace for the
  opened resource.

  Each open resource has multiple views that go with it.  For
  instance, you might want the following views on an article:

    1) Edit.

    2) Preview.

    3) Properties.

    4) History.

  Thus, an article would have four views.  Initially these views are
  represented as tabs.  (However, since this leads to tabs-with-tabs,
  we might rethink this.)

Copyright

  This document has been placed in the public domain.