File:  [mozdev] / chameleon / www / documentation / chameleon-todo.html
Revision 1.1: download - view: text, annotated - select for diffs - revision graph
Thu May 31 14:55:26 2001 UTC (19 years ago) by petejc
Branches: MAIN
CVS tags: HEAD
--pete

    <h2>Chameleon 0.03 ToDo</h2>

    This is ToDo list - plan for redesign of key Chameleon
    features.
     
    <ul>
      <li>
        Divide presentation &amp; background logic into separate
        components (in 0.02 was everything tied to the UI) -
        should allow future embedding in other applications. This
        implies mayor changes to Chameleon API.
      </li>
      <li>
        Generic XUL styling. We need to be able to load &amp;
        style any XUL files.
      </li>
      <li>
        <ul>
          <li>
            Load overlays to separate tabs (like menubar, navbar,
            personal toolbar etc.).
          </li>
        </ul>
      </li>
      <li>
        Throw away internal JS arrays representation of style and
        work directly over stylesheet through DOM (this was
        allowed only in latest builds due to fixes to bugs 7551 -
        dynamic stylesheet loading; bugnumber style DOM in XUL -
        pete's patch). Or we could use RDF database for storing
        these things. dunno...
      </li>
      <li>
        <ul>
          <li>
            Load XUL, create StyleSheet copy, exchange through
            dom. Work on the copy.
          </li>
        </ul>
      </li>
      <li>
        Add tree-like style representation - PowerUser UI -
        something like in Document Inspector
      </li>
      <li>
        Clean up UI - use standard XUL elements; where needed
        !extedned! (not redefined) through XBL
      </li>
      <li>
        Create Modern &amp; Classic skin for Chameleon
      </li>
    </ul>
    <h3>
      Chameleon API
    </h3>
    Pete, please help me think out in detail the new api, down to
    the level of function names. We'll implement it later. Let's
    try the top-down approach in app design! :-) We should start
    at top level, comment on it and then move downwards and
    iterate the comment &amp; correct procedure. Let me start
    here:<br>
     
    <dl>
      <dt>
        XUL loader
      </dt>
      <dd>
        load any XUL file, identify overlays, so that we can load
        them separately...
      </dd>
      <dt>
        Styling engine
      </dt>
      <dd>
        most complex part; 
      </dd>
      <dt>
        UI functions
      </dt>
      <dt>
      </dt>
      <dd>
        should use XUL loader to create separate tabs in UI for
        each overlay, generally use only calls to other parts of
        this API, 
      </dd>
      <dt>
        Background
      </dt>
      <dd>
        loading, saving of stylesheets, project management, RDF
        database(?), copying images to style folder...
      </dd>
      <dd>
        <br>
      </dd>
    </dl>
    <hr>
    <small>--mondo</small>


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>