From: Smith, F. <F....@te...> - 2004-09-29 21:18:20
|
This is very timely Kevin since I'm working on an application that would be well suited to Splitter main frame/background with codeEditors in at least two of the panes - it's a translation utility from a source pane to converted frame. Anyway, (I've elected to put the 2nd codeEditor in a child window for the time being.) Anyway, my application would fit just fine with what you've described to date. The kind of functionality within the sash examples in the wxPython demo is pretty cool though, basically supporting unlimited pane distribution within the background layout. Does this make sense?=20 I think the mp3 player in the PythonCard distribution might be an example of an application that could benefit from a splitter paradigm. Right now it has two static text areas. Regardless .... Thanks for working on this Kevin. -----Original Message----- From: Kevin Altis [mailto:al...@se...]=20 Sent: Wednesday, September 29, 2004 3:43 PM To: pythoncard-Users Subject: [Pythoncard-users] SplitterBackground and testSplitter sample Yesterday I checked in a new model.py that contains a very experimental=20 SplitterBackground subclass of Background along with a testSplitter=20 sample as a proof-of-concept of a 3 pane IDE-like window that contains=20 three separate panes (left, right-top, right-bottom). All the work is=20 done in the on_initialize method and was more or less stolen from the=20 wxPython demo Main.py file but it does show that backgrounds of other=20 samples can be used as panes in splitters similar to how pages in a=20 Notebook currently work by changing the superclass from Background to=20 PageBackground. If you have been waiting for splitter support, I would appreciate some=20 feedback on the types of windows or apps you were looking forward to=20 creating to get a better idea of whether we should just support a=20 default set of the most common pane configurations or allow unlimited=20 nesting. If there are particular samples or tools that you think would=20 benefit from the use of splitters as opposed to a single pane static or=20 sizer layout, etc. please say so, as those might make good tests of=20 features and expose problems with my simple wrapper. There are other issues with regards to where event handlers should be=20 located for common functionality, how user code should go about=20 determining which pane has focus, etc. I need to get some input from=20 the list so that I know whether I should be spending much time on=20 splitters before doing release 0.8.1 later this month. ka ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Pythoncard-users mailing list Pyt...@li... https://lists.sourceforge.net/lists/listinfo/pythoncard-users |