To echo this sentiment, and hopefully add something useful from an inexperienced user, one area that I would like to see focus on is "best practices"; cookbook sort of stuff. As I've been learning TG, I have basically been playing with different techniques based on what I already know about Python and HTML / CSS, and the little things I'm picking up about KID and SQLObject. The bottom line being that after all that wandering and munging, I've come up with stuff that works, but is surely sub-optimal in a variety of ways or will break spectaculary later because I'm not fully considering or aware of the complete implications of my design choices.
For instance, I'm semi-stuck with my current project because I can't get a select box to allow multiple selections for a many-many relation. The obvious solution of adding "multiple" attribute to the select tag just gets me a nice backtrace becuse Kid doesn't apparently like that... This is an obvious and common usage case, so there surely there's a known "good way to do it". Speakig of Kid backtraces, a quick guide to interpreting the backtrace information that comes up in the browser when something goes sideways would be useful. For example, I've figured out that a backtrace that finishes with a complaint that the template I'm using couldn't be found means that I have an error in that template. However, a lot of the backtrace information is somewhat unintelligable to someone who does not have experience with the components of TG. -QH- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
