1998-01-31 23:39:01 +00:00
|
|
|
|
"""Main Pynche (Pythonically Natural Color and Hue Editor) widget.
|
1998-10-02 16:06:27 +00:00
|
|
|
|
|
|
|
|
|
This window provides the basic decorations, primarily including the menubar.
|
|
|
|
|
It is used to bring up other windows.
|
1998-01-31 23:39:01 +00:00
|
|
|
|
"""
|
|
|
|
|
|
|
|
|
|
from Tkinter import *
|
1998-09-29 20:03:53 +00:00
|
|
|
|
import tkMessageBox
|
1998-01-31 23:39:01 +00:00
|
|
|
|
|
1998-09-28 23:38:44 +00:00
|
|
|
|
# Milliseconds between interrupt checks
|
|
|
|
|
KEEPALIVE_TIMER = 500
|
1998-02-17 22:25:23 +00:00
|
|
|
|
|
|
|
|
|
|
1998-02-12 19:52:31 +00:00
|
|
|
|
|
1998-09-28 23:38:44 +00:00
|
|
|
|
class PyncheWidget:
|
Many changes to support a second mode of operation. Pynche can now be
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.
1998-10-22 03:25:59 +00:00
|
|
|
|
def __init__(self, version, switchboard, master=None):
|
1998-10-01 16:46:16 +00:00
|
|
|
|
self.__sb = switchboard
|
|
|
|
|
self.__version = version
|
|
|
|
|
self.__textwin = None
|
1998-10-02 16:05:48 +00:00
|
|
|
|
self.__listwin = None
|
1998-10-05 21:14:46 +00:00
|
|
|
|
self.__detailswin = None
|
Many changes to support a second mode of operation. Pynche can now be
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.
1998-10-22 03:25:59 +00:00
|
|
|
|
modal = self.__modal = not not master
|
|
|
|
|
# If a master was given, we are running as a modal dialog servant to
|
|
|
|
|
# some other application. We rearrange our UI in this case (there's
|
|
|
|
|
# no File menu and we get `Okay' and `Cancel' buttons), and we do a
|
|
|
|
|
# grab_set() to make ourselves modal
|
|
|
|
|
if modal:
|
|
|
|
|
self.__tkroot = tkroot = Toplevel(master, class_='Pynche')
|
|
|
|
|
tkroot.grab_set()
|
|
|
|
|
tkroot.withdraw()
|
|
|
|
|
else:
|
|
|
|
|
# Is there already a default root for Tk, say because we're
|
|
|
|
|
# running under Guido's IDE? :-) Two conditions say no, either the
|
|
|
|
|
# import fails or _default_root is None.
|
|
|
|
|
tkroot = None
|
|
|
|
|
try:
|
|
|
|
|
from Tkinter import _default_root
|
|
|
|
|
tkroot = self.__tkroot = _default_root
|
|
|
|
|
except ImportError:
|
|
|
|
|
pass
|
|
|
|
|
if not tkroot:
|
|
|
|
|
tkroot = self.__tkroot = Tk(className='Pynche')
|
|
|
|
|
# but this isn't our top level widget, so make it invisible
|
|
|
|
|
tkroot.withdraw()
|
1998-09-28 23:38:44 +00:00
|
|
|
|
# create the menubar
|
1998-10-06 19:39:34 +00:00
|
|
|
|
menubar = self.__menubar = Menu(tkroot)
|
1998-09-28 23:38:44 +00:00
|
|
|
|
#
|
|
|
|
|
# File menu
|
|
|
|
|
#
|
Many changes to support a second mode of operation. Pynche can now be
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.
1998-10-22 03:25:59 +00:00
|
|
|
|
if not modal:
|
|
|
|
|
filemenu = self.__filemenu = Menu(menubar, tearoff=0)
|
|
|
|
|
filemenu.add_command(label='Quit',
|
|
|
|
|
command=self.__quit,
|
|
|
|
|
accelerator='Alt-Q',
|
|
|
|
|
underline=0)
|
1998-09-28 23:38:44 +00:00
|
|
|
|
#
|
1998-10-01 16:46:16 +00:00
|
|
|
|
# View menu
|
|
|
|
|
#
|
1998-10-06 19:39:34 +00:00
|
|
|
|
viewmenu = Menu(menubar, tearoff=0)
|
1998-10-01 16:46:16 +00:00
|
|
|
|
viewmenu.add_command(label='Text Window...',
|
|
|
|
|
command=self.__popup_text,
|
|
|
|
|
underline=0)
|
1998-10-02 16:05:48 +00:00
|
|
|
|
viewmenu.add_command(label='Color List Window...',
|
|
|
|
|
command=self.__popup_listwin,
|
|
|
|
|
underline=0)
|
1998-10-05 21:14:46 +00:00
|
|
|
|
viewmenu.add_command(label='Details Window...',
|
|
|
|
|
command=self.__popup_details,
|
1998-10-06 19:39:34 +00:00
|
|
|
|
underline=0)
|
|
|
|
|
#
|
1998-09-28 23:38:44 +00:00
|
|
|
|
# Help menu
|
|
|
|
|
#
|
1998-10-06 19:39:34 +00:00
|
|
|
|
helpmenu = Menu(menubar, name='help', tearoff=0)
|
1998-10-20 20:45:46 +00:00
|
|
|
|
helpmenu.add_command(label='About Pynche...',
|
1998-09-28 23:38:44 +00:00
|
|
|
|
command=self.__popup_about,
|
|
|
|
|
underline=0)
|
1998-10-06 19:39:34 +00:00
|
|
|
|
#
|
|
|
|
|
# Tie them all together
|
|
|
|
|
#
|
Many changes to support a second mode of operation. Pynche can now be
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.
1998-10-22 03:25:59 +00:00
|
|
|
|
if not modal:
|
|
|
|
|
menubar.add_cascade(label='File',
|
|
|
|
|
menu=filemenu,
|
|
|
|
|
underline=0)
|
1998-10-06 19:39:34 +00:00
|
|
|
|
menubar.add_cascade(label='View',
|
|
|
|
|
menu=viewmenu,
|
|
|
|
|
underline=0)
|
|
|
|
|
menubar.add_cascade(label='Help',
|
|
|
|
|
menu=helpmenu,
|
|
|
|
|
underline=0)
|
|
|
|
|
|
|
|
|
|
# now create the top level window
|
|
|
|
|
root = self.__root = Toplevel(tkroot, class_='Pynche', menu=menubar)
|
Many changes to support a second mode of operation. Pynche can now be
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.
1998-10-22 03:25:59 +00:00
|
|
|
|
root.protocol('WM_DELETE_WINDOW',
|
1998-10-22 18:46:28 +00:00
|
|
|
|
modal and self.__bell or self.__quit)
|
1998-10-06 19:39:34 +00:00
|
|
|
|
root.title('Pynche %s' % version)
|
|
|
|
|
root.iconname('Pynche')
|
Many changes to support a second mode of operation. Pynche can now be
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.
1998-10-22 03:25:59 +00:00
|
|
|
|
# Only bind accelerators for the File->Quit menu item if running as a
|
|
|
|
|
# standalone app
|
|
|
|
|
if not modal:
|
|
|
|
|
root.bind('<Alt-q>', self.__quit)
|
|
|
|
|
root.bind('<Alt-Q>', self.__quit)
|
|
|
|
|
else:
|
|
|
|
|
# We're a modal dialog so we have a new row of buttons
|
|
|
|
|
bframe = Frame(root, borderwidth=1, relief=RAISED)
|
|
|
|
|
bframe.grid(row=4, column=0, columnspan=2,
|
|
|
|
|
sticky='EW',
|
|
|
|
|
ipady=5)
|
|
|
|
|
okay = Button(bframe,
|
|
|
|
|
text='Okay',
|
|
|
|
|
command=self.__okay)
|
|
|
|
|
okay.pack(side=LEFT, expand=1)
|
|
|
|
|
cancel = Button(bframe,
|
|
|
|
|
text='Cancel',
|
|
|
|
|
command=self.__cancel)
|
|
|
|
|
cancel.pack(side=LEFT, expand=1)
|
1998-10-06 19:50:33 +00:00
|
|
|
|
|
|
|
|
|
def __quit(self, event=None):
|
Many changes to support a second mode of operation. Pynche can now be
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.
1998-10-22 03:25:59 +00:00
|
|
|
|
self.__tkroot.quit()
|
|
|
|
|
|
1998-10-22 18:46:28 +00:00
|
|
|
|
def __bell(self, event=None):
|
|
|
|
|
self.__tkroot.bell()
|
Many changes to support a second mode of operation. Pynche can now be
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.
1998-10-22 03:25:59 +00:00
|
|
|
|
|
|
|
|
|
def __okay(self, event=None):
|
|
|
|
|
self.__sb.withdraw_views()
|
|
|
|
|
self.__tkroot.grab_release()
|
|
|
|
|
self.__quit()
|
|
|
|
|
|
|
|
|
|
def __cancel(self, event=None):
|
|
|
|
|
self.__sb.canceled()
|
|
|
|
|
self.__okay()
|
1998-09-28 23:38:44 +00:00
|
|
|
|
|
|
|
|
|
def __keepalive(self):
|
|
|
|
|
# Exercise the Python interpreter regularly so keyboard interrupts get
|
|
|
|
|
# through.
|
1998-10-06 19:39:34 +00:00
|
|
|
|
self.__tkroot.tk.createtimerhandler(KEEPALIVE_TIMER, self.__keepalive)
|
1998-02-12 19:52:31 +00:00
|
|
|
|
|
1998-09-28 23:38:44 +00:00
|
|
|
|
def start(self):
|
Many changes to support a second mode of operation. Pynche can now be
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.
1998-10-22 03:25:59 +00:00
|
|
|
|
if not self.__modal:
|
|
|
|
|
self.__keepalive()
|
1998-10-06 19:39:34 +00:00
|
|
|
|
self.__tkroot.mainloop()
|
1998-02-17 22:25:23 +00:00
|
|
|
|
|
Many changes to support a second mode of operation. Pynche can now be
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.
1998-10-22 03:25:59 +00:00
|
|
|
|
def window(self):
|
1998-09-28 23:38:44 +00:00
|
|
|
|
return self.__root
|
|
|
|
|
|
1998-02-17 22:25:23 +00:00
|
|
|
|
def __popup_about(self, event=None):
|
1998-10-07 03:36:58 +00:00
|
|
|
|
from Main import __version__
|
1998-10-06 18:52:59 +00:00
|
|
|
|
tkMessageBox.showinfo('About Pynche ' + __version__,
|
1998-09-29 20:03:53 +00:00
|
|
|
|
'''\
|
1998-10-06 18:52:59 +00:00
|
|
|
|
Pynche %s
|
|
|
|
|
The PYthonically Natural
|
|
|
|
|
Color and Hue Editor
|
1998-09-29 20:03:53 +00:00
|
|
|
|
|
1998-10-20 20:45:46 +00:00
|
|
|
|
For information contact
|
1998-10-07 03:40:29 +00:00
|
|
|
|
author: Barry A. Warsaw
|
|
|
|
|
email : bwarsaw@python.org''' % __version__)
|
1998-10-01 16:46:16 +00:00
|
|
|
|
|
|
|
|
|
def __popup_text(self, event=None):
|
|
|
|
|
if not self.__textwin:
|
|
|
|
|
from TextViewer import TextViewer
|
|
|
|
|
self.__textwin = TextViewer(self.__sb, self.__root)
|
|
|
|
|
self.__sb.add_view(self.__textwin)
|
|
|
|
|
self.__textwin.deiconify()
|
1998-10-02 16:05:48 +00:00
|
|
|
|
|
|
|
|
|
def __popup_listwin(self, event=None):
|
|
|
|
|
if not self.__listwin:
|
|
|
|
|
from ListViewer import ListViewer
|
|
|
|
|
self.__listwin = ListViewer(self.__sb, self.__root)
|
|
|
|
|
self.__sb.add_view(self.__listwin)
|
|
|
|
|
self.__listwin.deiconify()
|
1998-10-05 21:14:46 +00:00
|
|
|
|
|
|
|
|
|
def __popup_details(self, event=None):
|
|
|
|
|
if not self.__detailswin:
|
|
|
|
|
from DetailsViewer import DetailsViewer
|
|
|
|
|
self.__detailswin = DetailsViewer(self.__sb, self.__root)
|
|
|
|
|
self.__sb.add_view(self.__detailswin)
|
|
|
|
|
self.__detailswin.deiconify()
|
Many changes to support a second mode of operation. Pynche can now be
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.
1998-10-22 03:25:59 +00:00
|
|
|
|
|
|
|
|
|
def withdraw(self):
|
|
|
|
|
self.__root.withdraw()
|
1998-10-22 18:46:28 +00:00
|
|
|
|
|
|
|
|
|
def deiconify(self):
|
|
|
|
|
self.__root.deiconify()
|