Mailman 3 March 2004 - Tkinter-discuss

Pmw Question
by clnethery＠juno.com March 19, 2004

March 19, 2004

Sorry about that, I forgot to include a code example. Let me warn you first... ..this is ugly, OOP newbie code (my imports probably illustrate that, for starters), but it replicates the problem: ### imports ### import Tkinter from Tkinter import * from Tkconstants import * import idlelib.TreeWidget as tw import Pmw from xml.dom.minidom import parseString from idlelib.TreeWidget import TreeItem, TreeNode ### initialization ### root = Tkinter.Tk() root.title('Agile Integration Tool') Pmw.initialise(root) ### menubar ### mBar=Pmw.MenuBar(root, hull_relief='raised', hull_borderwidth=1) mBar.pack(fill='x') mBar.addmenu('File', 'Close this window or exit') mBar.addcascademenu('File', 'New', 'Set some other preferences', traverseSpec = 'z', tearoff = 1) mBar.addmenuitem('File', 'command', 'Save this application', command='save', label='Save') mBar.addmenuitem('File', 'command', 'Open up SaveAs dialog', command='saveas', label='Save As') mBar.addmenuitem('File', 'separator') mBar.addmenuitem('File', 'command', 'Exit the application', command='exit', label='Exit') Mainframe = Frame(root, width=1015, height=708) Mainframe.pack(fill = 'both', expand = 1, padx = 5, pady = 5) Notebook = Pmw.NoteBook(Mainframe) Notebook.setnaturalsize() Notebook.pack(fill = 'both', expand = 1, padx = 5, pady = 5) Notebook1 = Notebook.add('General Stuff') Notebook1MainFrame = Frame(Notebook1, borderwidth=2, width=975, height=600, relief=GROOVE) Notebook1MainFrame.pack(fill = 'both', expand = 1, padx = 5, pady = 5) Notebook1MainFrame.place(relx=0.01, rely=0.01, anchor=NW) Notebook1SubFrameRight = Frame(Notebook1MainFrame, borderwidth=2, relief=GROOVE, height=580, width=470) Notebook1SubFrameRight.pack(fill = 'both', expand = 1, padx = 5, pady = 5) Notebook1SubFrameRight.place(relx=0.5, rely=0.01, anchor=NW) HashBoxFrame = Frame(Notebook1SubFrameRight, borderwidth=2, width=440, height=280, relief=GROOVE) HashBoxFrame.pack(padx=1, pady=1, fill='both', expand=1) HashBoxFrame.place(relx=0.02, rely=0.36, anchor=NW) sc2 = Pmw.ScrolledFrame(HashBoxFrame) sc2.pack(fill=X, expand=1, padx=2, pady=2) sc2.place(relx=0.025, rely=0.025, anchor=NW) HashBox1 = Pmw.EntryField(sc2, labelpos=W, labelmargin=1, validate = None) HashBox1.pack(fill=X, expand=1, padx=1, pady=1) HashBox2 = Pmw.EntryField(sc2, labelpos=W, labelmargin=1, validate = None) HashBox2.pack(fill=X, expand=1, padx=1, pady=1) HashBox1.place(relx=0.01, rely=0.01, anchor=NW) HashBox2.place(relx=0.5, rely=0.01, anchor=NW) root.mainloop() I've removed most of the excess code, to make the remaining bad code easier to read. If you replace "sc2 = Pmw.ScrolledFrame(HashBoxFrame)" with "sc2 = Frame(HashBoxFrame)" it displays the EntryFields as I would like to display them (except for the fact that they're not in a ScrolledFrame).

2 1

Pmw question
by clnethery＠juno.com March 19, 2004

March 19, 2004

Hi there. I'm a newbie to Python and Tkinter and have encountered a problem I don't know how to overcome. The issue is as follows: I have created a GUI consisting of PMW Notebooks with PMW Notebooks inside them. I am now trying to insert a Pmw Scrolled Frame inside one of the "sub"-Notebooks, with Entryfields within the Scrolled Frame. I receive the error: "ScrolledFrame instance has no attribute 'tk'", which I assume is because ScrolledFrame inherits from Mega-Architype instead of Mega-Widget. Does anyone know of a way to get around this problem? Thanking you in advance, CN

2 1

RE: [Tkinter-discuss] Administrative items
by Peter Milliken March 19, 2004

March 19, 2004

