Here follows a list of the topics (in no particular order) we see a need for, in the 
next time.

Best regards, Pascal


PG.01a  Idle driver: after a given time w/o inputs,
        execute a given program; multiple handlers can
        be chained, e.g. one for pointer blanking, one
        for backlight off, one for sleep mode, etc.
        => TBD


PG.01b  Pointer blanking and imagery change: we have multiple sub-input
        drivers (we'll probably write a superdriver and have ts, backpad
        and keys as sub-drivers); each subdriver, when generating events
        may change the pointer imagery and en/disable delayed pointer
        blanking
        => Function to change ptr img/blking: TBD
        => super input driver: SMARTDATA


PG.02   Input driver for SoftKeys: tsinput.c should
        generate key events when a pen up occures outside
        the lcd area.
        => SMARTDATA


PG.03   Agree upon a convention to pass parameters to
        a driver: currently via env vars. Env vars seems
        okay, since passing a bunch of cmd-line params and
        propagating to drivers is a bit heavy.
        => ALL


PG.04   Demo application with all widgets, and always up-to-date
        => Does it already exist ?


PG.05   Autoconf
        => SMARTDATA


PG.06   fonts: - possibility to set global default font explicitely
               - for a context, possibility to set default font to
                 override global one
        => MICAH ?


PG.07   Do some profiling
        => TBD


PG.08   Rendering acceleration for linear 1, 2 and 4 (in C, not asm)
        => TBD


PG.09   EZ328 driver: - check cleanup after exit (xcopilot crashes)
                      - possibility to have the 1st lcd line off pgui
                        to use it as debug indicators
         => SMARTDATA


PG.10   Finder:
        terminology: finder = desktop + taskbar; desktop = apps icons
        - desktop: icons a la Palm, with grouping (tabs, menu ?)
        - taskbar:
                o when app running, a button to return to desktop
                o when desktop visible, several standard indicators;
                  some of them also visible when app running
                o indicators: area in the taskbar that app can access;
                  e.g. time/date, charge/battery level, alert (new SMS,
                  appointment), hw-module-related (e.g. GPS coordinates)
        - description file for apps; format ?  XML is really too heavy !!
        - apps located on filesystem, url or database (TBD)
        - an app may request GUI space (replacing the desktop), space in
          the taskbar, or even nothing (e.g. could splash a popup upon
          alert)
        - server port to change config: add/remove/move app, control
          taskbar
        - keys (soft, hard, or gui button) call a menu with shortcuts:
          favourites, and most-recent-used stuff
        => ALL: more ideas
        => SMARTDATA: implem.


PG.11   For apps wanting to show an indicator there are two possibilities:
        - getting the taskbar handle, they could create a canvas in it
          (currently not possible)
        - making a connection to the finder, telling it to create/remove/modify
          a canvas and receive click events
        => TBD


PG.12   GUI handling similar to cell-phones: Focus movable with 2 (or 4)
        keys; focused widget actionned by key; in dialog boxes, yes/no
        (= left/right) buttons clickable by two keys
        => TBD


-- 
  Pascal Bauermeister
  Head of Software Development

  SMARTDATA
  PSE-A / EPFL
  CH-1015 Lausanne

  http://www.smartdata.ch
  mailto:[EMAIL PROTECTED]
  Phone: +41 (21) 693 84 98
  fax:   +41 (21) 693 84 91

_______________________________________________
Pgui-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/pgui-devel

Reply via email to