The only reason I would not go with TW2 at this point is because tgext.menu, while it works, can be difficult. I have yet to hear of a way (short of hardcoding the JS paths) to ensure that JSLinks are loaded in the proper order, while TW1 has this ability working correctly already.
But that's it. I know of no other reason not to use it. On Fri, Feb 4, 2011 at 3:23 AM, Tim Black <[email protected]> wrote: > Is there a good reason NOT to use ToscaWidgets 2 in TurboGears 2.1? I'm > just starting to make some compound widgets and think it might be best to go > ahead and use TW2. > > Tim > > -- > You received this message because you are subscribed to the Google Groups > "TurboGears" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/turbogears?hl=en. > -- Michael J. Pedersen My IM IDs: Jabber/[email protected], ICQ/103345809, AIM/pedermj022171 Yahoo/pedermj2002, MSN/[email protected] -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
