Am 15.03.2011 22:06, schrieb Damon Courtney:
>> This is the same reason that megawidget frameworks aren't the (direct) answer to attract people. As a base, people expect all the "core" widgets to be available, which in Tk they aren't. They don't want to go create them. For Tk to be in the running for people it needs all those widgets there, and they need to be easy to use (which Tk is great for when the widget that's being used exists!). The megawidget stuff is great for after all the standard stuff is there.> > For the record, I was not proposing a megawidget framework as an answer to missing core functionality. I consider the lack of a megawidget framework AS missing core functionality. Much like with OO, the fact that so many have been written over the years only is proof that Tk should supply one.> > But not for enhancing core widgets where they so obviously need a feature. When it's obvious that something is missing from a core widget, the path is to fix or enhance the core widget, not use the built in megawidget framework to build over the top of it. The biggest reason Tk needs a megawidget framework is so that new widgets can be built on top of it and maintain the standard methods and interaction that widgets coded in C all share.> > Being written in C in the completely silly way that Tk widgets are written should not be a requirement for adding new widgets to the core. Most widgets never need the kind of speed that C provides and could easily be written in Tcl/Tk. They just lack a framework that provides the basics and enforces a set of standards that all core widgets follow.> > This is what I want in the core.> > D> ------------------------------------------------------------------------------> Colocation vs. Managed Hosting> A question and answer guide to determining the best fit> for your organization - today and in the future.> http://p.sf.net/sfu/internap-sfd2d> _______________________________________________> Tcl-Core mailing list> Tcl-...@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/tcl-core
+1 from me
I think the elements provided in ttk should be made available on Tcl
level (i once tried a version of some of them and it does not seem to be
too hard) and then widgets including layout, states and style
functionality also written in Tcl should be built on that base. I am
also pretty sure that C is not necessary for speed reasons for most Tk
functionality.
Arnulf
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
Tcl-Core mailing list
Tcl-...@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tcl-core