Not meaning to be critical of the Intro :-) It is a great starting point but I'm not sure you should be holding it up as a "comprehensive" manual.... :-) I believe it is not comprehensive enough in some areas and the way it is written it doesn't leave the possibility that there is more information that should/could be searched for. For example, if you look at "Events and Bindings" and compare the attributes available from the Event Object as opposed to the attributes that are mentioned for the Event Object on the Tk man page. There are many more attributes available (see the equivalent Tk page) about an event than are mentioned in the Intro - sometimes these types of details can make a huge difference to an implementation of something i.e. I once wrote an application (in my Tcl/Tk days before I shifted to Python/Tkinter) that was required to time the difference between keystrokes (speech therapist wanted to measure and gather data on the frequency of stuttering in a patient) - I could have used a call to a time module but that all depended on *when* I decided to process the event - presenting all sorts of notty problems for the code, whereas the event object actually contains a time attribute - captured by the event processing system, that tells me quite accurately enough *when* that event occured. So there was no notty problems about "when" the key event was generated, I just used the time attribute of the event. So the Intro is a nice starting point that will probably be used by many without having to go further, but I believe it is far from "comprehensive" - in my view :-) Given that I have read books on GUI programming with Tcl/Tk and read the Grayson book on using Python with Tkinter, I find myself going continually to the Tk pages directly - but this is a "hidden" field for many newbies and your average Python programmer who doesn't have any Tcl/Tk background and therefore doesn't realise the wealth of detail that the Tk elements actually have and can provide. Probably the only real answer is a comprehensive translation of the Tk pages into Pythonese rather than "summaries" such as the Intro - something that I consider quite "dangerous" because of the lack of clues that all has not be faithfully "translated" (IMO - very critical of a noble effort and I apologise if this offends anyone). Peter -----Original Message----- From: Cameron Laird [mailto:claird@lairds.com] Sent: Thursday, March 18, 2004 8:21 AM To: FBatista(a)uniFON.com.ar; tkinter-discuss(a)python.org Subject: RE: [Tkinter-discuss] Administrative items > From tkinter-discuss-bounces(a)python.org Wed Mar 17 16:18:06 2004 > . > . > . > Me, who's in a pre-newbie state, but firmly decided to use Tkinter as > python's GUI, miss very much a comprehensive manual. > . > . > . Facundo, how does <URL: http://www.pythonware.com/library/tkinter/introduction/ > fail to meet your need? _______________________________________________ Tkinter-discuss mailing list Tkinter-discuss(a)python.org http://mail.python.org/mailman/listinfo/tkinter-discuss Warning: Copyright ResMed. Where the contents of this email and/or attachment includes materials prepared by ResMed, the use of those materials is subject exclusively to the conditions of engagement between ResMed and the intended recipient. This communication is confidential and may contain legally privileged information. By the use of email over the Internet or other communication systems, ResMed is not waiving either confidentiality of, or legal privilege in,the content of the email and of any attachments. If the recipient of this message is not the intended addressee, please call ResMed immediately on +61 2 9886 5000 Sydney, Australia.

4 3

Administrative items
by Cameron Laird March 18, 2004

March 18, 2004

1. Yes, I applied to gmane, so this'll be available as a newsgroup. I have no idea how long the process'll take. 2. What *I* really, really want, is a Wiki for Tkinter. It's a big enough subject to deserve its own; that's my view, at least. I can't face setting up a Wiki myself, just now (personal reasons); any volunteers? I'll gleefully pour in content, once there's a container, and I'm sure others will too. 3. Why are we doing this? A colleague I respect very, very much asked why we have a mailing list, rather than just (?!?) training people to use Subject-line keywords in comp.lang.python, for example. I have abundant reasons, but not so well-formulated that I can express them succinctly (basics: Tkinter social dynamics will fit this mailing list better). 'Any one else know how to say it? How much does the world need another Tkinter book? 'Know what? We *could* do a collaborative one. I wonder if that'd be interesting ...

4 10

RE: [Tkinter-discuss] Administrative items
by Batista, Facundo March 17, 2004

March 17, 2004

claird(a)phaseit.net wrote: #- > From tkinter-discuss-bounces(a)python.org Wed Mar 17 16:18:06 2004 #- > . #- > . #- > . #- > Me, who's in a pre-newbie state, but firmly decided to use #- Tkinter as #- > python's GUI, miss very much a comprehensive manual. #- > . #- > . #- > . #- Facundo, how does <URL: #- http://www.pythonware.com/library/tkinter/introduction/ > #- fail to meet your need? Use it a lot. 99.99% of times. But: - Need to fill ALL the widget patterns. Because you look at the syntax and options, but in doubt (and always faster) you look to the widget more common usage. - Need to fill with a lot of catchy details (those that are common sense to an experimented user but a newbie spends two hours looking around), i.e. how to finish a Tkinter app when using IDLE. - Needs to be packed in a better PDF or an HTML that you can print-it-all. - Needs to be updated (1999!) With all said, it's a *very* good book. I appreciate all the sections in each widget, and the organization of the first chapter. Because of that I thought it was a pitty when Fredrik said it was dead. I'll be very happy with a full and updated version of _this_ book (not so happy as to buy it with my devaluated argentinian pesos, but enough happy as to spend personal time in the effort). . Facundo

