[Tkinter-discuss] New Full Tkinter document editor widget --suggestions, comments, etc.
longorh at npt.nuwc.navy.mil
Tue Apr 1 19:22:24 CEST 2008
I've actually been considering WCK as a platform for future development (What
I've done so far I consider to be experimental). I've read your article
(Fredrik Lundh's, Using Event Trackers to Simplify Tool Implementation) and
really think this is a solution for implementing the addition of new kinds
I've recently written a very small plugin framework which automatically
loads all plugins in a path. As the plugin classes are instantiated, they
are provided with access to the Model, view widget and a notebook widget
(for inserting a custom GUI if applicable). With StyledText, I'm leaning
towards a design in which a plugin may also include a pluggable controller.
In this way, plugins will be used to add lists, tables, images and other
sorts of objects to StyledText.
I will periodically update the StyledWidget in the Tkinter wiki as I more
towards a final implementation.
Thanks for your comments.
Fredrik Lundh wrote:
> Michael O'Donnell wrote:
>> But I find that as you get more ambitious, better to use a Canvas widget
>> instead of a Text widget, which is pretty inflexible. Using a Canvas, you
>> need to do a lot more work (splitting text into lines, positioning lines
>> on the
>> canvas, etc.), but you can do almost anything you can think of with a
> on the other hand, the overhead might kill you if you switch to a
> Canvas. the Text widget is highly optimized for text rendering, after
> (I'd use a WCK widget if I were you guys, but that's me ;-)
> Tkinter-discuss mailing list
> Tkinter-discuss at python.org
View this message in context: http://www.nabble.com/New-Full-Tkinter-document-editor-widget----suggestions%2C-comments%2C-etc.-tp16266693p16419433.html
Sent from the Python - tkinter-discuss mailing list archive at Nabble.com.
More information about the Tkinter-discuss