1. 02 Agu, 2010 1 kayıt (commit)
  2. 10 Tem, 2001 1 kayıt (commit)
  3. 18 Nis, 2001 1 kayıt (commit)
  4. 27 Nis, 1999 1 kayıt (commit)
  5. 26 Nis, 1999 1 kayıt (commit)
  6. 22 Eki, 1998 1 kayıt (commit)
    • Barry Warsaw's avatar
      Many changes to support a second mode of operation. Pynche can now be · ca07ba00
      Barry Warsaw yazdı
      run either as a standalone application (by running pynche or
      pynche.pyw), or as a modal dialog inside another application.  This
      can be done by importing pyColorChooser and running askcolor().  The
      API for this is the same as the tkColorChooser.askcolor() API, namely:
      
          When `Okay' is hit, askcolor() returns ((r, g, b), "name").  When
          `Cancel' is hit, askcolor() returns (None, None).
      
      Note the following differences:
      
          1. pyColorChooser.askcolor() takes an optional keyword `master'
             which if set tells Pynche to run as a modal dialog.  `master'
             is a Tkinter parent window.  Without the `master' keyword
             Pynche runs standalone.
      
          2. in pyColorChooser.askcolor() will return a Tk/X11 color name as
             "name" if there is an exact match, otherwise it will return a
             color spec, e.g. "#rrggbb".  tkColorChooser can't return a
             color name.
      
      There are also some UI differences when running standalone vs. modal.
      When modal, there is no "File" menu, but instead there are "Okay" and
      "Cancel" buttons.
      
      The implementation of all this is a bit of a hack, but it seems to
      work moderately well.  I'm not guaranteeing the pyColorChooser.Chooser
      class has the same semantics as the tkColorChooser.Chooser class.
      ca07ba00
  7. 20 Eki, 1998 1 kayıt (commit)
  8. 06 Eki, 1998 2 kayıt (commit)
  9. 05 Eki, 1998 2 kayıt (commit)
  10. 02 Eki, 1998 3 kayıt (commit)
  11. 01 Eki, 1998 2 kayıt (commit)