1 0

RE: [Tkinter-discuss] Administrative items
by Batista, Facundo March 17, 2004

March 17, 2004

On Wed, Mar 17, 2004 at 08:50:16PM +0000, Martin Franklin wrote: #- > What do people want in the Widget list / Widget pages? #- Example usage? A discussion of all the widget specific options? #- I guess a python translation of the Tk man pages would be a start? Me, who's in a pre-newbie state, but firmly decided to use Tkinter as python's GUI, miss very much a comprehensive manual. I know it's a hard task (that's why I'm attempting to participate in a collaborative book), but I think is very important. For example: Note the difference in Python if you don't it's Python Standard Library! . Facundo

2 1

Answers to a couple of Cameron's questions
by Kenneth McDonald March 17, 2004

March 17, 2004

1) Why a mailing list? I find that a mailing list is better if I have a particular focus. Due to the volume of something like comp.lang.python, I may not bother it for days on end, whereas getting the mailing list batched to me every day is very easy. 2) As regards a Tkinter book, I always thought that it would be really cool if Tkinter itself provided help in a consistent manner. For example: import Tkinter print Tkinter.__help__ As long as each "level" contains at least a reference to everything on the next "level", it would be easi(er) for a newbie to drill down to what they want. Also easier to maintain. Obviously, docstrings would be fine too. Ken

2 1

Tkinter aesthetic
by Batista, Facundo March 17, 2004

March 17, 2004

The other day in #python at irc.freenode.net, an user told me that Tkinter under Linux is *very* ugly (he migrated to GTK+ because of this). Is there a plan to beautify it? Thank you! . Facundo

5 5

RE: [Tkinter-discuss] Re: Tkinter aesthetic
by Batista, Facundo March 17, 2004

March 17, 2004

Stewart Midwinter wrote: #- I'm guessing that the look of Tk widgets is due to the way #- it achieves it #- cross-platform independence. I have a Tkinter app that I #- move seamlessly from #- Windows to Linux and back again. To me, anyway, that #- independence is worth #- something. If we get a nicer look (and for me, Qt has the #- nicest look of all #- the GUI toolkits), but lose that independence, we won't have #- advanced at all. Of #- course, if we can get a more modern look and retain that #- independence, I'm all #- for it. My exact position, :) #- As for GTK, after at least 5 hours and numerous attempts, I #- *still* can't get it #- working under Windows! I made it work, but it's a difficult task (did it three times, and always had to get into google to search for answers). And I don't want to get into it when I carry my application to another desk. . Facundo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ADVERTENCIA La información contenida en este mensaje y cualquier archivo anexo al mismo, son para uso exclusivo del destinatario y pueden contener información confidencial o propietaria, cuya divulgación es sancionada por la ley. Si Ud. No es uno de los destinatarios consignados o la persona responsable de hacer llegar este mensaje a los destinatarios consignados, no está autorizado a divulgar, copiar, distribuir o retener información (o parte de ella) contenida en este mensaje. Por favor notifíquenos respondiendo al remitente, borre el mensaje original y borre las copias (impresas o grabadas en cualquier medio magnético) que pueda haber realizado del mismo. Todas las opiniones contenidas en este mail son propias del autor del mensaje y no necesariamente coinciden con las de Telefónica Comunicaciones Personales S.A. o alguna empresa asociada. Los mensajes electrónicos pueden ser alterados, motivo por el cual Telefónica Comunicaciones Personales S.A. no aceptará ninguna obligación cualquiera sea el resultante de este mensaje. Muchas Gracias.

1 0

RE: [Tkinter-discuss] Administrative items
by Batista, Facundo March 17, 2004

March 17, 2004

claird(a)phaseit.net wrote: #- How much does the world need another Tkinter book? 'Know #- what? We *could* #- do a collaborative one. I wonder if that'd be interesting ... How many books are on-line (so anyone can download it for free)? I think the first question is answered. Yes, we *could* do a collaborative one. And I think that'd very interesting: for us and for Tkinter newbies (by the way, I belong to both of those groups). . Facundo

1 0