Package: jpilot
Version: 0.99.7-0.99.8-pre7-1
Severity: wishlist

This may be upstream wishlist...

After discussion on when to press [Sync] or [Backup] buttons, I thought
changing looks of these jpilot buttons depending on the existence of
/dev/pilot may be a good idea.  When it is not available, share them and
make them not to be clicked.  This idea applies even if you you change
to new interface method to USB devices.  

Basically, event loop should check pilot device availability and change
appearance of buttons.  (Above mentioned implementation details are not
that important.)

This kind of UI is much more intuitive to me than opening console and
checking device availability by hand.

Regards,

Osamu
-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

Versions of packages jpilot depends on:
ii  debconf                     1.4.42       Debian configuration management sy
ii  libatk1.0-0                 1.8.0-4      The ATK accessibility toolkit
ii  libc6                       2.3.2.ds1-20 GNU C Library: Shared libraries an
ii  libglib2.0-0                2.4.8-1      The GLib library of C routines
ii  libgtk2.0-0                 2.4.14-2     The GTK+ graphical user interface 
ii  libpango1.0-0               1.6.0-3      Layout and rendering of internatio
ii  libpisock8                  0.11.8-10    Library for communicating with a P

-- debconf information:
* shared/pilot/port: ttyUSB1

-- 
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
        Osamu Aoki <[EMAIL PROTECTED]>  Brussels Belgium, GPG-key: A8061F32
 .''`.  Debian Reference: post-installation user's guide for non-developers
 : :' : http://qref.sf.net and http://people.debian.org/~osamu
 `. `'  "Our Priorities are Our Users and Free Software" --- Social Contract



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to